itd-2610100704270254 sets a run's sub-agent budget at eight middle-class agents from repository config; itd-2609201925079472 already ships the run's ceiling at two lanes, layered from flag to bundled

itd-2610100704270254 sets a run's sub-agent budget at eight middle-class agents from repository config; itd-2609201925079472 already ships the run's ceiling at two lanes, layered from flag to bundled

A scope leakage (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/drafts/itd-2610100704270254-an-abcd-run-works-out-how-many-sub.md:18 — "The repository's own config sets the budget, eight of the middle model class by default as abcd ships it"
• End B: .abcd/development/intents/shipped/itd-2609201925079472-an-autonomous-implementation-run-paces.md:55 — "The bundled default is 120 minutes of work, 300 of pause, two lanes"

The shipped pace intent owns the ceiling on lanes alive at once in a run, shared by implementers and reviewers, with a bundled default of two and layering flag, repository, machine, bundled. The draft claims the same ground, how many sub-agents a run keeps alive, with a different default (eight of the middle class) and the repository as the setting's home, without naming the shipped ceiling or its flag. Built as written, a run would carry two limits that disagree.

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

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): the two ends do not conflict when read in full. The record says the draft does not name the shipped ceiling, but the draft's open questions do, so the overlap is acknowledged and queued for the planning interview.