Gladex Agent Logs

2115:**Status**: Built ✅ (2026-09-24; closes the "live relay probe blocked by :25-greeting bug" follow-up — 220 banner verified answering on :25 via 40/40 probes + nc + strace, live relay probe exit 0)
2165:**Status**: Built ✅ (2026-09-24; first live run caught 16 drifted workflow files — see CHANGELOG 0.4.25)
2270:**Status**: Green ✅ 2026-09-27 (122/122; closes `[0.4.66]`'s queue item (1) and
2302:**Status**: Green ✅ 2026-09-24 (28/28 twice: clean run + concurrent-shift decoy run)
2327:**Status**: Green ✅ 2026-09-26 (48/48; pre-fix replay against the committed suite — md5 `b9d7dcd3c2aa159c33f5f7144cdbfb5a`, suite md5 `261ad2b7608334b20743bfa25b926bcb`, `/tmp/opencode/contrastfix/pre-fix-final.log` — → **33 passed / 15 failed**, and 33 + 15 = 48 closes exactly; mutations **M1** else dropped → caught by 10, **M2** guard weakened → caught by 9, all inside **F2** because **F1 cannot distinguish the two guards**)
2402:**Status**: Green ✅ 2026-09-27 (**348/348**; full regression **52 suites / 4267 assertions / 0 failed / 0 skipped, exit 0** — 29 shell = 2892, 23 PHP = 1375. Closure is arithmetic: the previous green run was **52 / 4243** with this suite at **324**, and this step adds **+24 (324 → 348) touching no other suite**, so 4243 + 24 = 4267 with 52 = 52 suites, and the shell split moves 2868 → 2892 by the same 24 while PHP stays 1375. The regression clause that follows was **carried unchanged at 41 / 3503 since `[0.4.67]`** — the tree had already reached 52 / 4210 by `[0.4.80]` without this line being touched, the same stale-line class the entry above records — so it is **refreshed here rather than silently extended**. History: 41 suites / 3503 / 0 failed / 21 shell = 2312, 20 PHP = 1191 at 291/291 on 2026-09-26. Was 40 / 3396 / 20 shell = 2205 with `[0.4.66]`; **`[0.4.67]` adds `tests/test_queue_source.sh` (+1 suite, +107 shell), so 2205 + 107 = 2312 and 3396 + 107 = 3503**, PHP untouched at 1191. Before that, `[0.4.66]` grew `tests/test_regression_run.sh` (+0 suites, +83 shell: 110 → 193), so 2122 + 83 = 2205 and 3313 + 83 = 3396, and `[0.4.65]` added that suite (+1 suite, +110 shell) — 2012 + 110 = 2122, 3203 + 110 = 3313. This line was itself two runs stale at `[0.4.64]` — `[0.4.63]` added `test_app_contrast.php` (+1, +185) without updating it, so 958 + 185 + 48 = 1191 and 2970 + 185 + 48 = 3203 came out then)
2460:**Status**: Built ✅ 2026-09-26 (193/193; closes `[0.4.65]`'s PROGRESS queue item (1); full regression 41 suites / 3503 assertions / 0 failed)
2489:**Status**: Green ✅ 2026-09-26 (193/193)
2562:**Status**: Green ✅ 2026-09-27 (122/122; pre-fix replay of `HEAD`'s tool → 109
2653:**Status**: Green ✅ 2026-09-26 (91/91; closes `[0.4.67]`'s queue item (11);
=== around promote entry start ===
235:## promote-dev-to-prod
written right now). `LINT_STUB_SLEEP` (env, test-only) sleeps the lint gate so a
suite can prove the age covers gate time: a scan-time age would read 0.

**`GLADEX_GATE_PROBE=1` forces `--dry-run` inside `main()`** — defence in depth, so a
dashboard caller asking for a JSON report cannot promote anything even if it forgets
`--dry-run`: two independent pins (`--dry-run` **and** the probe) must both fail. The
`promote-gates` row on `system-status` sets both. `--force` is what a *reader* needs,
because a plain `--dry-run` stops at the first refusing gate and would report only one
gate instead of all four; forcing changes behaviour, never reporting.

**Promoted trees** — one list (`PROMOTED_TREES`) drives **both** the rsync loop and
the freshness check, so "what we ship" and "what we staleness-check" cannot drift:

| repo | env | why |
|---|---|---|
| `app/src/php` | `src/php` | served app code |
| `examples/workflows` | `examples/workflows` | public `/templates` gallery — the **env copy shadows the repo** (`templates.php` candidate 1) |

Kept in step with `source-sync-check`, which compares exactly these two trees; a
test asserts the sets match. `tools/` is deliberately **not** promoted — promote only
*executes* `tools/healthcheck` to verify prod and never deploys it, so editing a tool
cannot change what prod serves.

**Operation**:
0. Reviewer verdict gate (above) — refuses with exit 5 before touching anything
0b. Dev-sync gate (above) — refuses with exit 6 before touching anything
0c. Commit lint gate (above) — refuses with exit 7 before touching anything
0d. Ship-tree gate (above) — refuses with exit 8 before touching anything
1. Checks git status at `/data/repo`
2. rsyncs **each** promoted tree into prod (`app/src/php` → `src/php`,
   `examples/workflows` → `examples/workflows`, both `--delete`)
> build · mimo-v2.6-flash-free
→ Read repo/tools/REGISTRY.md [limit=20, offset=714]
> build · mimo-v2.6-flash-free
→ Read repo/tools/REGISTRY.md [limit=16, offset=733]
> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -540,9 +540,9 @@
   `source-sync-check` **and a clean `repo-lint` stub** (since 2026-09-24 this suite
   pins only the verdict/dev-sync gates; the lint gate has its own suite), so the
   dev-sync gate is exercised for real. Every invocation
   uses `--dry-run`, so the suite can never restart the live prod service.
-- `tests/test_promote_lint_gate.sh` → **161 assertions**, hermetic sandbox, **14 mutations**
+- `tests/test_promote_lint_gate.sh` → **189 assertions**, hermetic sandbox, **16 mutations**
   all caught (gate result ignored; refusal exiting 0; exit code trusted over the
   child's JSON; timeout handler re-raising — a hang crashes instead of refusing;
   timeout bound removed; `--force` bypass removed; **every `failures[].lang` read as
   a syntax rule — `[0.4.53]`'s own defect, planted; the empty-kind fallback dropped;
@@ -551,18 +551,23 @@
   silent failure grows an invented reason)**, and **the pre-fix one-failure-only
   rule restored** — M10/M11/M12; **`[0.4.55]`'s — the changelog rule dropped from
   the `--help` prose, i.e. the defect itself, planted — M13**; **`[0.4.92]`'s — the
   mixed exit-3 refusal's verified half dropped from the parent's detail, i.e. the
-  defect itself, planted — M14**). **Since `[0.4.47]` the sandbox is
+  defect itself, planted — M14**; **`[0.4.93]`'s two — the exit-3 bound's
+  `(+N more)` announcement dropped, and the `errors[]` dict branch dropped so every
+  cause falls back to `str(e)`, i.e. one half of the defect each — M15/M16**). **Since `[0.4.47]` the sandbox is
   a real git repo too** (`git init` + baseline commit in the fixture): without it the
   ship-tree gate that now runs *after* this suite's own gate fails closed and every
   scenario reports 8 instead of 0. Scenario `repo-lint` stub emitting
   the real child's JSON shapes (`ok`, `php-fail`, `go-broken`, `changelog-dup`,
   `mixed-langs`, `rc1-no-lang`, `rc1-empty`, **`multi-reasons`** (three failures,
   one message-less — attribution and the never-invent-a-reason rule), **`many-reasons`**
   (seven, mixed rules — the shared 5-failure bound), `cannot-verify`,
   **`cannot-verify-mixed`** (exit 3 carrying `errors[]` *and* two `failures[]`,
-  one of them a rule), `usage`, `garbage`, `rc0-not-ok`, `hang`), a static assertion that the gate call
+  one of them a rule), **`cannot-verify-many`** (exit 3, **four dict-shaped
+  `errors[]` entries** + one failure — the real payload shape, the bound and the
+  marker) and **`cannot-verify-three`** (three dicts — the off-by-one the bound
+  rests on), `usage`, `garbage`, `rc0-not-ok`, `hang`), a static assertion that the gate call
   precedes the copy loop, gate-order checks (5 and 6 outrank 7), `--help` contract
   (including that exit 7 no longer promises *only* a syntax failure, and — **since
   `[0.4.55]`, section J-b** — that the *Commit lint gate* prose states **all three**
   of repo-lint's rules on whitespace-flattened help, names

> build · mimo-v2.6-flash-free
✗ Edit repo/tools/REGISTRY.md failed
Error: Could not find oldString in /data/repo/tools/REGISTRY.md. It must match exactly, including whitespace and indentation.
> build · mimo-v2.6-flash-free
$ cd /data/repo && sed -n '592,600p' tools/REGISTRY.md | cat -A | cut -c1-80
**Section N4** (`[0.4.92]`) pins the **mixed exit-3 refusal**: the unverifiabl
  half still reported, the *verified* half reaching the verdict too (both files,
  `fail lint (changelog, php)`, a reason attributed to its own file), the two$
  halves in **one** string in that order M-bM-^@M-^T errors first, verdict appen
  refusal still ending in `fix the commit before promoting`, and, on the pure$
  `cannot-verify` shape, **no** failure verdict, **no** parse/compile claim and$
  **no** file named that the child never judged (the boundary that keeps$
  "cannot verify" from becoming a verdict of its own).$
  **Pre-fix replay**$
> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -596,8 +596,18 @@
   refusal still ending in `fix the commit before promoting`, and, on the pure
   `cannot-verify` shape, **no** failure verdict, **no** parse/compile claim and
   **no** file named that the child never judged (the boundary that keeps
   "cannot verify" from becoming a verdict of its own).
+  **Section N5** (`[0.4.93]`) pins the **shape and the bound of the exit-3
+  causes**: a dict-shaped `errors[]` entry — the payload the child *really*
+  sends, since `lint()`, the Go compile gate and the changelog gate all return
+  `{"path","lang","error"}` — rendered as `path: error` with **no** Python repr
+  (`{'path' …`) anywhere in the refusal; the fourth cause stopped at the bound
+  **and announced** with `(+1 more)`, in one string with the appended verdict
+  half (`… (+1 more), and committed file(s) fail to parse or compile: …`); the
+  off-by-one checked both ways (**three** causes all shown and *not* marked
+  truncated); and the plain-**string** fallback every older stub emits left
+  byte-equal to what it printed before the helper existed.
   **Pre-fix replay**
   (tool md5 `106cabca1bed13a0554f6a7e27d2b10f`, log
   `/tmp/opencode/lintgate-pre-fix.log`) → **73 passed / 17 failed**: 14 behavioural
   (`--help` ×2, live N-b ×3, N2 ×9) plus **M7–M9 unplantable** (`plant matched 0

> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -638,9 +638,21 @@
   not exist yet), while every N4 *guard* passed pre-fix and identifies itself as
   such: exit 7, the unverifiable half still reported, `cannot verify the
   committed tree`, `fix the commit before promoting`, and the not-dropped-in-
   exchange needle — **151 + 5 = 156 = 161 − 6 (M14's body never ran) + 1 (the
-  setup failure)**, so the two runs close exactly. Every invocation uses `--dry-run`.
+  setup failure)**, so the two runs close exactly. **Pre-fix replay for
+  `[0.4.93]`** (tool md5 `0c93193cff93238c85f7dcd789548581`, log
+  `/tmp/opencode/pre-fix-replay-37.log`) → **169 passed / 9 failed**: 7
+  behavioural (N5's `path: error` quote, the repr-absent needle, the second and
+  third cause rendered, the `(+1 more)` announcement, the bound-then-verdict
+  order pin, and the three-cause "third shown") plus **M15 and M16
+  unplantable** (`plant matched 0 line(s)` — neither line existed yet), while
+  every N5 *guard* passed pre-fix and identifies itself: the three exit-7
+  assertions, both "fourth cause stops at the bound" checks (the old code
+  dropped it too — silently, which is the defect, not the drop), `fix the
+  commit before promoting`, the string-fallback pass-through and both
+  no-marker-on-a-short-list checks. **169 + 9 = 178 = 189 − 13 (M15's 7 +
+  M16's 6 bodies never ran)**, so the two runs close exactly. Every invocation uses `--dry-run`.
 
   Live transcript (real `repo-lint` child, real tool, throwaway repo): the changelog
   case → `LINT REFUSED (exit 7): committed file(s) fail lint (changelog): CHANGELOG.md
   [CHANGELOG.md: duplicate version 1.0.0 (first at line 3)]` (attributed since

> build · mimo-v2.6-flash-free
✗ Edit repo/tools/REGISTRY.md failed
Error: Could not find oldString in /data/repo/tools/REGISTRY.md. It must match exactly, including whitespace and indentation.
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -n "0.4.92\]\`\*\*)" tools/REGISTRY.md | head; sed -n '755,765p' tools/REGISTRY.md | cat -A | cut -c1-100
767:— 2026-09-27, CHANGELOG `[0.4.92]`**)
every tree the envs serve 2026-09-24; dev-sync gate added 2026-09-24; stdout$
line-buffering/output-order fix 2026-09-24; commit lint gate added 2026-09-24;$
`--format json` gate report + `GLADEX_GATE_PROBE` added 2026-09-25; per-gate$
`child` path and `mailbox` evidence fields added 2026-09-25; `mailbox.age_seconds`$
re-dated from the report's own `timestamp` 2026-09-25, CHANGELOG `[0.4.45]`;$
**ship-tree gate (exit 8) added 2026-09-25, CHANGELOG `[0.4.47]`**; exit-7 refusal$
worded from `failures[].lang` instead of assumed from the exit code 2026-09-25,$
CHANGELOG `[0.4.53]`; exit-7 reasons attributed per file (`path: message`, never a$
bare reason) 2026-09-25, CHANGELOG `[0.4.54]`; **the `--help`/docstring commit-lint prose widened to
of repo-lint's rules, with `tools/repo-lint --help` named as the list's home, 2026-09-25,$
CHANGELOG `[0.4.55]`**; **exit-3 refusal widened to carry BOTH halves of a mixed$
> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -763,9 +763,11 @@
 bare reason) 2026-09-25, CHANGELOG `[0.4.54]`; **the `--help`/docstring commit-lint prose widened to all three
 of repo-lint's rules, with `tools/repo-lint --help` named as the list's home, 2026-09-25,
 CHANGELOG `[0.4.55]`**; **exit-3 refusal widened to carry BOTH halves of a mixed
 payload — the `errors[]` that could not be checked AND the `failures[]` judged red
-— 2026-09-27, CHANGELOG `[0.4.92]`**)
+— 2026-09-27, CHANGELOG `[0.4.92]`; **exit-3 causes quoted as `path: error`
+instead of a Python repr of the dict, and bounded at 3 with ` (+N more)` so a
+fourth cause never vanishes silently 2026-09-27, CHANGELOG `[0.4.93]`**)
 
 ---
 
 ## ip-drift-check

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

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

[Sun Sep 27 18:01:33 2026] 127.0.0.1:37912 Accepted
[Sun Sep 27 18:01:33 2026] 127.0.0.1:37912 Closing
[Sun Sep 27 18:01:33 2026] 127.0.0.1:37918 Accepted
[Sun Sep 27 18:01:33 2026] 127.0.0.1:37918 Closing
[Sun Sep 27 18:01:34 2026] 127.0.0.1:37926 Accepted
[Sun Sep 27 18:01:34 2026] 127.0.0.1:37926 Closing
[Sun Sep 27 18:01:35 2026] 127.0.0.1:43362 Accepted
[Sun Sep 27 18:01:35 2026] 127.0.0.1:43362 Closing
[Sun Sep 27 18:01:35 2026] 127.0.0.1:43374 Accepted
[Sun Sep 27 18:01:35 2026] 127.0.0.1:43374 Closing
[Sun Sep 27 18:01:36 2026] 127.0.0.1:43384 Accepted
[Sun Sep 27 18:01:36 2026] 127.0.0.1:43384 Closing
[Sun Sep 27 18:01:37 2026] 127.0.0.1:43394 Accepted
[Sun Sep 27 18:01:37 2026] 127.0.0.1:43394 Closing
[Sun Sep 27 18:01:38 2026] 127.0.0.1:43408 Accepted
[Sun Sep 27 18:01:38 2026] 127.0.0.1:43408 Closing
[Sun Sep 27 18:01:38 2026] 127.0.0.1:43418 Accepted
[Sun Sep 27 18:01:38 2026] 127.0.0.1:43418 Closing
[Sun Sep 27 18:01:39 2026] 127.0.0.1:43428 Accepted
[Sun Sep 27 18:01:39 2026] 127.0.0.1:43428 Closing
[Sun Sep 27 18:01:40 2026] 127.0.0.1:43444 Accepted
[Sun Sep 27 18:01:40 2026] 127.0.0.1:43444 Closing
[Sun Sep 27 18:01:41 2026] 127.0.0.1:43460 Accepted
[Sun Sep 27 18:01:41 2026] 127.0.0.1:43460 Closing
[Sun Sep 27 18:01:41 2026] 127.0.0.1:43472 Accepted
[Sun Sep 27 18:01:41 2026] 127.0.0.1:43472 Closing
[Sun Sep 27 18:01:42 2026] 127.0.0.1:43482 Accepted
[Sun Sep 27 18:01:42 2026] 127.0.0.1:43482 Closing
[Sun Sep 27 18:01:42 2026] 127.0.0.1:43486 Accepted
[Sun Sep 27 18:01:42 2026] 127.0.0.1:43486 Closing
[Sun Sep 27 18:01:43 2026] 127.0.0.1:43500 Accepted
[Sun Sep 27 18:01:43 2026] 127.0.0.1:43500 Closing
[Sun Sep 27 18:01:44 2026] 127.0.0.1:43502 Accepted
[Sun Sep 27 18:01:44 2026] 127.0.0.1:43502 Closing
[Sun Sep 27 18:01:45 2026] 127.0.0.1:45838 Accepted
[Sun Sep 27 18:01:45 2026] 127.0.0.1:45838 Closing
[Sun Sep 27 18:01:45 2026] 127.0.0.1:45844 Accepted
[Sun Sep 27 18:01:45 2026] 127.0.0.1:45844 Closing
[Sun Sep 27 18:01:46 2026] 127.0.0.1:45852 Accepted
[Sun Sep 27 18:01:46 2026] 127.0.0.1:45852 Closing
[Sun Sep 27 18:01:46 2026] 127.0.0.1:45866 Accepted
[Sun Sep 27 18:01:46 2026] 127.0.0.1:45866 Closing
[Sun Sep 27 18:01:47 2026] 127.0.0.1:45880 Accepted
[Sun Sep 27 18:01:47 2026] 127.0.0.1:45880 Closing
[Sun Sep 27 18:01:48 2026] 127.0.0.1:45886 Accepted
[Sun Sep 27 18:01:48 2026] 127.0.0.1:45886 Closing
[Sun Sep 27 18:01:49 2026] 127.0.0.1:45892 Accepted
[Sun Sep 27 18:01:49 2026] 127.0.0.1:45892 Closing
[Sun Sep 27 18:01:49 2026] 127.0.0.1:45904 Accepted
[Sun Sep 27 18:01:49 2026] 127.0.0.1:45904 Closing
[Sun Sep 27 18:01:50 2026] 127.0.0.1:45914 Accepted
[Sun Sep 27 18:01:50 2026] 127.0.0.1:45914 Closing
[Sun Sep 27 18:01:51 2026] 127.0.0.1:45918 Accepted
[Sun Sep 27 18:01:51 2026] 127.0.0.1:45918 Closing
[Sun Sep 27 18:01:52 2026] 127.0.0.1:45928 Accepted
[Sun Sep 27 18:01:52 2026] 127.0.0.1:45928 Closing
[Sun Sep 27 18:01:52 2026] 127.0.0.1:45936 Accepted
[Sun Sep 27 18:01:52 2026] 127.0.0.1:45936 Closing
[Sun Sep 27 18:08:45 2026] 127.0.0.1:58028 Accepted