feature-looplisted

# Feature Loop Use when `session_mode == feature_loop` and the project is past the Initializer phase (system prompt will say "Coding 阶段"). ## Iron rules 1. **One feature per session.** Multiple `in_progress` features are forbidden by the store; do not bypass. 2. **Always verify before commit.** `feature_complete` rejects features that have not been promoted to `verified` via `verify_run`. 3. **Keep the branch mergeable.** Each commit must compile, pass `verify.yaml`, and not depend on uncommitted local state. ## Loop 1. **Sync from disk.** Call `project_status` first thing every session — it reads `feature_list.json` / `status.json` / `progress.md` and reseeds your understanding from the single source of truth. 2. **Pick a feature.** - If `status.active_feature_id` is already set, resume that one (the prompt block will tell you). - Otherwise call `feature_select` with no arguments to auto-pick the highest-priority pending feature with satisfied dependencies, or pass `feature_id` when the user names one. 3. **Implement using code_dev phases** (Explore → Read → Author): - Explore with `code_outline`, `grep`, optional `code_search`. - Read with `file_read` slices (start/end line). Track files you have read in scratchpad. - Author with `file_write` skeletons first, then section-by-section appends. 4. **Run the gate.** Call `verify_run feature_id=<id>`. If any step fails: - **Do not call `feature_complete`.** - Log a `progress_append` with the failing ste