# Scheduled fresh-thread worktree runtime evidence

Scope: [#22800](https://git.cafe/pingdotgg/t3code/pull/22800), [mirror #22801](https://github.com/pingdotgg/t3code/pull/22801). Minimum AFTER rows captured: **2/2, R1 PASS and R2 PASS**.

BEFORE source: [e27a03e94d](https://git.cafe/pingdotgg/t3code/commit/e27a03e94d43b504cfc3933282af913763312afd), full SHA `e27a03e94d43b504cfc3933282af913763312afd`.
Runtime-tested AFTER source: [224ad28ee9](https://git.cafe/pingdotgg/t3code/commit/224ad28ee98c6a0e483e4fd10e4055b24f92710d), full SHA `224ad28ee98c6a0e483e4fd10e4055b24f92710d`.
Final local HEAD: [e5bc3901be](https://git.cafe/pingdotgg/t3code/commit/e5bc3901bedb74ca2f009a4d89d4822778206a67), full SHA `e5bc3901bedb74ca2f009a4d89d4822778206a67`. This adds only `apps/server/scripts/seed-scheduled-task-worktree-fixture.sh`; implementation unchanged. Parent owns push and PASS2.

Rendering/runtime: server-only transcript exception, no UI changes or pixel captures. T3 preview Chromium drove the existing fixture Codex agent using actual isolated-server MCP tools. Existing lead-owned Node v24.21.0 server PID 115512 started 10:33:41 UTC, after AFTER commit at 10:31:40 UTC; cwd is this worktree's `apps/server`, running `node src/bin.ts`. Its environment and open DB descriptors confirm isolated home `/home/ubuntu/wt/issue-16183/.t3`, server localhost:14587, web localhost:6547. No additional servers were started.

The local bare origin advertises master at `5cade2a196ef3c8da4151a9e8ced1c1b5a04c336`. Both local/tracking master exist; main and cached origin/HEAD were absent before mutation and immediately before unbind/trigger. Both stored strategies are `{type:"worktree",baseRef:"refs/remotes/origin/master",startFromOrigin:true}` with null thread binding.

- R1 task `scheduled-task:9f32911b-e1b3-4041-9adb-e51db8284ce4` created unbound. Returned fresh thread `thread:project:9b67ce6b-1ea0-42fb-83df-cfe8b4a547f7:fc313107-1d00-4e7d-848a-0bc67ec2ca09`; real worktree `/home/ubuntu/wt/issue-16183/.t3/worktrees/project/t3-13d9e1e9`, branch `t3/reply-ok-only`.
- R2 task `scheduled-task:30ab72cb-5ca7-4652-8468-4da48770dcb0` first stored bound thread `39fd1ccb-5665-4be8-9362-c70aa471ae16` with root strategy, then actual explicit unbind stored null binding and the qualified master worktree strategy. Returned fresh thread `thread:project:9b67ce6b-1ea0-42fb-83df-cfe8b4a547f7:e6f116fe-0a2a-42bc-91ef-de125b0e6573`; real worktree `/home/ubuntu/wt/issue-16183/.t3/worktrees/project/t3-5bed94f5`, branch `t3/reply-ok`.

For each, durable scheduled-task message IDs bind the task to the run; persisted run transitions include preparing, starting, running and completed. Both providers replied OK. Both child HEADs equal the advertised default SHA and both working trees are clean. The trace includes successful worktree preparation and prepared-run release twice. This proves more than scheduler dispatch success.

## Evidence

- [AFTER transcript, exact actual tool calls/results, task projections, child/run/events and Git proof](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/597cff49bb491f64/after.txt)
- [AFTER preparation/release server trace](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/f4f9b49d716d9e38/after-server-trace.ndjson)
- [R1 created and R2 bound, before unbind](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/9f627e53bccb6e34/after-create-before-unbind.json)
- [After explicit unbind, before triggering; uncached origin/HEAD proof](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/79809604f5926aa6/after-unbind-before-trigger.json)
- [After trigger: full durable children/runs/events and actual Git proof](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/22d537e7a7a2c790/after-trigger.json)
- [After cleanup: zero tasks; children/runs retained](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/b049044a9cc17e84/after-cleanup.json)
- [Scoped fixture-agent durable events, including actual MCP inputs/outputs](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/a785eb0e1446cb01/fixture-agent-events.ndjson)
- Preserved [BEFORE transcript](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/cd0f6c30f8b467f4/before.txt) and [BEFORE failure trace](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/0ec2ade24f428ab6/before-server-log.ndjson).
- Original [proof matrix and scoped controls](https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/67b18877b527801e/matrix.md).

## Reproduce

Run `bash apps/server/scripts/seed-scheduled-task-worktree-fixture.sh` from the final checkout, or supply a new temporary directory. The committed script contains all fixture data: the empty Git tree, fixed identity/timestamp/message and expected SHA. It creates a local bare master origin and clone, removes cached origin/HEAD, and prints the actual MCP sequence and durable acceptance checks. Register the generated project in isolated development state and use its agent thread. No live-state edits or credentials are needed. The script was run successfully at `/tmp/issue-16183-pass2-rebuild`; its result exactly matched the captured default SHA. A second run refused to overwrite the fixture. `bash -n` and staged `git diff --check` passed; commit hook formatting passed. Shellcheck is unavailable. No backend implementation changed, so prior scoped test results were not rerun or independently claimed here.

Both created tasks were deleted with actual MCP deletion calls; MCP list and independent read-only SQLite query confirm zero scheduled tasks remain. Child threads/worktrees remain available for inspection. No forge CLI, forge comments, pushes, UI edits, auth configuration changes or new servers. Local evidence remains under `/tmp/issue-16183-evidence`.

Friction: this child browser needed standard isolated pairing and a full reload after hash-only navigation. Pairing credentials were kept out of public artifacts. First explicit update used `taskId`, failed schema validation, then succeeded with `scheduledTaskId`; both calls are retained. C1-C10 were not rerun in this runtime capture; residual branches remain as documented in the original matrix. No minimum runtime row remains unverified.