The build intent says each invocation does one step; the build brief keeps 'step' for a spec's steps and calls one invocation's work a stage

The build intent says each invocation does one step; the build brief keeps 'step' for a spec's steps and calls one invocation's work a stage

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

• End A: .abcd/development/intents/planned/itd-2609201916151817-one-verb-takes-a-single-intent-from.md:21 — "every invocation reads the state, does one step, writes the state and exits"
• End B: .abcd/development/brief/04-surfaces/34-build.md:388 — "A spec's steps and a lane's stages are two words for two things"

The build intent says every invocation does one step and exits. Under BU1, the build chapter keeps 'step' for a spec's steps only, and what one invocation performs is a lane's stage, one move of the run. Read with the brief's vocabulary, the intent says each invocation lands a whole spec step, which the loop does not do.

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