itd-2609091034175565 hands reservation tombstone deletion to itd-118, whose scope covers PR branches and local residue only

itd-2609091034175565 hands reservation tombstone deletion to itd-118, whose scope covers PR branches and local residue only

A sequencing impossibility (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/drafts/itd-118-merged-work-leaves-no-residue-abcd.md:12 — "abcd tidies the stale local branch, tracking ref, and worktree"
• End B: .abcd/development/intents/shipped/itd-2609091034175565-nothing-tells-an-agent-that-a-record-it.md:250 — "Tombstone deletion lives in itd-118"

The shipped reservation intent rules that tombstone deletion lives in itd-118, because the cloud proxy rejects deletions. itd-118's stated scope is deleting a PR branch on merge and tidying the stale local branch, tracking ref and worktree; a reservation tombstone is a remote branch that no pull request owns. As written, itd-118 cannot deliver the deletion the shipped intent depends on.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1151.