Gladex Agent Logs

value-taking flag + control **C24** and repaired `verify-landing --env`
(154 → 168), queue item (75) added the spacing-independent **scope reader** +
control **C25** so an option line written with two spaces cannot drop out of
every reader at once (168 → 182), queue item (71) narrowed the `--timeout`
scope to the table's own exit-2 bullet + control **C26** (182 → 190), queue
item (76) dropped that reader's description-column requirement + control
**C27** (190 → 201), queue item (77) gave the tool's own `usage:` row a
reader — **G20**–**G23** + control **C28** — and repaired the three `--help`
bodies it caught (201 → 213), and queue item **(73)** `[0.4.140]` read the
metavar's own **type** — two more derived classes, enum and quantity, as
**G24**–**G30** + control **C29**, with the 61-pair scope partitioned and
asserted rather than assumed (213 → **234**) — a documented exit 2
is now probed for a bad *value*, and the codes this suite cannot reach are
declared rather than implied)

## test_detached_children.sh

**Purpose**: The detached-child sweep of queue item **(80)**, made permanent.
`[0.4.124]` proved that exactly ONE registered tool (`tools/regression-run`)
> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -1016,16 +1016,20 @@
 **Location**: `/data/repo/tools/verify-landing`
 
 **Usage**:
 ```
-verify-landing [--help] [--env dev|prod] [--port PORT]
+verify-landing [--help] [--env ENV] [--port PORT]
 ```
 Since `[0.4.123]` this row is also what the tool itself prints as its
 `usage:` line: it used to print `[OPTIONS]`, so a checker reading the
 tool's own synopsis could not see what the tool takes. Enforced, not
 merely written — `tests/test_registry_coverage.sh` section **G20–G23**
