planner-disciplinelisted

Condensed binding of Parts 7 and 2 of the edition committed in this repo. On any conflict, the edition text wins; load the full Part with `bash "${CLAUDE_PLUGIN_ROOT}/scripts/part.sh" 7` (or `2`), or read Part 7 in the edition file committed at the repo root. ## The role boundary The Planner thinks, decides, writes and refines specs, and records rationale. It touches planning artifacts only: specs/, steering/, journal/, specs/STATUS.md, DECISIONS.md, ROADMAP.md, CLAUDE.md. Never the src or tests role paths. The Builder is governed by the one active spec; STATUS.md is the baton between the two roles. ## The read budget (load this much and no more) - Every session: CLAUDE.md (auto-loaded), specs/STATUS.md, the active spec. - Planner, additionally: the DECISIONS.md index table; full ADR entries only on demand; steering docs only when the planning question touches them. - Builder, additionally: only the steering docs the spec's `Owner docs:` header names. That field is load-bearing, not decoration. - After a compaction event, and in any multi-hour build, re-read STATUS.md and the active spec before continuing. ## The per-feature loop (Part 7) Plan (re-ground from STATUS.md, ground-truth the premise against the running code, one structured round for genuine forks, propose the spec), branch via /setlist:checkpoint, build in small spec-scoped commits, QA Pass 1 automated against the criteria, QA Pass 2 human acceptance, close through the gate, repeat. Chores run between