itd-94 has autonomous drain runs implementing intents; itd-82 defines drain as working issues only and leaves picking intents to `abcd build next`

itd-94 has autonomous drain runs implementing intents; itd-82 defines drain as working issues only and leaves picking intents to abcd build next

A terminology drift (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/shipped/itd-94-an-intent-that-is-not-planned-cannot-be.md:25 — "Autonomous drain runs get the same gate"
• End B: .abcd/development/intents/planned/itd-82-drain-ledger-triage.md:57 — "Picking among intents: abcd build next (itd-2609211116005482), the sibling run."

itd-94 says autonomous drain runs get the intent-readiness gate, so a drain there is a run that implements intents. itd-82 defines abcd drain over the open issue ledger and lists picking among intents as out of scope, the job of the sibling run abcd build next. 'Drain' means two different runs, and itd-82's drain never reaches the intent gate that itd-94 credits it with.

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

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262035127167. Same End A and the same root cause, drain reused for an intent-implementing run; itd-82 and the shipped drain agree that drain is issue-only, so the planned intent is the correct end and itd-94 the stale one.