abcd reserve lets a footprint path through when it is a file origin's default branch declares generated, but says nothing about it: a person reading the reservation cannot tell that it shares docs/reference/cli/commands.md with another live reservation, which the second lander must regenerate after merging main. The act names a shared path only when it backs off, warns of the person's own other copy, or cannot read the declaration.

Frontmatter

.abcd/work/issues/resolved/iss-2610282340087862-abcd-reserve-lets-a-footprint-path.md
open on GitHub ↗ · commit history ↗

mentions1

• dcn-26102900011041912026-10-29 — abcd reserve names each generated file a reservation shares with another record's live reservation (facilitator-on-delegation, iss-2610282340087862): the overlap judgement already lets a file origin's default branch declares linguist-generated through (dcn-2610170652481326), and now collects each such path with the other record, sorted by path then record; the reserve verb prints one shared: line per path on stdout, as a note rather than a stderr warning since nothing is wrong, and carries them as generated_shared in --json. Build and drain do not render it, as they render no other reservation note. The declaration stays the one root .gitattributes on origin's default branch, and freshness stays with TestReferenceMatchesCommittedPage and TestSurfaceSnapshotMatchesCommittedBaseline, so the second lander regenerates after merging. Grounds: loud staging, a stage that lets something through says so.