Issue 19657 current-main runtime reproduction
Commit: 70e5e384da
Environment: Linux x86_64, Node v24.21.0, web dev server, Chromium collaborative Browser panel, 1280x800.
Started: vp install; vp run dev in /home/ubuntu/wt/issue-19657. Isolated .t3 seeded by dev runner from read-only snapshot.
Real app prompt: Use native spawn_agent once; child replies fixture child done; wait, then reply fixture parent done. No file edits or commands.
Observed: parent replied fixture parent done. Sidebar has three top-level threads; native child /root/fixture absent.
Settings UI: Auto-settle inactive threads enabled.
Reporter SQL (read-only): subagent unpinned=1; top-level unpinned=3.
The new child has lineage.relationshipToParent=subagent and settledOverride=null.
No direct database writes were used.
Sweep span counts below count span records, not git processes or remote requests. settleThread is called twice per candidate in this implementation.
2026-10-21T22:31:22.057092+00:00 {'serverSettings.materializeSettingsSecrets': 1, 'sql.transaction': 1, 'sqlite': 1, 'ThreadSettlementServiceV2.settleThread': 6, 'ThreadSettlementServiceV2.pullRequestFor': 3}
2026-10-21T22:32:22.094676+00:00 {'serverSettings.materializeSettingsSecrets': 1, 'sql.transaction': 1, 'sqlite': 1, 'ThreadSettlementServiceV2.settleThread': 8, 'ThreadSettlementServiceV2.pullRequestFor': 4}
Limits: Native Codex child only; default (no branch) fixture. No Windows/Electron, mobile, Claude or delegate_task variant tested. This confirms candidate evaluation overhead; no claim of git-process reduction.
Existing maintainer-taken-over fix: https://git.cafe/pingdotgg/t3code/pulls/19665 (open, not verified by this session).