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

logs: refactor pushed to 817ddfea6, row 96 packet scan exception (sage-0144)

Browse Source 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
jason.woltje
2026-10-13 16:46:35 -05:00
co-authored by Claude Opus 5.5
parent 817ddfea65
commit 0e9eae68c7
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
BUILD-LOG.md
+5
View File
@@ -4520,3 +4520,8 @@ After: rebased onto 79e126be0; install scans systemd-analyze lookup paths instea
Before: rows 101 and 105 were approved; rows 85 r2 (#1579), 102 (#1596) and 103 (#1597) were approved, with 85 and 103 both editing packages/cli/README.md and packages/cli/tests/host.test.mjs.
After: one Sage gate of base 3a1e11b83 with 85, 102 and 103 applied was green (bus128 business67 cli165 control-board124 conversation182 discord178 harness73 ledger78 mosaic69 queue155 runs43 seat113 tasks92 webui108; scripts auth15 conductor17 config24 discord66 extension-package18 foundation44 queue28 release14 task98). Correction: the first run of that gate lacked the node_modules link and failed cli 8 with ENOENT; tee without pipefail hid the exit code. Rerun with the link and pipefail was green, and the gate template now refuses without node_modules. Landed 056a20397 (101), 3a1e11b83 (105), 305a012b1 (85), 2a9b77b56 (102), 465bbdfbb (103); rows done at revs 1016-1027, queue commit 8862cd5fd.
verify-commit passed rows 101, 105, 85 and 102 and refused row 103 on 465bbdfbb (packages/cli/README.md and packages/cli/tests/host.test.mjs content differs). Cause: Darkwing built the row 103 manifest 6e5ac8c0 on 79e126be0 before row 85 landed, so the landed blobs carry both rows' hunks. Mos accepted per-path patch-id equality against agents/darkwing/work/queue-103/r1/build.patch instead (sage-0143): for all 12 paths, `git diff 2a9b77b56 465bbdfbb -- <path> | git patch-id --stable` equals that path's section of build.patch (README 18e65f78, host.test.mjs eda1a908), and the commit's path set is exactly the patch's 12 paths. Mos checked it independently.
### 2026-10-13 21:46:35 UTC — Sage, refactor pushed to 817ddfea6; secrets scan exception for the row 96 packet (sage-0144)
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.