setup-discipline

Run python3 tools/check_stage_ready.py, which auto-detects the current stage and audits it, reporting failures per item and listing what it cannot verify. The skill's per-stage checklists define the full contract beyond the tool's mechanical subset.

Check on-disk state: no models/<name>/ entry means Stage 2 (onboard-model), only templates in use_cases/ means Stage 1 (a2mc-init), and a real use case directory means Stage 3 (onboard-case) or an active session. The SessionStart hook also surfaces the stage automatically.

setup-discipline covers the setup arc (a2mc-init, onboard-model, onboard-case) before a campaign runs, while calibration-discipline is the per-cycle and per-round checklist for a campaign already in progress. They are the same habits layer at different phases.

The milestone was likely never registered in rag/milestones.json, or the RAG index was never committed because chroma.sqlite3 carries skip-worktree so a plain git add stages nothing. Both are checklist items in the Stage 2 definition of done.

Items can be marked N/A only with an explicit reason recorded in the stage's log, such as fork-safe remotes being N/A without upstream write access. A checked box means the check was actually run, not merely believed to hold.