abcd <spc-N> on a bundle's shared spec reads the first member alone (describeSpec in internal/core/record/record.go): Links names only the intent: back-link, the closed branch's 'stays planned until' and 'the linked intent is' lines read that one member, and the readiness gate runs on it alone, so member 2 is never mentioned and, after member 1 is superseded, the page names a superseded record as the linked intent.

abcd <spc-N> on a bundle's shared spec reads the first member alone (describeSpec in internal/core/record/record.go): Links names only the intent: back-link, the closed branch's 'stays planned until' and 'the linked intent is' lines read that one member, and the readiness gate runs on it alone, so member 2 is never mentioned and, after member 1 is superseded, the page names a superseded record as the linked intent.

Grounds

• pursued: we expect a bundle spec's page to name every member and never a superseded one as the linked intent; shown wrong if the page for a bundle spec omits a live member or defers to a member that is not the one failing readiness