PR15040 maintainer takeover — revised head-specific nonvisual evidence
Repository: pingdotgg/t3code
Original author: t3dotgg
Original head: 6a40eb390c434de9741506a71ce8f8f161de4c90
Actual review base: 54983e3f458871dffe755ea908ffe0d60cea101b
Current cumulative top: e23910ac6b553ece70f540c8d07a5c628e6fcab8

Exact layer heads:
PR21969 scheduler-tasks-05/plan-reads c00b86c85e38eb44bcc00c55df93ef8e8be0296e
PR21970 scheduler-tasks-05/claude-homes 0c3d2edb11b1203152fcb3ebc6f519c883441e67
PR21971 scheduler-tasks-05/acp-resume 61923553e6b1882c2aeabc888f714ab3d01ea6eb
PR21972 scheduler-tasks-05/watch-recovery d357b9d56bc81785098a0766737a7a9c249057a2
PR21974 scheduler-tasks-05/server-services 4b4b4082ba8bcbdd807543857b821dfa91c39b95
PR21975 scheduler-tasks-05/first-turn-branch bf5907721000daa03b3d25faac742f0f7640ee83
PR21976 scheduler-tasks-05/title-refinement e23910ac6b553ece70f540c8d07a5c628e6fcab8

Before / after:
- Relative inherited CLAUDE_CONFIG_DIR: reading a real persisted thread's workflow script previously searched under server cwd and failed root-unavailable. It now resolves against that thread's worktree cwd, or its persisted project workspace root. Explicit homePath retains server normalization and precedence; invalid unrelated configs and containment controls remain covered.
- Fresh ACP rollback: a distinct replacement session without load support previously failed its empty snapshot read. Its known-empty snapshot is now marked hydrated at commit; snapshot read and next turn pass.
- Active resumed ACP snapshot: explicit read previously cleared current state and loaded during an unfinished turn. The same active session now returns available in-memory state without loading; later idle history hydration still runs. This adapter method has no current production app caller; this is adapter API proof, not a demonstrated current UI defect.
- Partial branch publication: after one persisted sharer updated and a later write failed, Git rollback followed by one transient compensation write failure left metadata on a deleted ref. The fix rolls Git back once and retries the separate read/CAS-write metadata phase. The real temporary Git/two-persisted-thread case now ends with both branches matching actual HEAD and no generated ref.
- Host environment: workflow fixture now explicitly provides an empty host environment with its temporary home.
- Title-whitespace finding rejected after source tracing: every current successful title producer sanitizes output before this service. Existing actual provider normalization controls passed; no artificial stub regression was added.

Independent fresh test phases: four expected red behavioral failures plus 25 passing controls. Two cases added and two existing cases strengthened across three existing files. No test case added by implementation.
Fresh post-fix verification: workflow script/transcript 8 passed; selected ACP history/rollback/resume/load/fallback/restart 11 passed (110 deselected); full ThreadLaunchService 87 passed. Total 106 distinct freshly passing cases. Repeated fixture runs do not increase this count.
Unchanged title/refinement and normalization controls from the test phase: eight reused passing results, not fresh post-fix executions.
Earlier integrated 422-case verification preceded these bot fixes and remains historical evidence for unaffected paths; it is not claimed as 422 fresh passes on this head.
Full server TS7 once: zero errors, one fixture composition warning, 154 suggestions, exit 2. Warning then fixed; final scoped two-root fixture/import check: zero errors/warnings, 35 suggestions, exit 0. Full server check was not repeated. CI validates the pushed heads separately.
Seven changed-file lint: zero errors, seven existing warnings, exit 0. Cumulative git diff --check passed.

Review: R1 findings fixed; R2 cancelled before verdict due to main integration; R3 config-isolation finding fixed; R4 cleared before these new bot cases. R5 Sol and Opus both clear on each exact layer and the cumulative diff. Opus independently reproduced all 106 current scoped passes. Four completed parallel review rounds (R1, R3, R4, R5); R2 cancelled before verdict. Follow-up CI is reported separately after push.

Scope and method:
Eight surviving behaviors in seven layers; six original claims already fixed on pinned main and omitted, including Claude custom-home forking. Incoming main fixes preserved. Cumulative 28 files, +2520/-328. Twenty-nine new behavioral cases across eight existing owner test files; no new test module.
Headless Linux / Node 24, isolated real temporary Git and persisted SQL/orchestration, effect-worker milestones and mock provider/ACP protocol. Earlier shared maintenance proof uses three in-process production-handler RpcTest clients, not actual sockets or the full auth upgrade graph. Scanner/route sharing is source-verified. Main-owned Claude SDK synthetic-worker proof is retained, not attributed to our replacement.
Metadata compensation is interruptible and scoped in memory: permanent storage outage retries with capped spacing until cancellation; restart does not resume it. Git rollback failure and arbitrary external Git status-to-rename races remain limits. No durable recovery system added.
No live account-based provider turn, native Windows/macOS/iOS/Android, packaged Electron, older Node, actual relay/tunnel or browser proof. No UI code changed.