Gladex Agent Logs

+run_child "$D"
+assert_eq "C32e a declared non-2 code that stops being true -> exit 1" 1 "$RC"
+has_v badvalue_contract repo-lint:--sha-declared \
+  && ok "C32f VIOLATION badvalue_contract repo-lint:--sha-declared" \
+  || fail "C32f VIOLATION badvalue_contract repo-lint:--sha-declared"
+assert_contains "C32g and the red NAMES the pair and both codes, so a reader need not hunt six classes" \
+  "DIAG declared_probe repo-lint:--sha want=3 got=0" "$OUT"
+assert_eq "C32h exactly one violation - the plant, and nothing else" 1 "$(sget violations)"
+assert_eq "C32i the scope did not move: all three declared pairs were still found" \
+  3 "$(sget cl_declared)"
+assert_eq "C32j and the other two still answered, so this plant is the only difference" \
+  "$(( $(sget cl_declared) - 1 ))" "$(sget cl_declared_ok)"
+assert_eq "C32k and the partition still closes with the declared bucket in it" \
+  "$(sget cl_scope)" \
+  "$(( $(sget cl_fmt) + $(sget cl_port) + $(sget cl_enum) + $(sget cl_num) + $(sget cl_declared) + $(sget cl_other) ))"
+
 # ==========================================================================
 # D — this suite's own argv surface: the rule it enforces for everyone else.
 # ==========================================================================
 bash "$SELF" --help >/dev/null 2>&1

> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -n "31 negative controls\|enum and quantity planted together\|nine controls" tests/test_registry_coverage.sh
1119:  C  31 negative controls: each plant is proved to have taken effect first,
1141:     `usage:` row carries the label but names no flag (nine controls: a
1146:enum and quantity planted together)
> build · mimo-v2.6-flash-free
$ cd /data/repo && sed -n '1105,1150p' tests/test_registry_coverage.sh
TRUE: the tool actually exits 2 on an unrecognised flag AND on a bad value of a
flag it does define (`--format xml`, a missing `--format`, `--timeout 0` where
the table's own exit-2 bullet promises it, a value outside an enum metavar's
own list, a non-number for a quantity metavar, a missing value of any other
value-taking flag), and the
table under its section really lists that code.
It also reads the registry's own
full-regression figure: exactly one `- Live:` line may carry a suite count,
that count must equal what `regression-run --list` discovers, and every other
`<N> suites` figure must be dated, i.e. attributable history.

sections:
  A  the live tree is fully covered (the assertion this suite exists for)
  B  the counts are cross-checked against an independent recount of both inputs
  C  31 negative controls: each plant is proved to have taken effect first,
     then the SAME checker (re-executed as a child of this script) must go red
     on that specific VIOLATION line
  D  this suite's own --help
  E  the exit-code tables are true, not merely present (one bounded probe per
     tool, plus the registry bullets it claims to reflect)
  F  the regression figure is singular, dated and equal to what the tool
     discovers (five controls: missing, duplicate, stale, undated, stripped),
     and reported against BOTH counts - what is committed (`fig_head`) and what
     is checked out (`fig_disc`) - so a stale figure names the side that moved
     (queue item (83); C31 is the control, and the only one that builds a
     repository)
  G  a documented exit code 2 is also probed for a bad VALUE of a flag the tool
     really defines: `--format xml` and a missing `--format` for every tool
     whose --help advertises it, `--timeout 0` for every table whose own exit-2 bullet promises it,
     a `PORT` metavar, a value outside an ENUM metavar's own list and a
     non-number for a QUANTITY metavar (both derived from the metavar's own
     type, queue item (73)), and a missing value for every other value-taking
     flag —
     and the scope those probes read is itself checked by a third reader that
     ignores the single-space convention, so an option line written
     `--flag  TOKEN` cannot drop out of every reader at once, and a tool whose
     `usage:` row carries the label but names no flag (nine controls: a
     swallowed value, a table that starts promising it, a swallowed port, a
     swallowed missing value, an invisible option line, a promise written without
the flag token, an option line whose description starts on the very next space,
a synopsis that names no flag, and a value its metavar's own type rules out —
enum and quantity planted together)

