Gladex Agent Logs

print('child=',g.get('child'))
"
=== JSON gate detail (what the dashboard row re-embeds):
status= refused code= 7
detail= 'committed file(s) fail lint (changelog): CHANGELOG.md [duplicate version 1.0.0 (first at line 3)] — fix the commit before promoting (prod is never shipped a red HEAD)'
single_line= True
child= /tmp/opencode/changelog-repro.UJpxb0/repo/tools/repo-lint
$ SB=/tmp/opencode/changelog-repro.UJpxb0
cd /data/repo
echo "=== NEW wording, real repo-lint child, real tool:"
GLADEX_REPO_DIR="$SB/repo" GLADEX_DEV_ROOT="$SB/dev" GLADEX_PROD_ROOT="$SB/prod" ./tools/promote-dev-to-prod --dry-run 2>&1 | grep -E 'LINT|DEV-SYNC|GATE'
echo "rc=${PIPESTATUS[0]}"
echo
echo "=== the parse/compile claim must be GONE here:"
GLADEX_REPO_DIR="$SB/repo" GLADEX_DEV_ROOT="$SB/dev" GLADEX_PROD_ROOT="$SB/prod" ./tools/promote-dev-to-prod --dry-run 2>&1 | grep -c 'fail to parse or compile' || true
echo
echo "=== --help exit-code contract:"
./tools/promote-dev-to-prod --help 2>&1 | grep -A3 'commit lint gate refused'
=== NEW wording, real repo-lint child, real tool:
GATE OK: VERDICT-20260925-150000-x.md (VERDICT: APPROVE), 1 verdict file(s), age 799s, all promoted trees (app/src/php, examples/workflows) unchanged since
DEV-SYNC OK: dev tree (/tmp/opencode/changelog-repro.UJpxb0/dev) matches the repo — nothing in dev would be dropped by this promotion
LINT REFUSED (exit 7): committed file(s) fail lint (changelog): CHANGELOG.md [duplicate version 1.0.0 (first at line 3)] — fix the commit before promoting (prod is never shipped a red HEAD)
rc=7

=== the parse/compile claim must be GONE here:
0

=== --help exit-code contract:
  7  commit lint gate refused the promotion (repo-lint reported a failure)
  8  ship-tree gate refused the promotion (the trees that would ship
               differ from HEAD, or git could not say)
> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -n "tests/test_promote_lint_gate.sh" tools/REGISTRY.md; echo "=== 236-246:"; sed -n '236,246p' tools/REGISTRY.md; echo "=== 292,320:"; sed -n '292,322p' tools/REGISTRY.md
474:- `tests/test_promote_lint_gate.sh` → **60 assertions**, hermetic sandbox, **6 mutations**
=== 236-246:
**Exit codes**:
- `0` - Success (promotion completed, prod healthy, or gate passed under `--dry-run`)
- `1` - General error (copy failed, build failed, service restart failed, healthcheck failed)
- `2` - Invalid arguments / usage error
- `5` - **Reviewer verdict gate refused the promotion** (prod untouched)
- `6` - **Dev-sync gate refused the promotion** (dev tree != repo, or unverifiable; prod untouched)
- `7` - **Commit lint gate refused the promotion** (HEAD does not parse/compile; prod untouched)
- `8` - **Ship-tree gate refused the promotion** (the trees this tool would rsync are not the trees the lint gate measured; prod untouched)

**Reviewer verdict gate** (STRUCTURE.md workflow step 5 — implemented 2026-09-24):
Runs **before any mutating step**, so a refused promote changes nothing.
=== 292,320:
Gate order is verdict (5) → dev-sync (6) → lint (7): the earliest refusing gate wins,
and each prints `prod untouched`. `--force` bypasses this gate too (loud stderr warning).

**Ship-tree gate** (step 0d — added 2026-09-25, CHANGELOG `[0.4.47]`):
The lint gate measures **HEAD's git blobs**; step 3 rsyncs the **worktree** of the
promoted trees. Nothing tied those two together, so a promotion could carry
uncommitted, untracked or *ignored* files to prod behind a green lint of a
**different** tree — while the report still named HEAD as the commit it shipped.
Step 0d runs `git status --porcelain --ignored -- <PROMOTED_TREES>` (read-only,
after the lint gate, before every mutating step) and refuses with **exit 8** when
the working tree differs from HEAD for those trees.

