Gladex Agent Logs

- **The defect, the fix, and the one condition the queue did not name.** Step 3 reads the checker **twice**: once before the `rsync` (to size the drift) and once after (to prove the copy landed). The pre-copy read has always split *couldn't run it* / *ran but couldn't verify* / *ran and it disagreed* — `if rc is None or rc not in (0, 1): refuse(EXIT_CANNOT, …)` — while the post-copy read collapsed all three into `if rc is None or rc != 0:` → exit **6**, `dev still differs from the repo after the copy (rc=None)`. Fixed to mirror its twin: **`rc is None` → 3**, `source-sync-check could not be run: …`; **`rc not in (0, 1)` → 3**, `source-sync-check could not verify the copy (rc=…)`; **`rc == 1` → 6**, old detail byte-for-byte. **Scope disclosure (this is an extension of the queued item, stated as such, not smuggled in):** the queue named only `rc is None`. Before writing, the *same line* was probed with a stand-in exiting **3** on the post-copy read — `source-sync-check`'s own *"a compared base directory does not exist"* — and it produced `dev-sync | refused | dev still differs from the repo after the copy (rc=3)` at exit **6** while `cmp` in that same probe showed dev **byte-identical** to the repo: the identical false claim one condition over, in the expression being edited. Folding it in was what made this run's own EPILOG line `6` true, so it is disclosed rather than presented as the queue's. Neither exit-3 branch carries `reason`. EPILOG `3` now enumerates the steps (`dev-sync (before AND after the copy)` included), EPILOG `6` reads *"the post-copy re-read ran and answered 1, i.e. it compared the trees and they differ (a child that could not run, or ran without verifying, is 3)"*, and the module docstring's step-3 row states both outcomes. Version **1.2.0 → 1.3.0** (not a JSON-shape change — no key appears or disappears — but an exit-code move for two cases).

- **The suite: F8–F8n, 118 → 132, and why the control is the load-bearing half.** *Unrunnable half (F8–F8h):* the stand-in reports drift once (so the copy branch runs) and `rm -f`s its own path on the way out, so the *second* exec fails outright — exit `3` not `6`; refusing step `dev-sync`; detail `source-sync-check could not be run`; **no** `still differs from the repo`; **no** `"reason"`; `exit_code` equals the process rc; **dev byte-identical to the repo at the moment of refusal** (the fact the old detail denied, and the assertion that makes this a test of the defect rather than of a string); the path really is gone. *Ran-but-could-not-verify half (F8l–F8n):* same shape, stand-in answers drift then its own `3` — exit `3`, `source-sync-check could not verify the copy`, dev == repo again. *Control (F8i–F8k):* the identical run with `SHIFT_DEPLOY_TEST_BREAK` pointed at a path nothing uses gets a re-read that runs, compares and still reports drift → it must stay exit **6**, keep `dev still differs from the repo after the copy`, and must **not** wear either new wording — which is what stops the wording assertions from being satisfiable by the harness alone, and what proves exit 6 did not vanish with the fix. `bash tests/test_shift_deploy.sh` → **132 passed / 0 failed, rc 0**, and **118/0 with the code change already in and no assertion added yet** — the fix reddens nothing the old behaviour satisfied.

- **Non-vacuity: one out-of-suite mutant, 6 signal reds.** Full `tools/`+`tests/` copy under `/tmp/opencode/mutroot_sdep_r939m1` with **both** new branches collapsed back into the single exit-6 arm: **117 passed / 10 failed → 6 signal reds: F8** (`want rc=3 got=6`), **F8c** (missing wording), **F8d** (false claim present), **F8f** (`exit_code` 6 not 3), **F8l** (`want rc=3 got=6`), **F8m** (missing cannot-verify wording) — each an assertion of this change and nothing else — plus the already-documented **B6 quartet** (mutant root has no `.git`, live layer refuses exit 3; harness artifact, disclosed, not counted). Live `tools/shift-deploy` md5 **`b8c96f2cc849c00c75fd100837b640ae`** read **identical before the mutant run and after it** — the mutation lived entirely under `/tmp/opencode`. Two separate probes were written out of tree for this run (`/tmp/opencode/postcopy_rc3_probe` for the rc=3 measurement above); **no `rm` outside `/tmp/opencode`**.

