[Spec 83] rev. 12: retract the FR-3 finding

[pseudoseed]

Problem. Spec 83 recorded FR-3 as unsatisfiable and filed #97 against discoverBuilders. Both were wrong. FR-3 works.

Root cause. Rev. 4 measured GET /v2/events and got 13 builders, every one with parentId: "workspace:<path>", zero with an architect parent. That measurement was taken when the workspace had no live builders, so all 13 rows were orphaned worktrees. A missing global.db row read as a missing feature.

Re-measured with live builders present:

builders: 15   parent=architect: 2   parent=workspace: 13
architect-parented: [('bugfix-97','uiv2'), ('spir-83','uiv2')]

The 2 are the only rows in global.db.builders for that workspace. v2-projection.ts:95 joins getBuilders().spawnedByArchitect, not discoverBuilders, so the hardcoded null at overview.ts:602, 662, 697 never reaches the wire.

Fix. Goal 4 lists FR-3 as satisfied. The evidence table retracts finding 4. D13 keeps its instruction and replaces its justification.

The client behaviour does not change. D13 still says: render the parentId the wire sends, never infer one. Both parent shapes are real and both appear in one tree. The never-infer rule is now the more important half — name-matching those 13 orphans to uiv2 would have produced a plausible tree and buried the real defect.

What was actually there is filed as #100: a worktree with no global.db row can be seen by every surface and removed by none. afx cleanup -p 78 returns Builder not found for project, and git worktree remove is forbidden by the irreversible-acts rule. 13 have accumulated in this workspace and nothing prunes them.

Credit. builder-bugfix-97 was spawned to fix #97, investigated the stated cause, measured it against the live stream, and reported that the prescribed fix was a no-op — before writing any code. #97 is closed as already-working with no PR.

Testing

• Re-measured the live stream myself rather than accepting the builder's report; the numbers above are mine.
• Confirmed v2-projection.ts:95 joins getBuilders(), so discoverBuilders' null is not on the path.
• No behaviour change and no source change. Spec text only; builder-spir-83 needs no rework.

🤖 Generated with Claude Code