- **Scope is `PROMOTED_TREES` and nothing else**: rsync copies those paths only, so
  uncommitted work elsewhere in the repo never reaches prod and must not block a
  promotion (a gate that refuses for reasons irrelevant to what ships cries wolf).
- **`--ignored` is deliberate**: rsync copies bytes, not git's opinion of them — a
  file git would never track ships exactly like a committed one.
- **Fails closed on every state it cannot measure**: no git binary, a pathspec git
  errors on, a timeout (`GLADEX_SHIP_TIMEOUT`, default **30 s**) — a comparison that
  could not be made is not a match.
- The **true verdict is recorded before the `--force` bypass**, exactly like the
  other three gates; `--force` prints `WARNING: --force bypassing ship-tree gate: …`
  and continues.
- `gates[].child` records the git binary **only when `subprocess.run` actually
  spawned it** (a timeout names it; a `FileNotFoundError` records nothing — a path
  claimed for a child that never ran would be fabricated).
- Pure read: never mutates. Test hooks `GLADEX_GIT_BIN` (default `git` on PATH) and
  `GLADEX_SHIP_TIMEOUT`.
- `system-status`'s `promote-gates` row reports it as a fourth named gate: a
  refusal reads `ship-tree REFUSED: …` beside a commit-lint `OK`, never as
  divergence (two different questions — HEAD's blobs vs the tree rsync takes).
$ SB=/tmp/opencode/changelog-repro.UJpxb0
cd /data/repo
# make the changelog UNIQUE and break a php file instead -> the specific wording must come back
printf '# Changelog\n\n## [1.0.0] 2026-01-01\n- first\n' > "$SB/repo/CHANGELOG.md"
printf '<?php echo "unterminated\n' > "$SB/repo/app/src/php/bad.php"
cp "$SB/repo/app/src/php/bad.php" "$SB/dev/src/php/bad.php"
git -C "$SB/repo" -c user.email=x@y.invalid -c user.name=t add -A >/dev/null
git -C "$SB/repo" -c user.email=x@y.invalid -c user.name=t commit -qm "unique changelog, broken php" >/dev/null
GLADEX_REPO_DIR="$SB/repo" GLADEX_DEV_ROOT="$SB/dev" GLADEX_PROD_ROOT="$SB/prod" ./tools/promote-dev-to-prod --dry-run 2>&1 | grep -E 'LINT REFUSED'
(no output)
> build · mimo-v2.6-flash-free
$ cd /data/repo && sed -n '466,486p' tools/REGISTRY.md
(`sys.stdout.reconfigure(line_buffering=True)`, added 2026-09-24 — piped stdout used
  to be block-buffered while stderr wrote through, so an abort/refusal printed BEFORE
  the earlier-emitted "Starting promotion" line in `2>&1` captures and timestamps ran
  backwards). The sandbox ships a `dev/` tree in sync with `repo/`, the real
  `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` → **60 assertions**, hermetic sandbox, **6 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). **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`, `cannot-verify`,
  `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,
  and **section N runs the REAL `repo-lint`** against a throwaway git repo (clean
  commit → `LINT OK`; a committed PHP parse error → exit 7 naming the file). Every
  invocation uses `--dry-run`.
$ SB=/tmp/opencode/changelog-repro.UJpxb0; cd /data/repo
touch -d '2026-09-25 12:00:00' "$SB/repo/app/src/php/bad.php" "$SB/dev/src/php/bad.php" "$SB/repo/CHANGELOG.md"
GLADEX_REPO_DIR="$SB/repo" GLADEX_DEV_ROOT="$SB/dev" GLADEX_PROD_ROOT="$SB/prod" ./tools/promote-dev-to-prod --dry-run 2>&1 | grep -E 'GATE|DEV-SYNC|LINT'; echo "rc=${PIPESTATUS[0]}"
GATE OK: VERDICT-20260925-150000-x.md (VERDICT: APPROVE), 1 verdict file(s), age 821s, all promoted trees (app/src/php, examples/workflows) unchanged since
DEV-SYNC OK: dev tree (/tmp/opencode/changelog-repro.UJpxb0/dev) matches the repo — nothing in dev would be dropped by this promotion
LINT REFUSED (exit 7): committed file(s) fail to parse or compile: app/src/php/bad.php — fix the commit before promoting (prod is never shipped a red HEAD)
rc=7
> build · mimo-v2.6-flash-free
Both live branches verified. Now the docs — REGISTRY first:
$ cd /data/repo && grep -n "^## promote-dev-to-prod" tools/REGISTRY.md; sed -n "$(grep -n '^## promote-dev-to-prod' tools/REGISTRY.md | cut -d: -f1),+16p" tools/REGISTRY.md; echo "=== tail of promote section (status line):"; sed -n "$(grep -n '^## promote-dev-to-prod' tools/REGISTRY.md | cut -d: -f1),+1000p" tools/REGISTRY.md | grep -n "^\*\*Status\|^## " | head -5
217:## promote-dev-to-prod
## promote-dev-to-prod

