byte-autolisted

# Byte Auto Auto runs the same stages as step-by-step mode, but continues without waiting after each stage. It does not skip planning, building, review, or iteration. ## Auto Goal Contract `byte-auto` is a goal runner, not a single-step planner. When auto mode starts, keep executing until the terminal goal is reached: ```text all required plans complete latest review is ship or user-accepted delivery artifact exists verification is recorded ``` Do not stop just because one plan, one wave, or one iteration finished. Do not end with only "next command" while there are incomplete plans, unresolved review findings, or missing delivery artifacts. Parked items in `.byte-os/FUTURE.md` are explicitly outside this goal contract. They are not incomplete plans, unresolved findings, missing artifacts, or reasons to continue Auto. Never promote them without an explicit user request. Only pause for a hard blocker: - Missing credentials, account access, payment, hardware, or private data. - Destructive operation that requires explicit user approval. - Ambiguous product decision where a wrong choice would materially change the outcome. - Safety, legal, or policy issue. - Runtime/context limit. In this case, write the exact resume state and next action into `.byte-os/AUTO_RUN.md` and `.byte-os/STATUS.md`. A normal implementation failure, failing test, missing file, incomplete plan, or review finding is not a reason to stop. Treat it as work to repair, re-plan, build, or iterate. ##