Support exact secondary-root Agent worktrees - #816
Conversation
Audit disposition — direct correctness blocker (2026-08-14)The complete-root authorization and fail-closed handling of stale, duplicate, and ambiguous bindings are good. The no-binding Context Builder branch still violates the intended physical-root contract, however: it returns Return the selected canonical physical root when no session binding overrides it, add a focused stored-versus-active workspace regression, and rerun the failing app shard. Treat the separate Codex context-window failure as a baseline/rebase issue if it is unrelated. I would not merge until the root-selection regression is fixed. |
Deep-review assessment — 2026-08-14Disposition: block on the no-binding execution-root regression. Authorizing bindings against the complete canonical workspace root set and rejecting stale/duplicate/ambiguous logical roots is the right model. However, Return the selected canonical physical execution root in the no-binding branch and add a regression where the selected secondary/stored workspace differs from the active primary workspace. This aligns with the reviewed exact-head shard failure that observed the active workspace instead of the stored selection. Rerun the failing shard and the full |
Summary
Validation
make dev-test FILTER=AgentRunWorktreeStartTests— 55 tests passedmake dev-lintmake dev-swift-build PRODUCT=RepoPrompt.agents/skills/rpce-contribution-check/scripts/preflight.sh commit.agents/skills/rpce-contribution-check/scripts/preflight.sh pushorigin/main..HEAD— no blockersAdditional validation context
The full local PR-ready root suite was attempted. It progressed through the affected coverage but did not complete: an unrelated durable-artifact concurrency test reported a busy publication result, and the run later stopped producing output in workspace-context tests. The focused Agent worktree suite, strict lint, and affected product build all passed.