docs: BUILD-LOG and SESSIONS for row 112 landing and the cc48b124f re-pin (#1606, #1607, #1608)

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-14 11:14:45 -05:00
parent d7e1d5ed5d
commit ce8669219d
2 changed files with 11 additions and 0 deletions
@@ -4525,3 +4525,13 @@ verify-commit passed rows 101, 105, 85 and 102 and refused row 103 on 465bbdfbb
 Before: origin/refactor at 0d71b9ddd. The pre-push secrets scan of 0d71b9ddd..817ddfea6 stopped on one match, `eyJ` in agents/researcher/work/i1-proxy-test/out/logs-endpoint.final.json (Researcher's row 96 packet, commit 587e64a27). Under sage-0142 I stopped and reported to Mos instead of working around it.
 After: Mos accepted the push unchanged (sage-0144). The match is the logs endpoint's `next-cursor` page marker: one base64 segment, 235 characters, no dots, decoding to v, file, offset, size, modTime, modTimeUnixNano, latestTimestamp and fingerprint (ints and strings, no key or auth field). Mos also read the whole 813-line log. It holds stand-in proxy keys, in a `DELETE /v0/management/api-keys?value=` line and in the out/config.*.yaml copies. They are made-up keys for a proxy that run-all.sh ran under `unshare -rn` with no route to the host proxy, and cleanup removed it, so no real credential is in the packet. Values are not repeated here. A rescan with that file excluded found 0 matches, and the file's only match was the cursor. Pushed 817ddfea6 as jarvis, fast-forward from 0d71b9ddd; 465bbdfbb is reachable from origin/refactor. Follow-up for Researcher, not blocking: in future packets, give stand-in keys a prefix the scan already passes, or redact `value=` in saved proxy logs.
 ### 2026-10-14 16:15 UTC — Sage, row 112 landed and the stack re-pinned to cc48b124f (#1606)
 Before (f63fc20e4): the bus refused a decision.raise recommendation that was not exactly one option key with `invalid-options`, the code for a bad option list. The raise_decision tool text asked for "Your recommended option key, with a reason". The PM sent "key: reason" four times (bus events 335-338), changed its options each time, and Jason's Q139/Q140 direction never reached the Inbox. The live stack ran from copy badfa52b9, and 179697a8a (row 110) was copied but not installed.
 After (cc48b124f): Darkwing's round 2. 5 files changed, +52 -5. A recommendation miss refuses `invalid-recommendation`, checked after the options. The tool text says recommendation is one key with the reason in question, and that approvalChoice defaults to yes. The bus README lists the three codes, and a malformed option object refuses `invalid-request`. Round 1 drew changes: Sage 28378, which corrected Sage's own wrong approve 28377 (rev 1107), and Filbert 28379. Round 2 was approved by Filbert (28383) and Sage (28384) on manifest 013c82c2, base 96656dd21, packet fee89d52f. Sage's gate on f63fc20e4 plus the candidate ran 16:01:58Z to 16:06:53Z: bus 148, business 67, cli 184, control-board 124, conversation 182, discord 178, harness 80, ledger 78, mosaic 69, queue 156, runs 43, seat 120, tasks 92 and webui 108, and all nine `scripts/test-*.sh`, with 0 failed. None of #258/#261/#262/#263 recurred. `queue review verify-commit 112` matched 5 paths. Row 112 was done at rev 1117 (5b86abe47) and pushed as jarvis, 28c08328e..5b86abe47. #1606 closed with 28394.
 Re-pin: Sage made copy cc48b124f, which carries 179697a8a, ancestor checked. Mos stopped the Console and the bus at 16:10:18Z. Sage saved rollback set /mnt/storage/scratch/sage-pin-rollback-badfa52b9, then ran bus-service and webui-service `install --copy cc48b124f...` and `stack-copy.sh wrapper`. All three returned rc 0 and changed only the copy id. `stack-copy.sh check` returned rc 0. Mos started the bus at 16:11:35Z and the Console at 16:11:38Z. Mos then resent the Q139 direction, and the PM raised decision 03130d08 (prd.approve, gated, recommendation "yes") at 16:12:12.900Z with no refusals. Sage's read-only checks found every process on the new copy and none on badfa52b9, and healthz returned 200. Rollback sets badfa52b9 and 465bbdfbb are kept, as are the old copies.
 Also filed: row 113 (#1607), the ledger reasoning-row and issue-page fix, and row 114 (#1608), the Discord connector on a pinned copy (Mos's request; the live step waits for the SetSpark freeze).
@@ -912,3 +912,4 @@ are never rewritten or removed; corrections are new entries.
 2026-10-14T15:52Z | Filbert (Opus 5.5, 048f3c63) | row 112 #1606 round 1 review | changes, comment 28379, rev 1108 (uncommitted for Sage): C1 the README invalid-options row names a malformed option's code wrongly (it refuses invalid-request); broker, tests and both mutants verified
 2026-10-14T16:00:23Z | darkwing | row 112 (#1606) round 2, invalid-options README row | README cell lists only count, key, text and duplicates, shape refuses invalid-request (Sage 28378, Filbert C1 28379), shape test added, m1 and m2 killed, gate passed 15:53:56-15:59:33Z, packet fee89d52f, in review revs 1113-1114, comment 28382
 2026-10-14T16:01Z | Filbert (Opus 5.5, 048f3c63) | row 112 #1606 round 2 review | approve, comment 28383, rev 1115 (uncommitted for Sage): C1 and Sage's 28378 closed, the README options row matches broker.mjs clause by clause; the new shape assertions kill a keys() mutant
 2026-10-14T16:15Z | Sage (Opus 5.5, 1ef1e4f8) | rows 112, 113, 114, 7 | row 112 reviewed (r1 approve 28377 wrong, changes 28378; r2 approve 28384), landed cc48b124f, done rev 1117, pushed 5b86abe47, #1606 closed; re-pin to cc48b124f steps 4-5 for Mos (rollback set badfa52b9), post-restart checks clean, decision 03130d08 in the Inbox; row 113 #1607 filed and briefed; row 114 #1608 filed and briefed (d7e1d5ed5); row 7 partial posted 28380