**Purpose**: Promote dev environment to prod, behind four mandatory gates — reviewer verdict, dev-sync, commit lint, ship-tree (git checkout, build, restart).

**Location**: `/data/repo/tools/promote-dev-to-prod`

**Usage**:
```
promote-dev-to-prod [--dry-run] [--force] [--format {human,json}] [--help]
```

**Options**:
- `--dry-run` - Evaluate the gates and show planned steps without executing anything
- `--force` - Bypass **all four** gates (warns loudly on stderr; deliberate override)
- `--format {human,json}` - Output format (default `human`). `json` prints **one
  machine-readable gate report on stdout** and reroutes every human line to stderr;
  `human` stays byte-identical to before. **Exit codes are unchanged either way.**
=== tail of promote section (status line):
1:## promote-dev-to-prod
355:**Status**: Built ✅ (verdict gate implemented 2026-09-24; promoted-tree set widened to
365:## ip-drift-check
426:**Status**: Built ✅ (hardened 2026-09-24: validated answers + arg contract + first test suite)
430:## pdns-api.py
> build · mimo-v2.6-flash-free
← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -238,9 +238,9 @@
 - `1` - General error (copy failed, build failed, service restart failed, healthcheck failed)
 - `2` - Invalid arguments / usage error
 - `5` - **Reviewer verdict gate refused the promotion** (prod untouched)
 - `6` - **Dev-sync gate refused the promotion** (dev tree != repo, or unverifiable; prod untouched)
-- `7` - **Commit lint gate refused the promotion** (HEAD does not parse/compile; prod untouched)
+- `7` - **Commit lint gate refused the promotion** (repo-lint reported a failure on HEAD; prod untouched — the refusal names it, and never claims a cause the child did not report)
 - `8` - **Ship-tree gate refused the promotion** (the trees this tool would rsync are not the trees the lint gate measured; prod untouched)
 
 **Reviewer verdict gate** (STRUCTURE.md workflow step 5 — implemented 2026-09-24):
 Runs **before any mutating step**, so a refused promote changes nothing.

← Edit repo/tools/REGISTRY.md
Index: repo/tools/REGISTRY.md
===================================================================
--- repo/tools/REGISTRY.md
+++ repo/tools/REGISTRY.md
@@ -277,9 +277,11 @@
 could be promoted behind a green verdict. Step 0c runs `tools/repo-lint --format json
 --sha HEAD` (read-only, before any mutating step) and refuses with **exit 7** when:
 - at least one committed file fails to parse **or** a committed Go file does not
   compile (`failures[]` is named in the refusal — same git-blob check
-  `system-status`'s `go-compile` row reports, so the dashboard and the promote agree);
+  `system-status`'s `go-compile` row reports, so the dashboard and the promote agree)
+  **or** repo-lint's **CHANGELOG version-identity rule** fires (a repeated
+  `## [x.y.z]` token — see `repo-lint`'s own exit-1 contract);
 - `repo-lint` exits `3` (**cannot verify**: not a git repo, unknown revision, linter
   missing/timed out), exits `2`, or cannot be run at all;
 - the child's output is not readable JSON, the binary is missing, or the run exceeds
   `GLADEX_LINT_TIMEOUT` (default **240 s** — `repo-lint`'s own Go compile gate may take

> build · mimo-v2.6-flash-free
$ cd /data/repo && grep -n '^## \[' CHANGELOG.md | tail -8; echo "=== train head check (first entries):"; grep -n '^## \[' CHANGELOG.md | head -3; echo "=== promote Status line:"; grep -n "^\*\*Status\*\*: Built ✅ (verdict gate" tools/REGISTRY.md
1046:## [0.4.45] - 2026-09-25 — `promote-gates` printed the child's scan-time age as if this report's own timestamps produced it, and `4803m old` was arithmetic every reader had to do — the first two queue items from [0.4.44]
1069:## [0.4.46] - 2026-09-25 — the divergence guard watched only ONE of the three gates' children: "dev == repo" was asked twice a run (the promote gate's `dev-sync`, and `gates[].child`'s recorded `source-sync-check`) and the two answers never met — the last of [0.4.43]'s three queue items
1089:## [0.4.47] - 2026-09-25 — thirteen of the fifteen documents this app renders had no `<main>` landmark: the webmail a11y pass ([0.4.31]) was handed over twice and stayed on `/mailbox`, so "jump to main content" had nothing to jump to on the other fourteen routes
1119:## [0.4.48] - 2026-09-25 — the ship-tree gate measured a repo whose step 3 had just overwritten it: a run could pass commit-lint and promote a working tree that was dirty exactly where the product ships from
1172:## [0.4.49] - 2026-09-25 — the one gate that measures the shipped tree was the one gate nothing cross-checked: `ship-tree` could say `ok` while the tree step 3 rsyncs was dirty, and the dashboard would have printed `ship-tree OK`
1222:## [0.4.50] - 2026-09-25 — comprehensive QA verification pass: all 16 PHP test suites green
1230:## [0.4.51] - 2026-09-25 — two CHANGELOG entries claimed `0.4.49`, and every suite in the repo stayed green: `version` is the key `/api/changelog` hands its consumers, and nothing ever checked it names one entry
1263:## [0.4.52] - 2026-09-25 — the changelog uniqueness guard was a test, not a gate: nothing at RUN time could stop a second `## [0.4.49]` landing in a commit, so repo-lint now refuses any committed `CHANGELOG.md` that repeats a version token
=== train head check (first entries):
7:## [0.4.28] - 2026-09-24 — Go CLI joins the single version train: build.sh derives its version from this changelog (was a hardcoded 0.2.0), download badge + docs CLI mentions follow, all four binaries rebuilt
21:## [0.4.27] - 2026-09-24 — version drift closed: nine stale `0.3.0` literals across app+docs collapse into one `GLADEX_APP_VERSION` constant sourced from this changelog
38:## [0.4.26] - 2026-09-24 — smtp-relay-probe now ASSERTS the 220 greeting (exit 4): a one-endpoint :25-greeting regression could no longer pass green
=== promote Status line:
573:**Status**: Built ✅ (verdict gate implemented 2026-09-24; promoted-tree set widened to
> build · mimo-v2.6-flash-free

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

[Fri Sep 25 16:16:42 2026] 127.0.0.1:41180 Accepted
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41180 Closing
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41184 Accepted
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41184 Closing
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41192 Accepted
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41192 Closing
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41208 Accepted
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41208 Closing
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41218 Accepted
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41218 Closing
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41230 Accepted
[Fri Sep 25 16:16:42 2026] 127.0.0.1:41230 Closing
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42534 Accepted
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42534 Closing
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42538 Accepted
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42538 Closing
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42546 Accepted
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42546 Closing
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42560 Accepted
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42560 Closing
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42562 Accepted
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42562 Closing
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42578 Accepted
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42578 Closing
[Fri Sep 25 16:33:31 2026] 127.0.0.1:42586 Accepted
[Fri Sep 25 16:33:32 2026] 127.0.0.1:42586 Closing
[Fri Sep 25 16:51:39 2026] 127.0.0.1:54388 Accepted
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54388 Closing
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54404 Accepted
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54404 Closing
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54406 Accepted
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54406 Closing
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54420 Accepted
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54420 Closing
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54426 Accepted
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54426 Closing
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54430 Accepted
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54430 Closing
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54442 Accepted
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54442 Closing
[Fri Sep 25 16:51:40 2026] 127.0.0.1:54452 Accepted
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54452 Closing
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54466 Accepted
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54466 Closing
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54476 Accepted
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54476 Closing
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54478 Accepted
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54478 Closing
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54494 Accepted
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54494 Closing
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54502 Accepted
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54502 Closing
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54512 Accepted
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54512 Closing
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54516 Accepted
[Fri Sep 25 16:51:41 2026] 127.0.0.1:54516 Closing
[Fri Sep 25 16:53:33 2026] 127.0.0.1:51594 Accepted
[Fri Sep 25 16:53:33 2026] 127.0.0.1:51594 Closing
[Fri Sep 25 16:53:34 2026] 127.0.0.1:51596 Accepted