Repository navigation
fix: prevent landscape workers deleting shared scratch - #987
Conversation
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1c9a61fea6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Delightful! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Scope
Landscape judgment workers could wildcard-delete another worker's shared scratch files. This change gives
landscape-sweep-workera native read-only tool allowlist and assigns scratch preparation/cleanup to the existing coordinator and command-only wrappers. Public GitHub GET/index/search replaces shell research in that role.Native Skill is also excluded: a measured 2.1.296 fixture showed dynamic skill context could delete a foreign file with Bash absent. Workers read and apply installed SKILL.md research instructions; future templates, routing text and prompt digest contracts follow that route. The SubagentStart and SessionStart token-lanes hooks supply no carrier to this role because its body already provides the applicable guidance. This prevents the default carrier from directing the restricted worker to ungranted tools.
9d4c00cd05d79b3fd5074df2e46bacab87ee67ff.92ae28b617371aa8fe16811969e75fb69be46397, one released second correction directly on1c9a61fea6925910ebe49e25736efb630d201fb3. The first correction and its historical receipts remain retained.lane:foundation.sweep.js,templates.json, README; native-boundary and harness tests; both token-lanes startup hooks, hook tests and SHA256SUMS; the token-session handbook; the dated decision and evidence-manifest registrations.SOTA sources
24972e3bc859fab2b46ed4c1e51f7d6130f06d3bd550811a114640de3370d0de. Bounded native source offsets are in the decision. Official hook/tool documentation was rechecked on 2026-10-11.Evidence-class table
Local commands run
Merged checks used tree
2e3d01452186cdc17476056431e11f80b07bb52b, produced bygit merge-tree --write-tree 8bffa2c41692ef483e91b68e3b15aeb331423d2c 1c9a61fea6925910ebe49e25736efb630d201fb3and checked out in an owned detached test worktree. No rebase or landing was performed. FULL validate checks integrity and scope; the native boundary suite uses isolated loopback fixtures with no paid model or real authentication. Full unittest discovery remains with hosted CI under the CC's test policy.Decision record
docs/decisions/2026-10-10-landscape-scratch-ownership.md records vendor sources, failing regressions, the hook correction, alternatives and the overturn condition.
The boundary controls tools available to judgment workers. Coordinator/native job wrappers retain their capabilities. Research quality and throughput with public GitHub retrieval and source-reading skills remain unbenchmarked; inaccessible facts stay unknown/pending.
Checklist
Follow-ups
refuted=trueversus role-bodyunknownconflict; compare coordinator prefetch or an authenticated read-only route (research intake: research-runtime, fix: prevent landscape workers deleting shared scratch #987 thread4240880950).--agentsshadows the user-scope role copy. Drop it on the next touch.Second correction — complete three-family wave
The CC’s 15:47Z release combines the sole in-scope SessionStart P2 with folded Workflow-path, hook-prerequisite and handbook corrections in ONE forward commit. SessionStart/SubagentStart share the worker silence boundary; both existing failing assertions are preserved. Hook checksums and all affected evidence registrations are refreshed. The pinned mirror
anthropics/claude-code@2301018b1f61073c501a8e7a4813ef48c239163bCHANGELOG.md:7476supplies SessionStart agent_type; :6738 supplies the general hook agent_type field and :5513 supplies print-mode tool-frontmatter behavior. Actual fail-first: SessionStart: 14 tests, two failures at 1c9a61f, green after the correction.Native Workflow
agent(prompt,{agentType})now has local loopback coverage for refused Bash/MCP execution, preserved foreign scratch and admitted Read. The installed role is copied verbatim into an isolated test config. This is synthetic-provider local integration, not paid research or a live-provider result. Opted-in hosts explicitly refresh both held-out carriers; handbook lists both carriers’ zero-byte worker output. Skills digest and capacity mechanism choices remain research-queue items, with the skills launch hold preserved.After this second fix round, ONE delta micro per family. The CC adjudicates any remaining items; a reproduced defect in the fix commit gets one correction, other findings are Follow-ups unless a new P1.
Current review disposition
Claude delta micro is PASS_WITH_P3 at 92ae28b; no correction is owed. Its carrier-silence and CLI-role-shadowing findings are retained above for the next touch, with record spacing and receipt-location wording. Current source-window/binary-hash receipts are retained privately in
lanes/convergence-practice-work/pr987-release-fix-20261011/, includingclaude-2.1.296-SessionStart-source.jsonand the full pinned changelog. This body edit changes no source or head. Hold for the queued GPT delta ACK over 1c9a61f..92ae28b and the CC landing cue; skills-modality launch and research Follow-up gates remain.