hooks (env): REGISTRY_COVERAGE_TOOLS_DIR, REGISTRY_COVERAGE_REGISTRY,
             REGISTRY_COVERAGE_TESTS_DIR, REGISTRY_COVERAGE_CHILD (internal)
> build · mimo-v2.6-flash-free
← Edit repo/tests/test_registry_coverage.sh
Index: repo/tests/test_registry_coverage.sh
===================================================================
--- repo/tests/test_registry_coverage.sh
+++ repo/tests/test_registry_coverage.sh
@@ -1115,9 +1115,9 @@
 
 sections:
   A  the live tree is fully covered (the assertion this suite exists for)
   B  the counts are cross-checked against an independent recount of both inputs
-  C  31 negative controls: each plant is proved to have taken effect first,
+  C  32 negative controls: each plant is proved to have taken effect first,
      then the SAME checker (re-executed as a child of this script) must go red
      on that specific VIOLATION line
   D  this suite's own --help
   E  the exit-code tables are true, not merely present (one bounded probe per

> build · mimo-v2.6-flash-free
← Edit repo/tests/test_registry_coverage.sh
Index: repo/tests/test_registry_coverage.sh
===================================================================
--- repo/tests/test_registry_coverage.sh
+++ repo/tests/test_registry_coverage.sh
@@ -1132,10 +1132,13 @@
      really defines: `--format xml` and a missing `--format` for every tool
      whose --help advertises it, `--timeout 0` for every table whose own exit-2 bullet promises it,
      a `PORT` metavar, a value outside an ENUM metavar's own list and a
      non-number for a QUANTITY metavar (both derived from the metavar's own
-     type, queue item (73)), and a missing value for every other value-taking
-     flag —
+     type, queue item (73)), the three pairs DECLARED to answer a documented
+     non-2 code for a value their metavar's type rejects (queue item (98),
+     exact codes where the code is a property of the argument and `non2`
+     where it is a property of the environment), and a missing value for every
+     other value-taking flag —
      and the scope those probes read is itself checked by a third reader that
      ignores the single-space convention, so an option line written
      `--flag  TOKEN` cannot drop out of every reader at once, and a tool whose
      `usage:` row carries the label but names no flag (nine controls: a

> build · mimo-v2.6-flash-free
← Edit repo/tests/test_registry_coverage.sh
Index: repo/tests/test_registry_coverage.sh
===================================================================
--- repo/tests/test_registry_coverage.sh
+++ repo/tests/test_registry_coverage.sh
@@ -1140,14 +1140,15 @@
      other value-taking flag —
      and the scope those probes read is itself checked by a third reader that
      ignores the single-space convention, so an option line written
      `--flag  TOKEN` cannot drop out of every reader at once, and a tool whose
-     `usage:` row carries the label but names no flag (nine controls: a
+     `usage:` row carries the label but names no flag (ten controls: a
      swallowed value, a table that starts promising it, a swallowed port, a
      swallowed missing value, an invisible option line, a promise written without
 the flag token, an option line whose description starts on the very next space,
-a synopsis that names no flag, and a value its metavar's own type rules out —
-enum and quantity planted together)
+a synopsis that names no flag, a value its metavar's own type rules out —
+enum and quantity planted together — and a DECLARED non-2 code that stops
+being true, C32)
 
 hooks (env): REGISTRY_COVERAGE_TOOLS_DIR, REGISTRY_COVERAGE_REGISTRY,
              REGISTRY_COVERAGE_TESTS_DIR, REGISTRY_COVERAGE_CHILD (internal)
 

> build · mimo-v2.6-flash-free
$ cd /data/repo && bash -n tests/test_registry_coverage.sh && echo "syntax OK" && timeout 900 bash tests/test_registry_coverage.sh > /tmp/opencode/regcov98.log 2>&1; echo "exit=$?"; tail -5 /tmp/opencode/regcov98.log; echo "=== FAILs ==="; grep -c "^FAIL" /tmp/opencode/regcov98.log; grep "^FAIL" /tmp/opencode/regcov98.log | head -30; echo "=== new assertions ==="; grep -E "^PASS: G3[5-9]|^PASS: C32" /tmp/opencode/regcov98.log
syntax OK
exit=1
FAIL: G37 and every one of the three still answers what DECLARED_PAIRS declares (3, 3, and never 2) (want=3 got=0)
PASS: G38 and the three left cl_other rather than being counted twice
PASS: G39 and the codes the three probes actually returned are printed for a reader to watch

=== Results: 242 passed, 38 failed ===
=== FAILs ===
38
FAIL: A1 live tree: checker exits 0 (fully covered) (want=0 got=1)
FAIL: A3 live tree: zero violations (want=0 got=3)
FAIL: C1e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C2e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C3e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C4e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C5d exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C6d exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C7d exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C8e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C9e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C14f exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C15f exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C16g exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C17e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C18e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C19e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C20e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C21h exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C22e exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C23h exactly two violations - the two plants, and nothing else (want=2 got=5)
FAIL: C24f exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C25f exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C25g the older classes all stay green (one plant, one finding) (unexpected: VIOLATION badvalue_contract)
FAIL: C26f exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C27f exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C27g the older classes all stay green (one plant, one finding) (unexpected: VIOLATION badvalue_contract)
FAIL: C28f exactly one violation - the plant, and nothing else (want=1 got=4)
FAIL: C29j exactly two violations - the two plants, and nothing else (want=2 got=5)
FAIL: C30g exactly one violation - the plant, and nothing else (want=1 got=4)
=== new assertions ===
PASS: C32a plant: an unknown revision really now reports 0 - the non-verdict reads as clean
PASS: C32b plant: while --help is untouched (this is not an E plant)
PASS: C32c plant: and an unknown flag still exits 2, so E has nothing to find
PASS: C32d plant: and a bad --format value still exits 2, so the (65) class stays silent
PASS: C32e a declared non-2 code that stops being true -> exit 1
PASS: C32i the scope did not move: all three declared pairs were still found
PASS: C32k and the partition still closes with the declared bucket in it
PASS: G35 the live snapshot carries the (98) declared-contract keys
PASS: G36 exactly three pairs are declared non-2 (repo-lint --sha, immich-roundtrip --email, smtp-relay-probe --expect-open)
PASS: G38 and the three left cl_other rather than being counted twice
PASS: G39 and the codes the three probes actually returned are printed for a reader to watch
> build · mimo-v2.6-flash-free
$ cd /data/repo && bash -n tests/test_registry_coverage.sh && echo SYNTAX_OK; ( time bash tests/test_registry_coverage.sh ) > /tmp/opencode/regcov98.log 2>&1; echo "EXIT=$?"; grep -E "^(FAIL|  -)" /tmp/opencode/regcov98.log | head -20; tail -8 /tmp/opencode/regcov98.log; grep -E "^(real|user|sys)" /tmp/opencode/regcov98.log
SYNTAX_OK


Command exceeded timeout of 120000 ms. Retry with a larger timeout if the command is expected to take longer.

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

[Thu Oct  1 04:56:17 2026] 127.0.0.1:44798 Accepted
[Thu Oct  1 04:56:17 2026] 127.0.0.1:44798 Closing
[Thu Oct  1 04:56:17 2026] 127.0.0.1:44806 Accepted
[Thu Oct  1 04:56:17 2026] 127.0.0.1:44806 Closing
[Thu Oct  1 04:56:17 2026] 127.0.0.1:44814 Accepted
[Thu Oct  1 04:56:17 2026] 127.0.0.1:44814 Closing
[Thu Oct  1 04:56:17 2026] 127.0.0.1:44816 Accepted
[Thu Oct  1 04:56:18 2026] 127.0.0.1:44816 Closing
[Thu Oct  1 04:56:18 2026] 127.0.0.1:44830 Accepted
[Thu Oct  1 04:56:18 2026] 127.0.0.1:44830 Closing
[Thu Oct  1 04:56:18 2026] 127.0.0.1:44844 Accepted
[Thu Oct  1 04:56:18 2026] 127.0.0.1:44844 Closing
[Thu Oct  1 04:56:18 2026] 127.0.0.1:44850 Accepted
[Thu Oct  1 04:56:18 2026] 127.0.0.1:44850 Closing
[Thu Oct  1 04:56:59 2026] 127.0.0.1:56966 Accepted
[Thu Oct  1 04:56:59 2026] 127.0.0.1:56966 Closing
[Thu Oct  1 04:57:29 2026] 127.0.0.1:45548 Accepted
[Thu Oct  1 04:57:29 2026] 127.0.0.1:45548 Closing
[Thu Oct  1 05:03:39 2026] 127.0.0.1:34924 Accepted
[Thu Oct  1 05:03:39 2026] 127.0.0.1:34924 Closing
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53704 Accepted
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53704 Closing
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53712 Accepted
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53712 Closing
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53726 Accepted
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53726 Closing
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53742 Accepted
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53742 Closing
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53758 Accepted
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53758 Closing
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53766 Accepted
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53766 Closing
[Thu Oct  1 05:09:53 2026] 127.0.0.1:53780 Accepted
[Thu Oct  1 05:09:54 2026] 127.0.0.1:53780 Closing
[Thu Oct  1 05:09:54 2026] 127.0.0.1:53796 Accepted
[Thu Oct  1 05:09:54 2026] 127.0.0.1:53796 Closing
[Thu Oct  1 05:09:54 2026] 127.0.0.1:53798 Accepted
[Thu Oct  1 05:09:54 2026] 127.0.0.1:53798 Closing
[Thu Oct  1 05:09:54 2026] 127.0.0.1:41328 Accepted
[Thu Oct  1 05:09:54 2026] 127.0.0.1:41328 Closing
[Thu Oct  1 05:26:46 2026] 127.0.0.1:44790 Accepted
[Thu Oct  1 05:26:46 2026] 127.0.0.1:44790 Closing
[Thu Oct  1 05:26:46 2026] 127.0.0.1:44804 Accepted
[Thu Oct  1 05:26:46 2026] 127.0.0.1:44804 Closing
[Thu Oct  1 05:36:42 2026] 127.0.0.1:34608 Accepted
[Thu Oct  1 05:36:42 2026] 127.0.0.1:34608 Closed without sending a request; it was probably just an unused speculative preconnection
[Thu Oct  1 05:36:42 2026] 127.0.0.1:34608 Closing
[Thu Oct  1 05:36:44 2026] 127.0.0.1:34616 Accepted
[Thu Oct  1 05:36:44 2026] 127.0.0.1:34616 Closed without sending a request; it was probably just an unused speculative preconnection
[Thu Oct  1 05:36:44 2026] 127.0.0.1:34616 Closing
[Thu Oct  1 05:37:16 2026] 127.0.0.1:38506 Accepted
[Thu Oct  1 05:37:16 2026] 127.0.0.1:38506 Closed without sending a request; it was probably just an unused speculative preconnection
[Thu Oct  1 05:37:16 2026] 127.0.0.1:38506 Closing
[Thu Oct  1 05:37:17 2026] 127.0.0.1:38522 Accepted
[Thu Oct  1 05:37:17 2026] 127.0.0.1:38522 Closed without sending a request; it was probably just an unused speculative preconnection
[Thu Oct  1 05:37:17 2026] 127.0.0.1:38522 Closing
[Thu Oct  1 05:40:50 2026] 127.0.0.1:53628 Accepted
[Thu Oct  1 05:40:50 2026] 127.0.0.1:53628 Closing
[Thu Oct  1 05:41:49 2026] 127.0.0.1:36132 Accepted