PR #27436 real runtime verification
main: 8b74a69019e3d0f5be62dc118c526669002fc195
PR head: 9377f0e12c1a70be4c000675709d2fd0ae280e70
Client: Playwright, /usr/bin/google-chrome, 1440x1000, Linux
One dev server at a time: vp run dev; peer: node apps/server/src/bin.ts serve (no watcher)
Both environments use fresh isolated state and a project added through the app at /home/user/lineage-verification.
Provider: Codex gpt-6.1-sol via local proxy.
Parent delegated across environments with delegate_task.
Child ran cat README.md and returned LINEAGE_CHILD_READY.
Parent deleted through thread actions -> Delete -> Confirm.
main: click Lineage parent row navigated away from child into an empty New thread view without deletion feedback.
PR: same child and deleted parent; row click sent orchestration.getThreadProjection for 63c28cc9-0e6f-459d-979a-bb97484d95d5.
Real websocket response: Success, thread.deletedAt=2026-11-01T01:53:33.580Z.
PR: info toast The parent thread was deleted; child route and LINEAGE_CHILD_READY remained visible.
PR: a second real remote Codex delegation produced Live child, which read README.md and returned LIVE_CHILD_READY.
PR: clicking Live parent from Live child opened the correct remote parent route.
PR: stopped the real peer backend; clicking Live parent showed Could not open the parent thread, kept Live child and LIVE_CHILD_READY visible, and did not claim deletion.
PR: after restarting the peer and waiting for its descriptor endpoint, clicking again opened the live parent successfully.
Blacksmith: both existing ThreadRelationshipsControl browser test files passed, 8 tests total.