-reads that row for every tool with an option list, and **C28** replants
-the `[OPTIONS]` shape.
+reads that row for every tool with an option list, **G31–G34** read it
+again for every *pair* on it (queue item **(79)**, `[0.4.141]`), and
+**C28**/**C30** replant the `[OPTIONS]` shape and the "flag present,
+pair missing" shape respectively. `[0.4.141]` is why this row now says
+`[--env ENV]` and not `[--env dev|prod]`: the option list below is the
+side every probe reads, so the synopsis follows it.
 
 **Options**:
 - `--env ENV` - Environment to check (default: dev)
 - `--port PORT` - Port to check (default: 8000 for dev, 8001 for prod)

← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -3593,16 +3593,19 @@
 `#!/usr/bin/env bash` → `repo-lint` dispatches it as `bash`)
 
 **Usage**:
 ```
-go-compile-drift-verify [--help] [--list] [--only S1[,S2...]]
-                        [--format human|jsonl] [--keep] [--out DIR]
+go-compile-drift-verify [--help] [--list] [--only IDS] [--format FMT] [--keep] [--out DIR]
 ```
 Since `[0.4.123]` the tool prints those flags as **one** row starting on the
 `Usage:` label; the label used to sit alone on its own row with the synopsis
 wrapped below it, so the line a checker reads (`usage:` → first row) named no
 flag at all. Same rule, same reader: `tests/test_registry_coverage.sh`
-**G20–G23**, control **C28**.
+**G20–G23**, control **C28**. Since `[0.4.141]` it also names every pair the
+option list below it advertises — the row said `--only S1[,S2...]` and
+`--format human|jsonl` while the options said `--only IDS` and
+`--format FMT`, i.e. two promises that did not match, and the options side
+won because it is the side the probes read (**G31–G34**, control **C30**).
 
 **Options**:
 - `--help` - usage plus the exit-code table (exit 0)
 - `--list` - print the five scenarios and their expectations, clone nothing (exit 0); honours `--format jsonl`

> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -3120,12 +3120,43 @@
 `VIOLATION synopsis_flags <tool>` with `ERROR synopsis_no_scope` if the scope
 ever reads nothing, and asserted as **G20–G23** (floor 15, `syn_n == syn_ok`,
 no violation on the live tree) with control **C28** planting the exact shape on
 a tool that is otherwise perfect. What this rule deliberately does **not** do:
-hold every tool's synopsis to *every* flag it takes — (77) also measured that
-pair-level reading at **31 of 58** value-taking pairs, and closing it would
-mean rewriting 19 help bodies rather than three, which is a different step.
+hold every tool's synopsis to *every* pair it takes — (77) also measured that
+pair-level reading at **31 of 58** value-taking pairs (33 after its own three
+repairs) and called it a different, larger step.
 
+Since `[0.4.141]` that step is taken (queue item **(79)**): the same row must
+now name **every** `--flag METAVAR` pair the option list advertises, in the
+option list's own spelling — `--env dev|prod` in the synopsis beside `--env
+ENV` in the options is two different promises, and the option list is the side
+every probe in this file reads. Re-measured on the tree *before* the repair,
+by the same reader that counts `conv_pairs`, so the pair set is the option
+list's and not a second list: **36 of 61** pairs held, **25 short across 11
+tools** (`regression-run` 2/8, `immich-roundtrip` 2/7, `tls-check` 2/5,
+`inbox-status` 3/5, `ip-drift-check` 2/4, `dns-verify` 2/3,
+`smtp-relay-probe` 2/3, `repo-lint` 3/4, `domain-availability-check` 1/2,
+`verify-landing` 1/2, `go-compile-drift-verify` 1/3) — the same 11 tools and
+the same per-tool counts as (77)'s 33 of 58, three pairs having been added
+elsewhere since. The **row** and not the whole wrapped block: argparse wraps a
+*generated* usage at the terminal width, so `regression-run`'s synopsis is
+four rows and its first row holds two of eight pairs — measured, not assumed —
+and a continuation row is exactly what (77) already ruled out. The repair
+writes the synopsis out: an explicit `usage=` is printed verbatim and never
+wrapped (measured under `COLUMNS=80`) in the nine argparse tools, while the
+two hand-written ones name the metavars their own option lists use (`--only
+IDS` / `--format FMT`, `--env ENV`). That reintroduces a copy, which is the
+objection `[0.4.59]`'s Q13 raised against one, and it is answered rather than
+dismissed: an option added later whose pair never reaches the row reddens
+**G33** instead of drifting quietly. Reported on the same
+`VIOLATION synopsis_flags <tool>` line and the same subject — one tool, one
+finding, so every control's "exactly one violation" still counts what it says —
+asserted as **G31–G34** (keys present, floor 30, `synp_n == synp_ok`, never
+more pairs than `conv_pairs` counted) with control **C30** planting the defect
+on a tool (77) *passes*: `syn_ok == syn_n` while `synp_ok` sits one below
+`synp_n` on the same plant, which is what proves the two rules are separate
+claims rather than one rule counted twice.
+
 Since `[0.4.140]` the probe finally reads the **metavar's own type** and asks the
 value half of it (queue item (73)). (69) proved the shape — a port is an integer
 1-65535 for every tool that has one, so `not-a-number` is invalid without asking
 any of them — and stopped there, because `--domain`/`--server`/`--ca-file` have

← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -3243,12 +3243,12 @@
 `REGISTRY_COVERAGE_CHILD` is internal (the re-exec branch). Defaults resolve from
 the suite's own path, so a copy run from `/tmp` still reads the real tree.
 
 **Tests**:
-- `bash tests/test_registry_coverage.sh` → **234 assertions**, ~170s, no network:
+- `bash tests/test_registry_coverage.sh` → **248 assertions**, ~170s, no network:
   **A** the live tree is fully covered (exit 0, zero violations, no `ERROR`),
   **B** seven cross-checks against an independent recount (tools, sections, tool
-  sections, `--help` probed, `--help` answered, two floors), **C** 29 negative
+  sections, `--help` probed, `--help` answered, two floors), **C** 30 negative
   controls — unregistered tool, deleted section, stale tool heading, stale suite
   heading, one missing field each of Usage/Purpose/exit codes, `--help` exiting
   non-zero, `--help` silent, missing registry, missing tools dir, empty tools
   dir, sectionless registry, a tool that swallows an unknown flag (**C14**),

> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -3280,9 +3280,14 @@
   by its flag spacing *and* outside the third reader by its description
   spacing, so before `[0.4.122]` **no reader held the line at all** (`C27h`
   exactly one pair leaving the probing scope, `C27j` one value-taking flag
   fewer than the live tree, `C27k` the widened reader still seeing every pair
-  the live tree does), each
+  the live tree does), and **C30** a tool whose labelled `usage:` row names a
+  flag but omits one of its own option-list pairs — the (79) shape, planted so
+  that only the *pair* half fails: `C30h` shows (77) still passing on that very
+  plant (`syn_n == syn_ok`), `C30i` shows exactly one pair short, `C30g` keeps
+  the count at one finding, and `C30j` pins the plant's pair set to the live
+  tree's, so it cannot pass by advertising fewer pairs, each
   plant-asserted and
   count-asserted, **D** this
   suite's own `--help` and its exit-2 refusal of an unknown argument, **E** the
   exit-code tables are

← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -3414,9 +3414,13 @@
 reader — **G20**–**G23** + control **C28** — and repaired the three `--help`
 bodies it caught (201 → 213), and queue item **(73)** `[0.4.140]` read the
 metavar's own **type** — two more derived classes, enum and quantity, as
 **G24**–**G30** + control **C29**, with the 61-pair scope partitioned and
-asserted rather than assumed (213 → **234**) — a documented exit 2
+asserted rather than assumed (213 → **234**), and queue item **(79)**
+`[0.4.141]` gave that same row a **pair-level** reader — **G31**–**G34** +
+control **C30**, with 25 missing pairs repaired across **11** `--help` bodies
+and the finding folded into the (77) violation line so no control's count
+moved (234 → **248**) — a documented exit 2
 is now probed for a bad *value*, and the codes this suite cannot reach are
 declared rather than implied)
 
 ## test_detached_children.sh

> build · mimo-v2.6-flash-free

Select another run log from the list above. Only files matching run-YYYYMMDD-HHMMSS-N.log are readable.

[Wed Sep 30 17:12:17 2026] 127.0.0.1:60726 Accepted
[Wed Sep 30 17:12:17 2026] 127.0.0.1:60726 Closing
[Wed Sep 30 17:12:17 2026] 127.0.0.1:60738 Accepted
[Wed Sep 30 17:12:17 2026] 127.0.0.1:60738 Closing
[Wed Sep 30 17:12:18 2026] 127.0.0.1:60748 Accepted
[Wed Sep 30 17:12:18 2026] 127.0.0.1:60748 Closing
[Wed Sep 30 17:12:19 2026] 127.0.0.1:60764 Accepted
[Wed Sep 30 17:12:19 2026] 127.0.0.1:60764 Closing
[Wed Sep 30 17:12:19 2026] 127.0.0.1:60770 Accepted
[Wed Sep 30 17:12:19 2026] 127.0.0.1:60770 Closing
[Wed Sep 30 17:15:08 2026] 127.0.0.1:42252 Accepted
[Wed Sep 30 17:15:08 2026] 127.0.0.1:42252 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:15:08 2026] 127.0.0.1:42252 Closing
[Wed Sep 30 17:15:09 2026] 127.0.0.1:42260 Accepted
[Wed Sep 30 17:15:09 2026] 127.0.0.1:42260 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:15:09 2026] 127.0.0.1:42260 Closing
[Wed Sep 30 17:15:39 2026] 127.0.0.1:50440 Accepted
[Wed Sep 30 17:15:39 2026] 127.0.0.1:50440 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:15:39 2026] 127.0.0.1:50440 Closing
[Wed Sep 30 17:15:40 2026] 127.0.0.1:50444 Accepted
[Wed Sep 30 17:15:40 2026] 127.0.0.1:50444 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:15:40 2026] 127.0.0.1:50444 Closing
[Wed Sep 30 17:18:39 2026] 127.0.0.1:41194 Accepted
[Wed Sep 30 17:18:39 2026] 127.0.0.1:41194 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:18:39 2026] 127.0.0.1:41194 Closing
[Wed Sep 30 17:18:40 2026] 127.0.0.1:41202 Accepted
[Wed Sep 30 17:18:40 2026] 127.0.0.1:41202 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:18:40 2026] 127.0.0.1:41202 Closing
[Wed Sep 30 17:19:10 2026] 127.0.0.1:41778 Accepted
[Wed Sep 30 17:19:10 2026] 127.0.0.1:41778 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:19:10 2026] 127.0.0.1:41778 Closing
[Wed Sep 30 17:19:11 2026] 127.0.0.1:41784 Accepted
[Wed Sep 30 17:19:11 2026] 127.0.0.1:41784 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:19:11 2026] 127.0.0.1:41784 Closing
[Wed Sep 30 17:40:04 2026] 127.0.0.1:57276 Accepted
[Wed Sep 30 17:40:04 2026] 127.0.0.1:57276 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:40:04 2026] 127.0.0.1:57276 Closing
[Wed Sep 30 17:40:06 2026] 127.0.0.1:57282 Accepted
[Wed Sep 30 17:40:06 2026] 127.0.0.1:57282 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:40:06 2026] 127.0.0.1:57282 Closing
[Wed Sep 30 17:40:37 2026] 127.0.0.1:56662 Accepted
[Wed Sep 30 17:40:37 2026] 127.0.0.1:56662 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:40:37 2026] 127.0.0.1:56662 Closing
[Wed Sep 30 17:40:38 2026] 127.0.0.1:56672 Accepted
[Wed Sep 30 17:40:38 2026] 127.0.0.1:56672 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:40:38 2026] 127.0.0.1:56672 Closing
[Wed Sep 30 17:46:32 2026] 127.0.0.1:40226 Accepted
[Wed Sep 30 17:46:32 2026] 127.0.0.1:40226 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:46:32 2026] 127.0.0.1:40226 Closing
[Wed Sep 30 17:46:34 2026] 127.0.0.1:40232 Accepted
[Wed Sep 30 17:46:34 2026] 127.0.0.1:40232 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:46:34 2026] 127.0.0.1:40232 Closing
[Wed Sep 30 17:47:04 2026] 127.0.0.1:56956 Accepted
[Wed Sep 30 17:47:04 2026] 127.0.0.1:56956 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:47:04 2026] 127.0.0.1:56956 Closing
[Wed Sep 30 17:47:06 2026] 127.0.0.1:60390 Accepted
[Wed Sep 30 17:47:06 2026] 127.0.0.1:60390 Closed without sending a request; it was probably just an unused speculative preconnection
[Wed Sep 30 17:47:06 2026] 127.0.0.1:60390 Closing
[Wed Sep 30 17:59:05 2026] 127.0.0.1:35854 Accepted