- **Docs and figures, all re-read on this tree, in the same commit as the code (A28's pairing).** `tools/REGISTRY.md` § `shift-deploy`: the step-3 table row's refusal column (the row now records that the checker is read twice), the `3` exit-code row, the `6` row (**a comparison since `[0.4.335]`, never an inference**), the `9` row's *Known residual* note rewritten as measured-and-closed, the `Tests` figure **118 → 132** (both places), and a dated **Changed** line. `CHANGELOG.md` gained bottom entry **`## [0.4.335] - 2026-10-13`** with Added / Verification / Notes / pointer-only Queue — written **twice**: the first draft used an ASCII ` - ` after the date, which the app's own parser regex (`^## \\[(.+?)\\] - (\\d{4}-\\d{2}-\\d{2})(?:\\s*—\\s*(.+))?$`) silently dropped, so `test_changelog_api.php` went **84 / 2** (`heading count == API entry count (340 vs 339)`) while `repo-lint` stayed green; caught by running the suite, rewritten with the em dash, then **86 / 0**. Recorded because it is the second time in this repo a heading's punctuation, not its content, decided whether it exists. Run 938's **Changed** line still carries its historical *"Measured, queued, not fixed here"* residual sentence — left **verbatim as history**, not rewritten, since run 939's own Changed line closes it by name.

- **Suites and tools, all re-read on this tree.** `bash tests/test_shift_deploy.sh` → **132 / 0, rc 0**; `php tests/test_changelog_api.php` → **86 / 0**; `php tests/test_changelog_mobile.php` → **125 / 0, 0 skipped**; `bash tests/test_queue_source.sh` → **278 / 0**; `./tools/repo-lint` → **rc 0, 210 linted file(s) parse clean, 47 Go module file(s) compile, `changelog-version: 339 … 339 unique, 10413 citation(s), 0 missing`** (git-blob count; the worktree holds **340** with `[0.4.335]` at line 10345 — **340** is the post-commit prediction, re-read below rather than carried); `REGISTRY_COVERAGE_CHILD=1 bash tests/test_registry_coverage.sh` → **rc 0, `violations=0`**, `fig_disc=107 fig_live=1 fig_claim=107 fig_stale=0 fig_head=107 fig_src=consistent`, `tools=29 registered=45 help_ok=29 badarg_ok=29 ec_ok=29 fmt_claim_mismatch=0 allflag_mismatch=0` — run **after** the last REGISTRY edit, so the **`- Live:` figure 107** and every neighbouring figure are machine-checked on the exact tree being committed; `./tools/queue-source-check` → **rc 1, exactly 1 violation: `[0.4.335] is not named in agent-logs/PROGRESS.md`** — **this very entry clears it (R8)**, and R10 is satisfied by the commit carrying `CHANGELOG.md` + this file together.

- **Scope and safety, one line each:** commits by **explicit pathspec, never `git add -A`** (shared worktree — `git status --porcelain` at write time shows **exactly this run's four modified paths** and no sibling file; PROGRESS.md becomes the fifth). This run's paths: `tools/shift-deploy`, `tests/test_shift_deploy.sh`, `tools/REGISTRY.md`, `CHANGELOG.md`, `agent-logs/PROGRESS.md`. **No `app/` file edited** → nothing to promote, no reviewer gate, no non-dry `promote-dev-to-prod` against the real trees (every mutating path ran inside `/tmp/opencode` sandboxes or the mutant root; the tool's live layer ran `--dry-run` only); dev and prod untouched, both **0.4.28**. **No `systemctl reset-failed`, no restart, no unit or timer change, no `identity-run.sh` edit, no `sofia-watch` edit**; **`rm` only inside `/tmp/opencode`** (mutant root, the rc=3 probe, suite sandboxes — all self-cleaning via the suite's trap); **no live messages-DB write**, no DNS write, no mail sent, no paid API, no API key configured; `hiring/queue/` untouched (**2 proposals `status=proposed`** — the investor's seat); spend **0.00**, free `*-free` models only.

- **Queue — next small step (read this first):** **(a⁵) unchanged and NOT consumed by this run** — the first run starting after sofia's fire at **Tue 2026-10-13 18:55:10 CEST** (or earlier if `sofia-watch` starts her on new mail) owns **one** `systemctl --failed` read **plus** the in-flight probe (`systemctl list-units --no-legend --plain 'identity-run@*' --state=activating,running,deactivating`): **failed-set empty AND no identity unit in flight** = the standing order executes (full `./tools/regression-run`, report the **first all-green totals**, naming **A30** cleared) **but read A12's detail rather than assuming it clears**; **empty while a shift IS in flight** = *not* all-green, wait (run 936's measured 8 m 17 s false-green window); **still red** = read the fresh marker, update the census against **run 936's baseline (1 unit / 1 class / ling-specific / work kept `1319ins/1files`)**; **still never `reset-failed`, never restart, never edit `identity-run.sh`**. **No new tool follow-up was measured this run** — every other non-zero exit in `tools/shift-deploy` was read while hunting this one and each is already correct (`rsync` `rc is None` → 6 with an `rsync … failed (rc=None)` detail is honest: it names the child, and dev really was not synced; step 4 and step 5's ledger `rc is None` already map to 3; step 1 and step 2 already split), so the queue carries no new unnumbered item from this desk. Then: **(b)** **STEP 0 first every run** (today: **0 unread dev / 0 prod**, `INBOX.md` **80/80/0 open**); **A28** must stay clear — this commit carries `CHANGELOG.md` + `tests/` + `tools/` + this file together, the documented pairing; **A3/A15** are this run's dirty tree and clear with its commit + push, **A12/A30** move to **(a⁵)** (A12's reason is `failed-units,queue-source` right now — the `queue-source` half clears with this entry, leaving the one failed unit, i.e. A30's reason); **the `- Live:` figure stays true at 107 — no suite was added, so the 108th suite owns the next refresh**, and re-check `REGISTRY_COVERAGE_CHILD=1 bash tests/test_registry_coverage.sh` → rc 0 before trusting any figure in `tools/REGISTRY.md` (done this run, rc 0); **`shift-deploy` is now 1.3.0 — the next JSON-shape change owns the next bump**; **still queued as previously recorded:** the durable-census item with run 936's two requirements (in-flight guard + journal-vs-transcript source decision) and the in-flight guard itself, **(93)**/**(97)(a)** first if the investor answers `hiring/queue/*.json`, **(2'')** the day the `GETTING_STARTED.md` keep/fold/retire answer arrives, **§14 renewal** cadence NEEDS-INVESTOR (no DENIC/whois/IANA re-probe), the LAN-only A/B/C (figures **110 messages / 189,209 bytes**), NUL-blob watch on a measured harm only, **(av)(d)** after the `REPORT.md` §14 sign-off, **(i)** until the prune lands, SOA MNAME and Pip's mail-policy research NEEDS-INVESTOR, **(113)**'s two `cp`s operator-blocked, **2026-10-20** §10 #6 re-read against `downloads.log`, the `/stats` display row closed with its `/api/stats` mirror unqueued, Pip's nine gaps closed, and **(ax)**, **(e)**, the drift-verify line, **(aw)**, the `promote-gates` verdict watch (never `--force` a stale verdict) and run 915's monitor closed/queued as recorded. **Closed by this run: queue line "step 3's post-copy re-read maps `rc=None` (and `rc=3`) to exit 6 with a detail the copy disproves"** (`[0.4.335]`).

- **Close-state:** this entry is appended **before** the commit that carries it (CLOSE PROTOCOL rule 1) and is never `git checkout --`-ed, staged-only or parked in `/tmp` (rules 2–3); the stop-state check is `git status --porcelain` **not listing `agent-logs/PROGRESS.md`** after the commit. The push must leave `git rev-list --count origin/main..main` → **0**. Post-commit re-reads (`repo-lint` → predicted 340/340, `queue-source-check` → rc 0 with R8 cleared by this entry, both changelog suites, the shift-deploy suite, `test_queue_source`, `inbox-status`, `version-check`, `budget-show`, `healthcheck`, the red-watch state file by `cat`) are recorded in the **close-correction** bullet appended before commit #2 if one is made (rule 2). **Queue line (a⁵) is owned by the first run starting after sofia's 18:55:10 CEST fire — this run started 16:17 CEST, took no post-fire read (the fire had not happened), and changed no unit, timer or file outside its five committed paths.**
'''
with open("agent-logs/PROGRESS.md", "a", encoding="utf-8") as fh:
    fh.write(entry)
print("appended")
PYEOF
tail -2 agent-logs/PROGRESS.md | head -c 300; echo; echo "=== status ==="; git status --porcelain; ./tools/queue-source-check; echo "qsc rc=$?"
appended

- **Close-state:** this entry is appended **before** the commit that carries it (CLOSE PROTOCOL rule 1) and is never `git checkout --`-ed, staged-only or parked in `/tmp` (rules 2–3); the stop-state check is `git status --porcelain` **not listing `agent-logs/PROGRESS.md`** after the commit. The p
=== status ===
 M CHANGELOG.md
 M agent-logs/PROGRESS.md
 M tests/test_shift_deploy.sh
 M tools/REGISTRY.md
 M tools/shift-deploy
queue-source-check: OK - one queue: [0.4.335] pointer-only, 111 item line(s) frozen across 289 section(s), 203 PROGRESS bullet(s), 2 path token(s)
qsc rc=0
> build · mimo-v2.6-flash-free
Entry is in and `queue-source-check` → **rc 0**. Committing by explicit pathspec (never `-A` on this shared index):
$ cd /data/repo && git add -- tools/shift-deploy tests/test_shift_deploy.sh tools/REGISTRY.md CHANGELOG.md agent-logs/PROGRESS.md && git commit -q -m "run 939: step-3 post-copy child that cannot run, or cannot verify, is exit 3 — shift-deploy 1.2.0→1.3.0, suite 118→132, mutant 6 signal reds, [0.4.335]" && git log --oneline -1; echo "=== status after commit ==="; git status --porcelain; echo "=== push ==="; git push origin main; echo "push rc=$?"; git rev-list --count origin/main..main; git rev-list --count main..origin/main; git status -sb | head -1
8b01fd4 run 939: step-3 post-copy child that cannot run, or cannot verify, is exit 3 — shift-deploy 1.2.0→1.3.0, suite 118→132, mutant 6 signal reds, [0.4.335]
=== status after commit ===
=== push ===
To git://git.gladex.de/gladex.git
   1f10b14..8b01fd4  main -> main
push rc=0
0
0
## main...origin/main
> build · mimo-v2.6-flash-free
$ cd /data/repo && ./tools/inbox-status; echo "rc=$?"; ./tools/version-check; ./tools/budget-show | sed -n '1,5p'; ./tools/healthcheck 2>&1 | grep -E "^(dev|prod):"; echo "=== git status ==="; git status --porcelain; echo "(empty above = PROGRESS.md not listed)"; echo "=== redwatch ==="; date -u; cat /data/agent-logs/red-watch.state
inbox-status — STEP 0 investor duty

  messages unread : dev 0 / prod 0 / total 0
  last reply      : dev 145 / prod 110
  INBOX.md        : 80 entries, 80 handled, 0 open

verdict: OK - nothing owed (0 unread, 0 open entries all replied)
rc=0
OK: dev=0.4.28 prod=0.4.28 (match)
=== Budget Status ===
Month:       2026-10
Allowance:   5.00 €
Spent:       0.00 € (no October charge in any file — MEASURED 2026-10-12: no public registry source can date a renewal (DENIC RDAP publishes only a "last changed" event, and does so for every .de domain; DENIC whois has no expiry field; the IANA RDAP bootstrap has no "de" entry), so the one open unknown is your billing cadence: monthly 1.50 as brief §4 states, or annual at the 2027-09-20 registration anniversary? Still NEEDS-INVESTOR, REPORT.md §14)
Remaining:   5.00 €
dev: HEALTHY
prod: HEALTHY
=== git status ===
(empty above = PROGRESS.md not listed)
=== redwatch ===
Tue Oct 13 14:49:39 UTC 2026
state=red
since=1791893840
failed=9
fails=FAIL A3 tree clean AND in sync with origin/main (kind=is key=git) ;; FAIL A4 queue-source-check exits 0 (kind=rc key=qsc) ;; FAIL A5 queue has exactly one home (kind=contains key=qsc) ;; FAIL A6 newest CHANGELOG queue is pointer-only (kind=contains key=qsc) ;; FAIL A7 queue-source-check json exits 0 (kind=rc key=qscj) ;; FAIL A8 queue-source-check reports no violations (kind=contains key=qscj) ;; FAIL A12 system-status verdict - checks in error: failed-units,queue-source (kind=is key=sysverdict) ;; FAIL A15 git-tree reports a clean tree (kind=contains key=sys) ;; FAIL A30 no unit is left in systemctl --failed (kind=contains key=sys)
updated=2026-10-13T14:45:01Z
$ cd /data/repo && ./tools/repo-lint 2>&1 | grep -E "changelog-version|result:|go-compile"; echo "---qsc---"; ./tools/queue-source-check; echo "rc=$?"; echo "---tqs---"; bash tests/test_queue_source.sh 2>&1 | tail -2; echo "---changelog---"; php tests/test_changelog_api.php 2>&1 | tail -2; php tests/test_changelog_mobile.php 2>&1 | tail -2; echo "---shift-deploy---"; bash tests/test_shift_deploy.sh 2>&1 | grep -E "^(FAIL|shift-deploy suite)"
go-compile: 47 module file(s) compile clean (1.874s)
  changelog-version: 340 changelog version heading(s), 340 unique, 10425 citation(s) checked, 0 missing, 13821 bare token(s) counted
result: all 210 linted file(s) parse clean (exit 0)
---qsc---
queue-source-check: OK - one queue: [0.4.335] pointer-only, 111 item line(s) frozen across 289 section(s), 203 PROGRESS bullet(s), 2 path token(s)
rc=0
---tqs---
queue-source-check suite: 278 passed, 0 failed
===============================
---changelog---

=== Results: 86 passed, 0 failed ===

=== Results: 125 passed, 0 failed, 0 skipped ===
---shift-deploy---
shift-deploy suite: 132 passed, 0 failed
> build · mimo-v2.6-flash-free
All post-commit re-reads green (repo-lint **340/340**, qsc rc 0, 132/0, 86/0, 125/0, 278/0, git clean). The `14:45:01Z` red-watch tick is a **pre-append snapshot** (it still shows A4–A8 queue-source red), so I'll wait for the next cron tick rather than assert the clear.
$ sleep 690; date -u; cat /data/agent-logs/red-watch.state; echo "=== cron line ==="; grep -a "state=" /var/log/red-watch.log 2>/dev/null | tail -4 || journalctl -u red-watch --no-pager -n 6 2>/dev/null | tail -6
Tue Oct 13 15:02:30 UTC 2026
state=red
since=1791893840
failed=2
fails=FAIL A12 system-status verdict - checks in error: failed-units (kind=is key=sysverdict) ;; FAIL A30 no unit is left in systemctl --failed (kind=contains key=sys)
updated=2026-10-13T15:00:01Z
=== cron line ===
> build · mimo-v2.6-flash-free
The tick waited for landed: **failed=9 → failed=2** (A3/A4/A5/A6/A7/A8/A15 all cleared; only A12+A30 remain). Recording it before commit #2:
$ cd /data/repo && date -u; ./tools/system-status --format json 2>&1 | python3 -c "
import json,sys
try: d=json.load(sys.stdin)
except Exception as e: print('parse:',e); sys.exit()
print('overall:', d.get('overall') or d.get('status'))
for c in d.get('checks',[]):
    if c.get('status')!='ok': print(' non-ok:', c.get('name'), c.get('status'), (c.get('detail') or '')[:160])
" ; echo "=== git status before append ==="; git status --porcelain; echo "=== fleet ==="; systemctl list-units --state=failed --no-legend --plain; systemctl list-timers 'identity-run@sofia.timer' --no-legend; echo "=== inbox at close ==="; ./tools/inbox-status | tail -2
Tue Oct 13 15:02:46 UTC 2026
overall: error
 non-ok: failed-units error 1 failed: identity-run@sofia.service rc=1 shift_exit=1 work=1319ins/1files
 non-ok: log-truncation warning identity-dispatcher.md now=5992 was=18062@e0bc90d (-66%), identity-jonas.md now=10670 was=81499@8c15565 (-86%)
 non-ok: SOA:gladex.de warning serial=2026092602 consistent on 1.1.1.1+8.8.8.8; mname=placeholder (NEEDS-INVESTOR open)
 non-ok: red-watch warning red, failed=2, since 2026-10-13T12:17:20Z, 2m old; FAIL A12 system-status verdict - checks in error: failed-units (kind=is key=sysverdict) ;; FAIL A30 no unit i
=== git status before append ===
=== fleet ===
identity-run@sofia.service loaded failed failed Scheduled persona run (sofia)
Tue 2026-10-13 18:55:10 CEST 1h 51min Tue 2026-10-13 13:55:01 CEST 3h 8min ago identity-run@sofia.timer identity-run@sofia.service
=== inbox at close ===

verdict: OK - nothing owed (0 unread, 0 open entries all replied)
> build · mimo-v2.6-flash-free
$ cd /data/repo && python3 - <<'PYEOF'
entry = '''
- **Close correction (appended before commit #2 — CLOSE PROTOCOL rule 2): the commit, the push, every post-commit re-read, and the one figure this run waited on instead of asserting.** `git commit` by explicit pathspec (five paths: `tools/shift-deploy`, `tests/test_shift_deploy.sh`, `tools/REGISTRY.md`, `CHANGELOG.md`, this file; never `git add -A` on this shared index) → **`8b01fd4`**, and `git status --porcelain` **straight after it was empty** — this entry was carried by commit #1, not left staged, not `git checkout --`-ed, not parked in `/tmp` (rule 3 holds), and no sibling-desk file was touched (the worktree held exactly this run's five modified paths at append time). `git push origin main` → **rc 0, `1f10b14..8b01fd4`**, `git rev-list --count origin/main..main` → **0**, `git rev-list --count main..origin/main` → **0**, `git status -sb` → `## main...origin/main` with no ahead/behind marker — **A3's condition met**. **Post-commit re-reads, all after the push:** `./tools/repo-lint` → **rc 0, 210 linted file(s) parse clean, 47 Go module file(s) compile**, `changelog-version: 340 … 340 unique, 10425 citation(s), 0 missing` — the predicted **339 → 340** with `[0.4.335]` landed (the pre-commit 339 was the git-blob count while the entry was uncommitted, exactly the stale-live-number class this repo documents; re-read rather than carried); `./tools/queue-source-check` → **rc 0, `one queue: [0.4.335] pointer-only, 111 item line(s) frozen across 289 section(s), 203 PROGRESS bullet(s)`** (sections 288 → 289) — **R8 cleared by the entry above, R10 by commit #1 carrying `CHANGELOG.md` + this file together**; `bash tests/test_queue_source.sh` → **278 / 0**; `php tests/test_changelog_api.php` → **86 / 0**; `php tests/test_changelog_mobile.php` → **125 / 0, 0 skipped**; `bash tests/test_shift_deploy.sh` → **132 / 0, rc 0**; `./tools/shift-deploy --version` → **`shift-deploy 1.3.0` rc 0**; `./tools/version-check` → `OK: dev=0.4.28 prod=0.4.28 (match)`; `./tools/healthcheck` → dev + prod **HEALTHY, HTTP 200, `0.4.28` both**; `./tools/budget-show` → **2026-10, allowance 5.00 / spent 0.00 / remaining 5.00**; `./tools/inbox-status` → **rc 0, `OK - nothing owed`**, `INBOX.md` **80 / 80 / 0 open** (**STEP 0 still paid at the close**: 0 unread dev / 0 prod, no row written, nothing marked read); spend **0.00**, free `*-free` models only, no secret or PII in any prompt, file or commit.

- **The red-watch tick, waited for rather than asserted.** At 14:49Z the state file read `updated=2026-10-13T14:45:01Z, failed=9` with **A4, A5, A6, A7 and A8 all red** — a **pre-append** snapshot taken before this entry named `[0.4.335]`, i.e. the queue-source check was legitimately failing at that instant and the snapshot was telling the truth about a moment that had already passed. Instead of quoting it as the outcome, this run **waited for the cron's own tick** (the same discipline runs 937–938 applied to their own). Re-read at 15:02:30Z: `updated=2026-10-13T15:00:01Z, failed=2`, **`fails = A12 ;; A30`** — so **A3, A4, A5, A6, A7, A8 and A15 all cleared with this run's commit + push exactly as predicted**, and **A12's reason narrowed from `failed-units,queue-source` to `failed-units`** (the `queue-source` half is gone because of this entry). `./tools/system-status --format json` → `overall: error` with **one error-level check**, `failed-units | error | 1 failed: identity-run@sofia.service rc=1 shift_exit=1 work=1319ins/1files` — i.e. **A12 and A30 are the same underlying fact**, sofia's one failed unit, and both belong to queue line **(a⁵)** (her **18:55:10 CEST** fire, `1h 51min` out at the close, or a mail-triggered `sofia-watch` start). The remaining warnings are pre-existing and not this run's: `log-truncation` (dispatcher/jonas persona logs), `SOA:gladex.de mname=placeholder` (NEEDS-INVESTOR), and `red-watch` itself reporting `red, failed=2`.

- **Queue line (a⁵) unchanged; every other queue item carried forward as recorded in the entry above.** After commit #2 this file is pushed by the same explicit-pathspec command, and `git rev-list --count origin/main..main` → **0** is the invariant the next run re-reads. **Stop-state: `git status --porcelain` must not list `agent-logs/PROGRESS.md`** after commit #2 — this bullet is carried by that commit, not staged-only, not `git checkout --`-ed, not parked in `/tmp`.
'''
with open("agent-logs/PROGRESS.md", "a", encoding="utf-8") as fh:
    fh.write(entry)
print("appended")
PYEOF
git add -- agent-logs/PROGRESS.md && git commit -q -m "run 939: close correction — 8b01fd4 pushed, post-commit re-reads recorded (340/340, R8 clear), red-watch tick waited for: A3+A4-A8+A15 cleared, A12+A30 left to (a5)" && git log --oneline -2; echo "=== status after commit #2 ==="; git status --porcelain; echo "=== push ==="; git push origin main; echo "push rc=$?"; git rev-list --count origin/main..main; git rev-list --count main..origin/main; git status -sb | head -1; echo "=== final stop-state ==="; git status --porcelain | grep -c "agent-logs/PROGRESS.md" || echo "PROGRESS.md NOT listed (rule 3 holds)"
appended
2377d33 run 939: close correction — 8b01fd4 pushed, post-commit re-reads recorded (340/340, R8 clear), red-watch tick waited for: A3+A4-A8+A15 cleared, A12+A30 left to (a5)
8b01fd4 run 939: step-3 post-copy child that cannot run, or cannot verify, is exit 3 — shift-deploy 1.2.0→1.3.0, suite 118→132, mutant 6 signal reds, [0.4.335]
=== status after commit #2 ===
=== push ===
To git://git.gladex.de/gladex.git
   8b01fd4..2377d33  main -> main
push rc=0
0
0
## main...origin/main
=== final stop-state ===
0
PROGRESS.md NOT listed (rule 3 holds)
> build · mimo-v2.6-flash-free
$ cd /data/repo && ./tools/inbox-status; echo "rc=$?"; sqlite3 /opt/startup/dev/data/messages.db "SELECT count(*) FROM messages WHERE direction='investor_to_agent' AND read=0;"; sqlite3 /opt/startup/prod/data/messages.db "SELECT count(*) FROM messages WHERE direction='investor_to_agent' AND read=0;"; git status --porcelain; echo "tree clean"; git log --oneline -2
inbox-status — STEP 0 investor duty

  messages unread : dev 0 / prod 0 / total 0
  last reply      : dev 145 / prod 110
  INBOX.md        : 80 entries, 80 handled, 0 open

verdict: OK - nothing owed (0 unread, 0 open entries all replied)
rc=0
0
0
tree clean
2377d33 run 939: close correction — 8b01fd4 pushed, post-commit re-reads recorded (340/340, R8 clear), red-watch tick waited for: A3+A4-A8+A15 cleared, A12+A30 left to (a5)
8b01fd4 run 939: step-3 post-copy child that cannot run, or cannot verify, is exit 3 — shift-deploy 1.2.0→1.3.0, suite 118→132, mutant 6 signal reds, [0.4.335]
> build · mimo-v2.6-flash-free
Run complete.

## STEP 0 — investor duty (paid first)
`investor_to_agent` unread: **dev 0 / prod 0**; `INBOX.md` **80 entries / 80 handled / 0 open**. `./tools/inbox-status` → **rc 0, "nothing owed"** — an empty inbox is answered by the measurement, not by a status row, so no row was inserted and nothing marked read. Re-verified again at the close (still 0 / 0). **Production is 0.4.28** — the wrong figure (0.4.29) appears nowhere.

## The step — run 938's queued follow-up, closed
`tools/shift-deploy` step 3 reads `source-sync-check` **twice**: before the `rsync` (to size the drift) and after it (to prove the copy landed). The pre-copy read has always split *couldn't run it* / *ran but couldn't verify* / *ran and it disagreed* — the post-copy read collapsed all three into **exit 6**, `dev still differs from the repo after the copy`.

- **`rc is None` → exit 3**, `source-sync-check could not be run: …`
- **`rc not in (0,1)` → exit 3**, `source-sync-check could not verify the copy (rc=…)`
- **`rc == 1` → exit 6**, old detail byte-for-byte

**Scope disclosure:** the queue named only `rc is None`. Before writing, I probed the *same line* with a stand-in exiting 3 — it produced `exit 6 / dev still differs … (rc=3)` while `cmp` proved dev byte-identical to the repo. The identical false claim one condition over, in the expression being edited, so folding it in was what made my own EPILOG line 6 true — recorded in CHANGELOG as an extension of the queued scope, not presented as it.

## Verification (all measured, none asserted)
| check | result |
|---|---|
| `test_shift_deploy.sh` | **132 / 0** (118 / 0 with the fix in and *no* assertion added — nothing reddened) |
| out-of-suite mutant (both branches reverted) | **6 signal reds: F8, F8c, F8d, F8f, F8l, F8m** + documented B6 quartet; live md5 `b8c96f2c…` identical before/after |
| `test_registry_coverage.sh` | **rc 0, violations=0**, `- Live:` figure **107** confirmed on the committed tree |
| `repo-lint` | rc 0, **340 → 340** headings (pre-commit 339 was a git-blob count; re-read, not carried) |
| `queue-source-check` | rc 0, `[0.4.335]` pointer-only — **R8 cleared by the entry** |
| changelog api / mobile / queue-source | **86 / 0**, **125 / 0**, **278 / 0** |
| `version-check` / `healthcheck` / `budget-show` | `0.4.28` match · both HEALTHY · **5.00 / 0.00 / 5.00** |

Caught by running the suite, not by reading: my first `[0.4.335]` heading used ASCII ` - `, which the app's parser regex silently dropped (`84 / 2`) while `repo-lint` stayed green — rewritten with the em dash.

## Close protocol
Entry appended **before** commit #1 (`8b01fd4`), close-correction appended **before** commit #2 (`2377d33`); both pushed, `origin/main..main` → **0**. `git status --porcelain` is **empty — PROGRESS.md not listed** (rule 3 holds).

**Red-watch tick waited for, not asserted:** at 14:49Z it read `failed=9` (A4–A8 queue-source red — a pre-append snapshot telling the truth about a moment that had passed); waited for the cron's own 15:00:01Z tick → **`failed=2`, fails = A12 + A30**. A3, A4–A8 and A15 all cleared with the push; A12/A30 are both sofia's one failed unit and belong to queue line **(a⁵)** — her fire at **18:55:10 CEST**, 1h 51min out at the close, so that item was **not** taken.

Queue line **(a⁵) unchanged**; no new unnumbered follow-up measured (every other non-zero exit in the tool was read while hunting this one and each is already correct). Spend **0.00**, free `*-free` models only, no secrets, no DNS write, no mail, `hiring/queue/` untouched (2 proposals awaiting the investor).
exit=0

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

[Tue Oct 13 17:26:14 2026] 127.0.0.1:56932 Accepted
[Tue Oct 13 17:26:14 2026] 127.0.0.1:56932 Closing
[Tue Oct 13 17:26:14 2026] 127.0.0.1:56944 Accepted
[Tue Oct 13 17:26:14 2026] 127.0.0.1:56944 Closing
[Tue Oct 13 17:26:14 2026] 127.0.0.1:56950 Accepted
[Tue Oct 13 17:26:14 2026] 127.0.0.1:56950 Closing
[Tue Oct 13 17:26:15 2026] 127.0.0.1:43390 Accepted
[Tue Oct 13 17:26:15 2026] 127.0.0.1:43390 Closing
[Tue Oct 13 17:26:15 2026] 127.0.0.1:43392 Accepted
[Tue Oct 13 17:26:15 2026] 127.0.0.1:43392 Closing
[Tue Oct 13 17:28:46 2026] 127.0.0.1:54464 Accepted
[Tue Oct 13 17:28:46 2026] 127.0.0.1:54464 Closing
[Tue Oct 13 17:28:46 2026] 127.0.0.1:54468 Accepted
[Tue Oct 13 17:28:46 2026] 127.0.0.1:54468 Closing
[Tue Oct 13 17:28:54 2026] 127.0.0.1:54474 Accepted
[Tue Oct 13 17:28:54 2026] 127.0.0.1:54474 Closing
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55754 Accepted
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55754 Closing
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55758 Accepted
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55758 Closing
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55764 Accepted
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55764 Closing
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55776 Accepted
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55776 Closing
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55782 Accepted
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55782 Closing
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55786 Accepted
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55786 Closing
[Tue Oct 13 17:30:19 2026] 127.0.0.1:55796 Accepted
[Tue Oct 13 17:30:20 2026] 127.0.0.1:55796 Closing
[Tue Oct 13 17:30:20 2026] 127.0.0.1:55808 Accepted
[Tue Oct 13 17:30:20 2026] 127.0.0.1:55808 Closing
[Tue Oct 13 17:30:20 2026] 127.0.0.1:55824 Accepted
[Tue Oct 13 17:30:20 2026] 127.0.0.1:55824 Closing
[Tue Oct 13 17:30:20 2026] 127.0.0.1:55828 Accepted
[Tue Oct 13 17:30:20 2026] 127.0.0.1:55828 Closing
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40862 Accepted
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40862 Closing
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40864 Accepted
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40864 Closing
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40876 Accepted
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40876 Closing
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40892 Accepted
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40892 Closing
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40898 Accepted
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40898 Closing
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40908 Accepted
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40908 Closing
[Tue Oct 13 17:31:22 2026] 127.0.0.1:40920 Accepted
[Tue Oct 13 17:31:23 2026] 127.0.0.1:40920 Closing
[Tue Oct 13 17:31:23 2026] 127.0.0.1:40922 Accepted
[Tue Oct 13 17:31:23 2026] 127.0.0.1:40922 Closing
[Tue Oct 13 17:31:23 2026] 127.0.0.1:40936 Accepted
[Tue Oct 13 17:31:23 2026] 127.0.0.1:40936 Closing
[Tue Oct 13 17:31:23 2026] 127.0.0.1:40942 Accepted
[Tue Oct 13 17:31:23 2026] 127.0.0.1:40942 Closing
[Tue Oct 13 17:31:59 2026] 127.0.0.1:44290 Accepted
[Tue Oct 13 17:31:59 2026] 127.0.0.1:44290 Closing
[Tue Oct 13 17:32:00 2026] 127.0.0.1:44298 Accepted

Other app logs: downloads.log