docs(build-log): row 41 round 4 started (filbert)

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-09 22:23:09 -05:00
parent 0b855ae1fe
commit 0a4c8f13b0
1 changed files with 4 additions and 0 deletions
@@ -3853,3 +3853,7 @@ After: R4 is fixed in `packages/harness/src/gate.mjs`. For Pi's `read` and Claud

 ### 2026-10-10 — Sage, row 40 landed: slice 1 S5 WebUI views and CHAT-03 follow-ups (#1522)
 Both round 3 reviews approve candidate d0aa0ded: Filbert (comment 27011, rev 260, a248ec64) and Darkwing (comment 27013, rev 264, 09bcd1a9, packet 67630cc4). The manifest checked 27/27 in the canonical tree, and the candidate landed as 08b428ec. I committed it through a temporary index because about 150 unrelated files under packages/mosaic/framework/tools/ are staged in the shared index. `queue review verify-commit 40 HEAD` matched all 27 paths. Gate on a detached worktree of 8cad7722 plus the candidate: webui 22/0, conversation 161/0, control-board 124/0, test-auth 15, test-conductor 17, test-config 24, test-discord 66, test-extension-package 18, test-foundation 44, test-queue 27, test-release 14, test-task 98/0, all with 0 failed. The Docker recall pair passed this time. Darkwing's note 1 is not fixed in this landing: mutant Mr (a hold inside held text is not drained again) survives, so a regression would swallow all later terminal input, Ctrl-C included. I took the approved candidate as it stands rather than open round 4 for one test. Dewey's flows test (drafted, kills Mr, flows 28/28) is the first follow-up row. Filbert's row 41 round 3 entry mentions a conversation `shim.mjs` from their round 2 gate that ignored SIGTERM; that test-cleanup note goes in the same follow-up row. Row 5 Gate E stays Jason's.
+
+### 2026-10-10 — Filbert, row 41 slice 1 S6 round 4 started (#1523)
+
+Before: Darkwing's round 3 asked for changes (#1523 comment 27032, rev 271, packet 974da6ed). R4 is verified fixed. R5: `insideWorkspace` in `gate.mjs` resolves a relative path against the workspace path as given, but Pi resolves it against its cwd, and both adapters `cd` into the workspace, so the cwd is the real path. With the workspace or the dataRoot behind a symlink, `..` climbs different parents. Darkwing's probe had a real Pi session read a file outside the workspace and write a new one there. Sage ruled R5 is fixed in this row as round 4: resolve a relative path against the real path of Pi's cwd; tests with a symlinked workspace and a symlinked dataRoot, each covering read and write and refusing the `../..` escape, plus one relative path through the symlinked root that stays inside and is allowed; rerun Darkwing's repro against real Pi; state in BUILD.md why Claude Code is unaffected; leave R1 to R4 alone, no other scope. Row 41 is in-progress again (rev 272, 0b855ae1). Plan: a relative path must resolve inside against both the real path and the given path; the survivor mutants Mw to Mz and the seat `workspaceDir` realpath go to follow-ups. No push; landing target 2026-10-13, after the Q14 hold.