fix(cloud-agent-next): isolate scoped Stop across the service boundary - #6005
Conversation
c4f0c5d to
70f6a25
Compare
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryIncremental review of the wrangler catalog pin to 4.112.0 (workspace + lockfile) with high confidence and no new high-severity defects. Files Reviewed (2 files)
Previous Review Summaries (2 snapshots, latest commit 88b903a)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 88b903a)Status: No Issues Found | Recommendation: Merge Executive SummaryIncremental review of the follow-up Stop isolation fixes (cleanup-vs-fullCleanup wait, delayed shared-root abort acknowledgment, and detach wrapping) with high confidence that the changed production paths are correct. Files Reviewed (3 files)
Previous review (commit 70f6a25)Status: No Issues Found | Recommendation: Merge Executive SummaryReviewed scoped Stop isolation across the sandbox-control service boundary (abort-result protocol, root-vs-runtime cleanup, per-root retirement claims, and outbox lanes) with high confidence that the changed production paths do not introduce new high-severity defects. Files Reviewed (31 files)
Reviewed by grok-4.6 · Input: 124.5K · Output: 5.1K · Cached: 186.9K Review guidance: REVIEW.md from base branch |
70f6a25 to
0e214a6
Compare
Release operation-only root cleanup without fencing sibling chats, keep per-root claims from retiring a successor, and reject root+quiescence on the strict abort-result reader. Preserve shared-root retirement without a kilo runtime, detach terminals only after a successful abort retirement, and cover worktree/terminal abort paths in unit tests.
0e214a6 to
88b903a
Compare
Sync with main and regenerate pnpm-lock.yaml. Main downgraded the wrangler catalog to 4.112.0 (#6005); the stale branch lockfile made --frozen-lockfile fail on the PR merge ref with ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY.
Summary
Test plan