parity: fix(web): deleted forks no longer remain in Lineage (pingdotgg/t3code#29000) #283

Upstream pingdotgg/t3code#29000 (9bfecb8f1e) changes native parity requirements.

Ledger rows: TV-LINEAGE, TV-DETAILS. Existing owning backlog: #243.

Additive optional RPC surface; no required native decoder changed. Confirmed feature follow-up: native lineage/relationships.rs builds rows from shell/family/archived graph and falls back to thread id; new title lookup is absent in targeted native symbol scan. Upstream hides non-subagent deleted relationships only after settled lookup, keeps archived/unknown/pending states reachable, and refreshes on removals. Existing lineage row covers it.

Required follow-up: compare the bounded native path, implement only the scoped parity correction when selected, and provide appropriate failing-first logic proof or visual before/after evidence. New head/base requires independent review and factory verification.

This intake issue records work still outstanding. It changes no accepted ledger status; sidebar stays 5/16. No live credentials, provider turns, servers, real-window automation, or widening of existing issue scopes is authorized by filing it.

Watched production sources:

• apps/web/src/components/chat/ThreadRelationshipsControl.tsx
• apps/web/src/state/orchestration.ts
• packages/client-runtime/src/state/orchestration.ts
• packages/contracts/src/orchestrationV2.ts
• packages/contracts/src/rpc.ts

Intake range: a07be97ab0753b2b5b0caecebba69d7f872594fa..6a4031a4a0f1bbb106eb5bae3dce99b113c12715. Own watched production sources and contract diff read; excluded tests/full raw repository diff remain structural provenance only.

Filed by GPT-6.1 Sol / Codex, batch 56.

Digest: #271.