byte-buildlisted

# Byte Build Build executes plans. By default, it executes the next dependency-ready wave, not simply plan 001. ## Inputs Read: ```text .byte-os/STATUS.md .byte-os/plans/*.plan.md .byte-os/PRODUCT_SPEC.md .byte-os/UX_SPEC.md .byte-os/TECH_SPEC.md .byte-os/OKRS.md .byte-os/CODEBASE_MAP.md .byte-os/HARNESS.md .byte-os/AGENTS_AUDIT.md AGENTS.md and relevant module AGENTS.md files ``` If no plans exist, run or recommend `byte-plan`. ## Modes ```text byte-build ``` Execute the next wave whose dependencies are complete. ```text byte-build --wave N ``` Execute all ready plans in wave `N`. ```text byte-build --plan ID ``` Execute one plan only. ```text byte-build --all ``` Execute all waves until plans complete or a blocker appears. In `byte-auto`, `byte-build --all` is not allowed to be the final stop unless all plans are complete or a hard blocker has been recorded. If a plan is blocked because it is underspecified, missing a scoped command, or needs repair after a failed check, return control to `byte-auto` with the exact repair action so auto mode can re-plan, fix, and retry. ## Execution Rules - Inspect the repository before editing. - Never implement parked entries from `.byte-os/FUTURE.md`. Build only active plan scope; a future entry must be explicitly promoted and planned first. - For existing codebases, read the relevant `AGENTS.md`, `CLAUDE.md`, `.byte-os/CODEBASE_MAP.md`, `.byte-os/HARNESS.md`, and `.byte-os/AGENTS_AUDIT.md` before editing. - Before edi