Repository navigation
fix(server): enforce owned worktrees for coding launches - #28
Draft
nullStack65 wants to merge 1 commit into
Draft
nullStack65 wants to merge 1 commit into
nullStack65 wants to merge 1 commit into
Conversation
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New coding launches can reuse a project checkout without proving exclusive thread ownership. Require a dedicated, destination-qualified worktree before thread creation and provider execution, preserve ownership during retries and accepted sends, and expose explicit Coding and Coordinator choices on desktop and mobile. Existing imported histories retain their recorded paths.
Validated with focused server and real-Git integration tests, web draft tests, mobile recovery/outbox tests, scoped typechecks and lint, plus independent review of the exact committed tree. One paid-provider integration remains opt-in and was skipped.
Normal CI passed on the latest commit: Check, Test, all three server shards, Rust, Release Smoke, and native-change gates. Paid preview was skipped.
Draft pending actual before/after UI evidence. Cloud browser/computer use is explicitly authorized. The supported browser controller is not exposed in the current session, so capture has not been performed; this is a tool-availability blocker, not a permission gate. The exact source head and current main base remain unchanged and normal CI remains green. No UI evidence, merge, or installed acceptance is claimed. Shared artifact sequencing and host incorporation remain with the existing release20/ENV owners once source landing is qualified.
Models: GPT-6.1 Sol outcome owner and native GPT-6 Luna implementation/review agents. Harness: Codex managed cloud.