The build intent arms auto-merge wherever a queue gates the default branch; the build brief arms it only when a ruleset also requires a person's approval

The build intent arms auto-merge wherever a queue gates the default branch; the build brief arms it only when a ruleset also requires a person's approval

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/planned/itd-2609201916151817-one-verb-takes-a-single-intent-from.md:62 — "A pull request with auto-merge armed where the ruleset gates it through a queue, a pull request left open where it does not."
• End B: .abcd/development/brief/04-surfaces/34-build.md:785 — "where an active ruleset gates the default branch through a merge queue and an active ruleset on it requires a person's approval, it arms auto-merge with the queue's method; otherwise it leaves the pull request open for a person to merge (ruling AM1)"

Decision 3 of the build intent arms auto-merge wherever the ruleset gates the default branch through a queue, and leaves the pull request open otherwise. The build chapter cites decision 3 and ruling AM1. It arms auto-merge only where a queue gates the branch and a ruleset also requires a person's approval, and otherwise leaves the pull request open for a person. For a repository with a queue and no required approval, the two documents give opposite answers.

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