forge-build-alllisted

# forge-build-all Run the build loop across ALL remaining units, in order, until the build plan is complete or a unit fails. This is the autonomous, multi-unit version of `forge-build`. Because this runs many units without a human checkpoint between each, it is deliberately conservative: it builds strictly to each spec, verifies every unit, and **stops at the first failure** rather than barreling ahead on a broken foundation. ## Preconditions - The project is set up (run the detector via `forge-init` if unsure) and has a build plan at `context/specs/00-build-plan.md`. - Read once at the start for shared context: the entry point, `context/context-digest.md` (fall back to `architecture.md` if absent), `context/lessons.md` (if present), `code-standards.md`, and `progress-tracker.md`. Because this run spans many units, also read `architecture.md` in full before starting. Read `ui-context.md` when the first UI unit comes up — not before. If there is no build plan, stop and tell the user to run `forge-spec` first. ## Argument / scope of the run By default, build every unit that is not yet complete, in build-plan order. Text after the command narrows the scope, e.g. `/forge-build-all units 3 through 7`, `the next 3 units`, or `until unit 10`. Confirm the resolved scope (which units, in what order) with the user before starting the run. **Model recommendation:** when confirming the scope, list any units marked `[complexity: high]` in the build plan. Because this run