mosaicstack/stack
25
0
Fork 1
Code Issues 366 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

docs: BUILD-LOG and SESSIONS for the fed66feff re-pin, row 117 and decisions 136/137

Browse Source 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
jason.woltje
2026-10-14 12:25:15 -05:00
co-authored by Claude Opus 5.5
parent 0b106518ad
commit 8d586bdb5b
2 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
BUILD-LOG.md
+10
View File
@@ -4561,3 +4561,13 @@ Landed as d90482030 on refactor from Darkwing's round 2 packet (40e5917f9), cand
Sage's landing gate ran at 2330074bb, which includes the PRD merge f7c8537b3 and its change to packages/bus/tests/requirements.test.mjs, with the candidate applied: 23 steps passed, bus 156/0 and harness 81/0, no flakes and no reruns, GATE_PASSED at 17:09:25Z. The worktree and its Docker network are removed. `queue review verify-commit 115` matched the 5 manifest paths. Queue commit d479f043e records revs 1131-1138 and row 115 done.
Decision 109 before-notice to Mos was sage-0173. The change isn't live: the copy and re-pin wait for Mos's go, possibly together with the bus restart for Jason's CTO business-file edit.
### 2026-10-14 17:25 UTC — Sage, row 115 live on copy fed66feff; row 117 filed (#1611); lead decisions 136 and 137
Re-pin (Mos's go, sage-0174 to sage-0176). Before: the live stack ran from copy f7c8537b3, without row 115. After: Sage made copy fed66feff and saved rollback set /mnt/storage/scratch/sage-pin-rollback-f7c8537b3. Mos stopped the units, Sage ran bus-service and webui-service `install --copy fed66feff...` with the units' full flags, then `stack-copy.sh wrapper`. The diff against the rollback set showed only the copy id, and `stack-copy.sh check` returned rc 0. Mos started the units. Downtime was 17:12:52Z to 17:13:29Z. At 17:24Z every stack process (59) runs from copies/fed66feff and none from an older copy. Rollback sets and copies are kept.
Coder clone (Mos's report). The coder was blocked on task 19/266 because its clone's origin/refactor was 0c3826910, several landings old. Sage's first answer, sage-0177, proposed letting a clone set user.* keys. Correction, sage-0179: row 104 (#1598) already gives every session its identity through GIT_AUTHOR_*/GIT_COMMITTER_*, and refusing user.* keys is deliberate. The clone's `[user]` section dates from 19:53Z on 10-13, before row 104 landed, and is a leftover. The one-off, relayed to the PM through Mos: `git config --remove-section user`, put away the superseded work/prd-v1-1 work, check out refactor clean. The real gap is filed as row 117 (#1611, brief 559ef2287, revs 1139-1141): a clone kept for other-branch or dirty gets the fetch, never a merge. Owner Darkwing, reviewer Dewey. Row 116 now waits for 117 (rev 1140).
Decisions (0b106518a). 136 records Jason's yes to the #271 CI steps (Vikunja #273-#278). Correction to sage-0178: test-queue.sh runs 9 test files in packages/queue/tests, not 11; the 156-test count was right. The landing gate template moved to /mnt/storage/scratch/sage-gate-template/gate.sh, which drops the pkg-queue step. 137 is Jason's Q143 answer, written up as the reviewer rule for Vikunja #279: doc-only findings, on .md files no test reads, record approve and land as a follow-up commit; everything else still blocks. The queue README's verdict paragraph points to it. Filbert, Dewey, Rocko and Darkwing were told (sage-0183 to sage-0186).
Not done here: the C-suite launch path waits for Mos's read-back with Jason (sage-0179 answered the read-only questions).