create-anpunkit 2.1.0 → 2.3.0

package/template/.claude/commands/infra.md

@@ -3,16 +3,20 @@ description: Provision or verify Azure infrastructure. Generates Bicep, shows wh
 argument-hint: [provision | verify | update <what changed> | regenerate-env | auth-proof]
 ---
 
-Caveman ULTRA mode. You are the ORCHESTRATOR.
+compression: user (.claude/ref/compression.md). You are the ORCHESTRATOR.
 
 Action: $ARGUMENTS (default: "provision" if INFRA.md missing, "verify" if present)
 
+Only meaningful when docs/OVERVIEW.md has `infra_needed: true`. If
+`infra_needed: false`, tell me this project has no infra phase and STOP.
+
 ---
 
 ## PRE-FLIGHT
 
-1. Check `az account show` — if it fails, STOP.
-   Tell me: "Run `scripts/auth-setup.sh` first."
+1. Confirm cloud CLI auth per the project's knowledge doc (Azure:
+   `knowledge/azure.md` ritual — `bash scripts/auth-setup.sh`; materialize it if
+   absent). If it fails, STOP and tell me the exact command to run.
 
 2. Determine mode from $ARGUMENTS or default logic.
 

package/template/.claude/commands/log-decision.md

@@ -3,7 +3,7 @@ description: Record an architectural decision in docs/DESIGN_LOG.md. Use only wh
 argument-hint: [what changed]
 ---
 
-Caveman ULTRA mode.
+compression: user (.claude/ref/compression.md).
 
 Append an architectural decision to docs/DESIGN_LOG.md. Change: $ARGUMENTS
 

package/template/.claude/commands/log-issue.md

@@ -3,7 +3,7 @@ description: Log an error to docs/ISSUES.md with root cause + solution, in the c
 argument-hint: [short error description]
 ---
 
-Caveman ULTRA mode.
+compression: user (.claude/ref/compression.md).
 
 Append an entry to docs/ISSUES.md. Error: $ARGUMENTS
 

package/template/.claude/commands/overview.md

@@ -2,7 +2,7 @@
 description: Bootstrap a new project. Runs design-research, research review, double grill (incl. data/state flow), datasource-understanding baseline, and planning. Run once per project.
 ---
 
-Caveman ULTRA mode.
+compression: user (.claude/ref/compression.md).
 
 Recommended: run from plan mode (Shift+Tab). Planning agents are read-only by
 tool grant; plan mode adds a read-only gate on the main session too. Optional.
@@ -16,11 +16,17 @@ Goal: stand up a fresh project workspace with a well-grounded plan.
 ### Round 1 — Initial grill
 
 1. Run the `grill-me` skill to interrogate me. Goal: understand initial scope.
-   Cover: project purpose, success criteria, external services, Azure services
-   needed (type + sizing), region, deployment target (Azure or local for E2E),
-   known constraints, unknowns. ALSO establish:
+   Cover: project purpose, success criteria, external services, cloud/infra
+   services needed (type + sizing, if any), region, known constraints, unknowns.
+   ALSO establish:
+   - **project_type**: web app / desktop app / script / library / other. This
+     drives the deterministic flag derivation (step 6) and knowledge-doc
+     selection.
    - **has_frontend**: is there a browser-facing UI? If yes, what is the frontend
      root path (e.g. `src/web/`, `app/`)? This drives the mandatory-E2E path match.
+   - **deploy meaning**: what does "done and shipped" mean for this project —
+     cloud deploy (where?), package publish (which registry?), verified
+     install/run instructions, or none (why)? This sets `deploy_kind`.
    Do not stop early. Do not write OVERVIEW.md yet.
 
 Store the round-1 answers as working context — do NOT write OVERVIEW.md yet.
@@ -86,11 +92,23 @@ Store the round-1 answers as working context — do NOT write OVERVIEW.md yet.
    - Project purpose and success criteria
    - Scope and constraints (informed by research findings)
    - External services with confirmed capabilities/limits
-   - "Azure services" section: every service with expected SKU
-   - Deployment target (azure-deployed or local-docker for E2E)
+   - Cloud/infra services section: every service with expected SKU (if any)
    - `has_frontend: true|false` and, if true, the frontend root path
    - Known risks / open questions (if any remain)
 
+   PROJECT FLAGS (hard rule 10 — declared once here, recorded verbatim, never
+   re-derived later):
+   - `project_type: web app|desktop app|script|library|other` (declared in round 1)
+   - `infra_needed: true|false` — derived: application types (web app, desktop
+     app, service) → true; script / library → false. Overridable here with a
+     stated reason.
+   - `e2e_kind: browser|cli|http|library-api` — derived: has_frontend → browser;
+     backend/API service → http; script → cli; library → library-api.
+   - `deploy_kind: cloud-deploy|package-publish|install-run-verified|none(<reason>)`
+     (from the round-1 "deploy meaning" answer).
+   - `knowledge_docs:` — derived list: web app or has_frontend → `knowledge/webapp.md`;
+     Azure services declared OR Azure cloud-deploy → `knowledge/azure.md`; else empty.
+
    OVERVIEW.md is written HERE — after the re-grill, not before.
 
 7. Write docs/DATAFLOW.md — a state-transition table per key object, driven by the
@@ -112,13 +130,27 @@ Store the round-1 answers as working context — do NOT write OVERVIEW.md yet.
 
 8. Hand OVERVIEW.md + DATAFLOW.md + design-research findings to the `planner`
    subagent. PLAN.md MUST:
-   - Start with Phase 0 (infra setup) as the first entry (always).
-   - End with a final code phase that contains the deploy task block.
+   - Start with Phase 0 (infra setup) as the first entry IFF `infra_needed: true`;
+     when `infra_needed: false` there is no Phase 0 — Phase 1 is the first entry.
+   - End with a final code phase whose deploy task completes `deploy_kind`
+     (cloud deploy / package publish / verified install-run / none-with-reason).
    - For any phase whose `changes` touch the frontend root: include ≥1
      UI-existence acceptance criterion naming the specific user-visible
      interactive element the phase introduces (not "page renders 200").
    - Map each phase to the DATAFLOW transitions it is expected to make reachable.
 
+   The planner ALSO writes the up-front SKELETON spec files (v2.2, §5.44/§5.51):
+   one `docs/spec-phase-<n>.md` per public-surface phase (skip Phase 0 + pure
+   infra/config/doc phases), enumerating the case NAMES — happy path, each named
+   edge, each named failure + error code — for every `dataflow:` transition and
+   every `acceptance` criterion, with `TBD` values. The generated header transcludes
+   that phase's `acceptance:` line + in-scope `DATAFLOW.md` transition rows verbatim.
+
+8b. STAMP each skeleton's staleness hash: for every `docs/spec-phase-<n>.md` the
+   planner wrote, run `bash scripts/spec-staleness.sh stamp <n>`. This embeds the
+   hash of the transcluded acceptance line + transition rows so phase-time
+   `/phase` can detect upstream drift. (Values are filled per phase by `spec-author`.)
+
 9. Create docs/STATE.md:
 ```
 
@@ -126,15 +158,18 @@ Store the round-1 answers as working context — do NOT write OVERVIEW.md yet.
 
 phase: 0 (pending)
 completed: project bootstrapped — design research, research review, double grill (incl. data/state flow) done
-next: run /infra to provision Azure infrastructure
+next: <if infra_needed: "run /infra to provision infrastructure (Phase 0)"; else "run /phase 1">
 blocker: none
 
 ```
+   When `infra_needed: false`, set `phase: 1 (pending)` and the next line to
+   "run /phase 1".
 10. Create docs/ISSUES.md with header `# Issues` and `## Archived` section.
 
 11. Create empty docs/HISTORY.md.
 
-12. Create docs/INFRA.md from the template (populated by /infra).
+12. Create docs/INFRA.md from the template (populated by /infra). Skip when
+    `infra_needed: false`.
 
 13. Create docs/ENDPOINTS.md:
  ```
@@ -144,6 +179,13 @@ blocker: none
  ```
 
 Then stop and show me PLAN.md + DATAFLOW.md for approval before any phase starts.
-
-Remind me: "Run `/infra` next to provision the Azure environment (Phase 0) and
-run the one-time AUTH PROOF before starting Phase 1."
+EXTEND the approval surface (v2.2, §5.51 — one confirmation, no new gate): for each
+public-surface phase, list the transition/acceptance ids it covers and the enumerated
+case NAMES (no values). I confirm the case-name set is COMPLETE here — these names
+are the up-front behavioral contract; values get filled + reviewed per phase at
+`/phase` SPEC REVIEW.
+
+Remind me of the next step per `infra_needed`:
+- `infra_needed: true` → "Run `/infra` next to provision the environment (Phase 0)
+  and run the one-time AUTH PROOF before starting Phase 1."
+- `infra_needed: false` → "No infra phase — run `/phase 1` to start."

package/template/.claude/commands/phase.md

@@ -1,10 +1,10 @@
 ---
-description: Run one phase end-to-end. TDD phases run SCAFFOLD -> RED -> TEST REVIEW -> GREEN; non-TDD phases run IMPLEMENT -> TEST. Both with the debug circuit breaker and the regression + dataflow + evidence guards at CLOSE.
+description: Run one phase end-to-end. TDD phases run SPEC fill -> SPEC REVIEW -> SCAFFOLD -> RED -> conformance -> GREEN -> boundary/E2E; non-TDD phases run IMPLEMENT -> TEST. Both with the debug circuit breaker and the regression + dataflow + evidence guards at CLOSE.
 argument-hint: [phase number]
 ---
 
-Caveman ULTRA mode. You are the ORCHESTRATOR. Route work to subagents —
-you do NOT implement or debug yourself.
+compression: user (.claude/ref/compression.md). You are the ORCHESTRATOR. Route work to subagents —
+you do NOT implement, fill specs, or debug yourself.
 
 Note: subagents cannot talk to the user. Only YOU can.
 
@@ -14,8 +14,9 @@ Target phase: $ARGUMENTS  (default: the phase marked pending in docs/PLAN.md)
 
 ## 0. PRE-FLIGHT
 
-a. INFRA CHECK (phases > 0):
-   - Read docs/INFRA.md. If Phase 0 not done -> STOP.
+a. INFRA CHECK (phases > 0): read docs/OVERVIEW.md `infra_needed`.
+   - `infra_needed: false` -> no Phase 0 exists; SKIP this check entirely.
+   - `infra_needed: true`: read docs/INFRA.md. If Phase 0 not done -> STOP.
      Tell me: "Phase 0 (infra) not complete. Run `/infra` first."
    - Exception: if $ARGUMENTS is "0", tell me to run `/infra` directly.
 
@@ -29,20 +30,26 @@ b. PHASE STATE CHECK: Read docs/STATE.md and docs/PLAN.md.
 c. FINAL PHASE CHECK: Read docs/PLAN.md. Is this the last phase (no further
    pending phases after this one)? Record this as IS_FINAL_PHASE=true/false.
 
-d. AUTH LIVENESS GATE (hard rule 16 — replaces the old soft nudge): if this phase
-   will run a real/E2E suite, confirm every credential it needs is live NOW.
+d. AUTH LIVENESS GATE (hard rule 16): only if this phase touches a credentialed
+   external service and will run a boundary/E2E suite. Skip otherwise.
    - If INFRA.md has no `AUTH PROOF: PASS` marker -> STOP: "Auth never proven
      reusable. Run `/infra` first."
-   - Run `scripts/auth-setup.sh --check` (Entra token obtainable + not expired)
-     and, for each external system this phase touches (docs/DATAFLOW.md external
-     rows + docs/ENDPOINTS.md auth column), confirm its credential is obtainable
-     headlessly. Any failure -> real/E2E is BLOCKED; tell me what to run; the
+   - Run the liveness command recorded in docs/INFRA.md `## AUTH` (Azure projects:
+     the ritual per `knowledge/azure.md`, i.e. `bash scripts/auth-setup.sh`) and,
+     for each external system this phase touches (docs/DATAFLOW.md external rows +
+     docs/ENDPOINTS.md auth column), confirm its credential is obtainable
+     headlessly. Any failure -> boundary/E2E is BLOCKED; tell me what to run; the
      MOCK suite may still proceed.
 
 e. FRONTEND TRIGGER (hard rule 13): read docs/OVERVIEW.md `has_frontend` + the
    frontend root. Set FRONTEND_PHASE=true iff `has_frontend: true` AND this
    phase's `changes` (docs/PLAN.md) include any path under the frontend root.
-   This is a PATH MATCH, not a judgment call. Record FRONTEND_PHASE for the GATE.
+   This is a PATH MATCH, not a judgment call. Record FRONTEND_PHASE — it gates the
+   `ui` boundary run + evidence at CLOSE.
+
+f. FLAG BASELINES: read docs/OVERVIEW.md `e2e_kind` + `deploy_kind`. These are the
+   project baselines; §1 binds this phase's effective E2E_KIND and (final phase)
+   confirms DEPLOY_KIND.
 
 ---
 
@@ -57,8 +64,9 @@ datasource, compare what it touches to the confirmed BASELINE in
 docs/research/datasource-<name>.md. If it touches a NEW table/column beyond the
 baseline -> surface my understanding of just that delta as a falsifiable claim;
 WAIT for confirm; append it to datasource-<name>.md. If it touches only confirmed
-data -> proceed with a one-line note, no stop. Real/E2E against an UNCONFIRMED
-datasource is HARD-BLOCKED (mock still runs).
+data -> proceed with a one-line note, no stop. Boundary/E2E against an UNCONFIRMED
+datasource is HARD-BLOCKED (mock still runs). The confirmed baseline is what
+`spec-author` grounds fixtures in.
 
 Then classify the phase:
 
@@ -66,63 +74,115 @@ Then classify the phase:
   exported function/class, CLI command, message contract) assertable from the
   acceptance spec. Size is NOT the criterion.
 
-- Clear public surface -> `TDD_PHASE=true` -> run the TDD path (§2 → §3a → §3r → §3b).
+- Clear public surface -> `TDD_PHASE=true` -> run the TDD path (§2 → §3 → §4 → §5 → §6 → §7).
 - Pure infra/config/doc, no public surface -> `TDD_PHASE=false` -> run the
   non-TDD path (§2N → §3N).
 - AMBIGUOUS -> default `TDD_PHASE=true`, but STATE the classification + the reason
-  to me, so I can override to non-TDD BEFORE SCAFFOLD fires. (Hard rule 11: never
-  downgrade a TDD phase just to dodge the RED gate.)
+  to me, so I can override to non-TDD BEFORE SPEC fill fires. (Hard rule 11: never
+  downgrade a TDD phase just to dodge the gates.)
+
+FLAG BINDING (hard rule 10): bind this phase's effective E2E_KIND — `browser` iff
+FRONTEND_PHASE, else the OVERVIEW `e2e_kind` baseline. If IS_FINAL_PHASE, restate
+`deploy_kind` and confirm the final phase's deploy task realizes it. STATE both
+bindings. Divergence from OVERVIEW is mine to resolve — never silently re-derived.
 
 =====================================================================
 ## TDD PATH  (TDD_PHASE=true)
 =====================================================================
 
-## 2. SCAFFOLD
+## 2. SPEC FILL + STALENESS
+
+a. SKELETON CHECK: confirm docs/spec-phase-<n>.md exists (planner generated it at
+   /overview). If MISSING (planner classified it non-TDD, or it's a new phase from
+   /replan): generate the skeleton NOW from this phase's PLAN.md `acceptance` +
+   `dataflow:` transitions in the planner skeleton format (generated header + named
+   `TBD` rows), then `bash scripts/spec-staleness.sh stamp <n>` to stamp its hash.
+
+b. Dispatch `spec-author`. It fills each case row with a real input payload
+   (`fixtures/<case-id>-input.json`), concrete expected output
+   (`fixtures/<case-id>-expected.json`), matcher tokens for volatile fields,
+   `error-code` for failures, and `selector/assert/value` `ui` descriptors —
+   grounded in the RESEARCH findings + the confirmed datasource baseline.
+
+c. CASE-SET-DIVERGENCE (hard re-entry, hard rule 12 / §5.52): if `spec-author`
+   returns `CASE-SET-DIVERGENCE` (a required case can't be filled from real facts,
+   or research revealed an unlisted/contradicted case) -> STOP. Surface the finding.
+   I amend the up-front case-name contract in the skeleton; you re-stamp
+   (`bash scripts/spec-staleness.sh stamp <n>`); then re-dispatch `spec-author` to
+   re-fill from scratch. AI never amends the case-name set — I own the contract.
+
+d. STALENESS (hard rule 17): run `bash scripts/spec-staleness.sh <n>`. Nonzero
+   (upstream PLAN acceptance line / DATAFLOW rows drifted since the skeleton was
+   stamped, e.g. via /replan) -> regenerate the skeleton header from current
+   PLAN/DATAFLOW, re-stamp, re-dispatch `spec-author`. Do NOT hand-edit the hash.
+
+## 3. SPEC REVIEW — human gate (hard rule 12)
+
+STOP. Surface the FILLED cases to me as FALSIFIABLE CLAIMS in plain language, e.g.:
+  - "POST /orders/submit with an empty line-item list → 422 EMPTY_ORDER."
+  - "Successful submit of a 3-line order → 201; order.id is a UUID; order.status is
+    'submitted'."
+Re-run `bash scripts/spec-staleness.sh <n>` at entry (nonzero -> back to §2d).
+SCAFFOLD cannot begin until I confirm. Classify any rejection WITH me (§5.50):
+  - WRONG EXPECTED -> fix the case row + `fixtures/<case-id>-expected.json`; no
+    re-research. (You may patch the fixture directly per my correction.)
+  - WRONG INPUT SHAPE -> re-dispatch `spec-author` with the correction.
+  - NEW CASE or CONTRADICTED CASE -> hard re-entry (§2c): I amend the skeleton, you
+    re-stamp, re-confirm the amended case(s) + any case sharing their `covers` id
+    (the staleness hash certifies the unchanged remainder — not re-read), re-fill.
+Loop until I approve. Unskippable on TDD phases.
+
+## 4. SCAFFOLD
 
 Dispatch `implementer` in SCAFFOLD mode: interface stubs only (signatures +
-types; bodies raise NotImplementedError / return 501); NO logic, NO tests.
-Returns the stub files + the interface surface.
+types; bodies raise NotImplementedError / return 501); NO logic, NO tests, NO
+edits to the spec or fixtures. Returns the stub files + the interface surface.
+
+## 5. RED
 
-## 3a. RED
+Dispatch `test-author` to EMIT the boundary harness from the locked spec `data`
+rows: one deep-equality assertion per case against `fixtures/<case-id>-expected.json`
+via the kit comparator `tests/helpers/spec-assert.*`, each citing its case with a
+`# spec: <case-id>` comment. It does NOT author assertions — it generates them from
+the spec. Place contract/ENDPOINTS/transition tests in `tests/regression/`,
+phase-local in `tests/phase-<n>/`.
 
-Dispatch `test-author` to write the REAL API suite (+ mock) BLIND against the
-stubs + acceptance, AND emit docs/test-plan-phase-<n>.md (acceptance criteria →
-test names, plus a mandatory "NOT covered / assumptions" section). Place
-contract/ENDPOINTS/DATAFLOW-transition tests in `tests/regression/`, phase-local
-tests in `tests/phase-<n>/`. Run the suite.
+If FRONTEND_PHASE (and the phase has `ui` cases): also dispatch `e2e-runner` to EMIT
+Playwright assertions from each `ui` case's `fixtures/<case-id>-ui.json` descriptor,
+each citing `// spec: <case-id>`. Run the suites.
 
-RED GATE = every acceptance test COLLECTS cleanly AND FAILS (assertion /
-NotImplemented).
-- Any test PASSES on stubs -> STOP (spec trivial or test wrong); show me.
+RED GATE = every case test COLLECTS cleanly AND FAILS (assertion / NotImplemented).
+- Any test PASSES on stubs -> STOP (spec trivial or emitter wrong); show me.
 - Collection / import / syntax error -> stub mismatch; re-dispatch SCAFFOLD to
   fix SIGNATURES (not logic); re-run.
-- UNDERSPEC -> STOP; ask me to sharpen the acceptance spec.
 
-## 3r. TEST REVIEW — human gate (hard rule 12)
+## 6. CONFORMANCE GATE (hard rule 18) — replaces the v2.1 human TEST REVIEW
 
-STOP. Surface docs/test-plan-phase-<n>.md to me: what each acceptance criterion
-maps to, and the "NOT covered / assumptions" section. GREEN cannot begin until I
-approve. On rejection, classify with me:
-  - MISREAD of an adequate spec -> re-dispatch `test-author` with my feedback as
-    added constraint; re-run RED; re-present the test plan.
-  - UNDERSPEC (the acceptance spec itself is too vague) -> sharpen the acceptance
-    spec in docs/PLAN.md, then re-dispatch `test-author` fresh.
-Loop until I approve. This gate is unskippable on TDD phases.
+Run `bash scripts/spec-conformance.sh <n>`. It loud-fails (and BLOCKS GREEN) if:
+  - any `TBD` marker remains in docs/spec-phase-<n>.md or a referenced fixture, OR
+  - any case-id in the spec table has no boundary test citing it (`# spec: <case-id>`).
+Nonzero -> fix the gap (re-dispatch `spec-author` for a stray TBD, or `test-author`/
+`e2e-runner` for a missing citation) and re-run. GREEN cannot start until it passes.
 
-## 3b. GREEN
+## 7. GREEN + BOUNDARY/E2E
 
-Dispatch `implementer` in FILL mode with the phase spec + research + the test
-file paths (it MAY read the tests — frozen before logic, no overfit — but must
-NOT edit them). Fill to green. Budget 3, WARN@2, STUCK@3.
+Dispatch `implementer` in FILL mode with the FILLED docs/spec-phase-<n>.md + its
+fixtures + research + the generated test file paths (it MAY read the tests — frozen
+before logic, no overfit — but must NOT edit tests, spec, or fixtures). Fill to
+green against the spec. Budget 3, WARN@2, STUCK@3.
 
-If FRONTEND_PHASE (from PRE-FLIGHT e): dispatch `e2e-runner` — MANDATORY, not
-optional (hard rule 13). It reads INFRA.md target, runs `scripts/e2e-stack.sh up`
-/ Playwright / `down`, and captures a screenshot at EACH UI-existence assertion
-regardless of pass/fail to docs/evidence/e2e-phase-<n>/, with a summary in
-docs/research/e2e-<slug>.md. Acceptance spec has no UI-existence criterion ->
-e2e-runner returns UNDERSPEC -> STOP, sharpen the spec.
+Run the BOUNDARY suite (real HTTP/CLI/message; `TEST_MODE=real`) — the outer surface
+per this phase's bound E2E_KIND. Capture evidence (hard rule 13):
+- `browser` (FRONTEND_PHASE): dispatch `e2e-runner` to run its emitted `ui` specs —
+  MANDATORY — reads INFRA.md target, runs the stack ritual per `knowledge/webapp.md`
+  (`scripts/e2e-stack.sh up` / Playwright / `down`), captures a screenshot at EACH
+  UI-existence assertion regardless of pass/fail to docs/evidence/e2e-phase-<n>/,
+  with a summary in docs/research/e2e-<slug>.md.
+- `cli` / `http` / `library-api`: the real-mode boundary suite IS the outer run;
+  capture its transcript (invocation + result) to docs/evidence/e2e-phase-<n>/.
+  No separate emitter is dispatched.
 
-PHASE GATE (rule 5) -> go to §4/§5/§6 (see GATE below).
+PHASE GATE (rule 5) -> go to §8/§9/§10 (see GATE below).
 
 =====================================================================
 ## NON-TDD PATH  (TDD_PHASE=false)
@@ -133,22 +193,24 @@ PHASE GATE (rule 5) -> go to §4/§5/§6 (see GATE below).
 Dispatch `implementer` (legacy mode) with phase spec + research summary.
 Returns STUCK -> go to ESCALATE.
 If IS_FINAL_PHASE: phase spec includes the deploy task; confirm the return
-includes "deployed URL" before proceeding.
+realizes `deploy_kind` (deployed URL / published version / verified install-run)
+before proceeding.
 
 ## 3N. TEST (blind)
 
-Dispatch `test-author`. It writes MOCK + REAL API suites from the acceptance
-spec — never reads the logic. (No TEST REVIEW gate on the non-TDD path — no
-public surface to mis-test. e2e-runner only if FRONTEND_PHASE.)
+Dispatch `test-author`. It writes MOCK + boundary suites from the acceptance
+spec — never reads the logic. (No spec file, SPEC REVIEW, or conformance gate on
+the non-TDD path — no public surface to contract. e2e-runner only if FRONTEND_PHASE.)
 
 =====================================================================
 
 ## GATE (both paths)
 
-PHASE GATE = current-phase REAL API suite passes AND (FRONTEND_PHASE) E2E passes
-WITH evidence captured AND the accumulated mock regression corpus stays green AND
-every docs/ENDPOINTS.md entry has a regression test AND every REACHABLE
-docs/DATAFLOW.md transition has a regression test (all checked at CLOSE).
+PHASE GATE = current-phase BOUNDARY suite passes AND (FRONTEND_PHASE) the `ui`
+boundary passes WITH evidence captured AND the accumulated mock regression corpus
+stays green AND every docs/ENDPOINTS.md entry has a regression test AND (TDD)
+`spec-conformance.sh` passed AND every REACHABLE docs/DATAFLOW.md transition has a
+filled case in the phase spec (all checked at CLOSE).
 - GATE PASS -> go to CLOSE.
 - GATE BLOCKED (SERVICE UNAVAILABLE, STACK NOT READY, AZURE UNAVAILABLE, FLAKE)
   -> tell me, wait. Not a code bug. For AZURE UNAVAILABLE: suggest `/infra verify`.
@@ -156,17 +218,17 @@ docs/DATAFLOW.md transition has a regression test (all checked at CLOSE).
 
 ---
 
-## 4. FIX
+## 8. FIX
 
 Dispatch `debugger` (isolated context) on the specific failure.
-- FIXED -> re-run TEST (and the regression corpus).
+- FIXED -> re-run the boundary suite (and the regression corpus).
 - SERVICE UNAVAILABLE -> tell me, wait. Suggest `/infra verify` if Azure.
 - WARN (2 attempts failed) -> relay immediately, then let debugger finish attempt 3.
 - STUCK -> go to ESCALATE.
 
 ---
 
-## 5. ESCALATE — circuit breaker. Mode B.
+## 9. ESCALATE — circuit breaker. Mode B.
 
 FIRST STUCK: STOP. Present to me: the problem, 3 failed hypotheses, the
 debugger's recommendation, the debug file path. Ask what to do. Wait. Options:
@@ -179,20 +241,25 @@ what to try next. Hand control to me.
 
 ---
 
-## 6. CLOSE
+## 10. CLOSE
 
 REGRESSION + COVERAGE GATES (before closing — all FAIL HARD, do not close):
-- Run `scripts/regression.sh` (mock corpus). A failure BLOCKS close -> route to FIX.
+- Run `bash scripts/regression.sh` (mock corpus). A failure BLOCKS close -> route to FIX.
 - ENDPOINTS COVERAGE: every `docs/ENDPOINTS.md` entry MUST have >=1 test in
   `tests/regression/`. Zero coverage -> FAIL HARD.
-- DATAFLOW COVERAGE (hard rule 14): every `docs/DATAFLOW.md` transition whose
-  trigger is REACHABLE in the code shipped so far MUST have >=1 test in
-  `tests/regression/`. Zero coverage on a reachable transition -> FAIL HARD.
-  Unreachable transitions list as PENDING (not failed). IF IS_FINAL_PHASE: any
-  transition still PENDING -> FAIL HARD (everything must be live by the last phase).
-- EVIDENCE (FRONTEND_PHASE only, hard rule 13): docs/evidence/e2e-phase-<n>/ must
-  contain at least the per-UI-existence-assertion screenshots. Empty -> FAIL HARD.
-- IF IS_FINAL_PHASE: additionally run `scripts/regression.sh --real` (full real
+- DATAFLOW COVERAGE (hard rule 14, re-seamed v2.2): every `docs/DATAFLOW.md`
+  transition whose trigger is REACHABLE in the code shipped so far MUST have >=1
+  FILLED CASE in docs/spec-phase-<n>.md. Zero coverage on a reachable transition ->
+  FAIL HARD. Unreachable transitions list as PENDING (not failed). IF
+  IS_FINAL_PHASE: any transition still PENDING -> FAIL HARD. (The case→test half is
+  already enforced by `spec-conformance.sh` at §6 — every case-id is cited by a
+  boundary test, which by placement lands in tests/regression/.)
+- EVIDENCE (hard rule 13): docs/evidence/e2e-phase-<n>/ must contain the boundary
+  run's evidence — per-UI-existence-assertion screenshots for `browser`, or the
+  captured boundary-run transcript for `cli`/`http`/`library-api`. Required whenever
+  this phase closes an E2E_KIND boundary (browser: FRONTEND_PHASE; others: the phase
+  ships/changes the outer surface). Empty when required -> FAIL HARD.
+- IF IS_FINAL_PHASE: additionally run `bash scripts/regression.sh --real` (full real
   corpus). A failure blocks close.
 
 Mark phase `done` in docs/PLAN.md.
@@ -202,31 +269,35 @@ ARCHITECTURE / DATAFLOW SELF-CHECK:
   workflow rule? YES -> run `/log-decision`. NO -> state why not.
 - Did this phase add/change an object's STATE LIFECYCLE? YES -> update
   docs/DATAFLOW.md (hard rule 9) in this CLOSE, and confirm new reachable
-  transitions are covered. NO -> state why not.
+  transitions are covered by a filled case. NO -> state why not.
 
 IF IS_FINAL_PHASE — FINAL CLOSE sequence:
 
   a. Run `/synthesize` — pass the signal that this is the final phase so the
      synthesizer runs the extended pass (OVERVIEW.md + README.md update).
 
-  b. Read docs/ENDPOINTS.md. Surface a "READY TO USE" summary to me:
+  b. Surface a "READY TO USE" summary to me, shaped by `deploy_kind`:
      ```
      ✅ PROJECT COMPLETE
 
-     Deployed at: <base URL from docs/INFRA.md "Deployed base URL">
+     <deploy_kind line:
+       cloud-deploy         -> Deployed at: <base URL from docs/INFRA.md "Deployed base URL">
+       package-publish       -> Published: <package name> @ <version> to <registry>
+       install-run-verified  -> Verified install/run: <the exact commands, confirmed working>
+       none(<reason>)        -> Not shipped: <reason>>
 
-     ## Endpoints
-     <paste the full docs/ENDPOINTS.md table>
+     ## Interface
+     <web/http: paste the full docs/ENDPOINTS.md table; cli: the command surface;
+      library: the public API surface>
 
      ## Quick start
-     - Base URL: <URL>
-     - Auth: <Bearer token / API key / none — from ENDPOINTS.md>
-     - Health check: GET <base URL>/health
+     <how to use it, per deploy_kind — base URL + auth + health check for a service;
+      install + invoke for a CLI; import + call for a library>
 
      ## Docs
-     - Full endpoint catalogue: docs/ENDPOINTS.md
+     - Full interface catalogue: docs/ENDPOINTS.md
      - Object/state flow: docs/DATAFLOW.md
-     - Infrastructure: docs/INFRA.md
+     - Infrastructure: docs/INFRA.md (if infra_needed)
      - Project history: docs/HISTORY.md
      ```
   Tell me the project is complete and ready to use.
@@ -246,6 +317,7 @@ After each step, update docs/STATE.md:
 phase: <n> (in progress)
 tdd: <true|false>
 frontend_phase: <true|false>
+e2e_kind: <browser|cli|http|library-api — the bound value>
 completed: <steps done so far>
 next: <exact next step>
 blocker: <none or open issue>

package/template/.claude/commands/quick.md

@@ -3,7 +3,7 @@ description: Make a small, obvious change directly — no agent chain, no phase
 argument-hint: [what to change]
 ---
 
-Caveman ULTRA mode. Apply `karpathy-guidelines` skill.
+compression: user (.claude/ref/compression.md). Apply `karpathy-guidelines` skill.
 
 Purpose: skip the orchestration tax for a 5-line fix.
 

package/template/.claude/commands/replan.md

@@ -3,7 +3,7 @@ description: Revise docs/PLAN.md when it no longer matches reality — add, cut,
 argument-hint: [what changed about the plan]
 ---
 
-Caveman ULTRA mode.
+compression: user (.claude/ref/compression.md).
 
 Recommended: run from plan mode (Shift+Tab). Optional; the command stops for
 your approval regardless.

package/template/.claude/commands/store-wisdom.md

@@ -2,7 +2,7 @@
 description: Promote resolved issues and research findings from this project to the shared anpunkit-kb repo. Analyzes, proposes candidates for your review, then pushes approved entries.
 ---
 
-Caveman ULTRA mode. You are the ORCHESTRATOR.
+compression: user (.claude/ref/compression.md). You are the ORCHESTRATOR.
 
 Purpose: share what this project learned with all future projects.
 Only resolved issues and completed research qualify. Open issues do NOT.

package/template/.claude/commands/synthesize.md

@@ -2,7 +2,7 @@
 description: Compress handoff docs, dedup the issue log, prune snapshots. Run before /clear.
 ---
 
-Caveman ULTRA mode.
+compression: user (.claude/ref/compression.md).
 
 Trigger: end of a phase, or any time STATE.md / ISSUES.md feel bloated.
 

package/template/.claude/commands/unstuck.md

@@ -2,7 +2,7 @@
 description: Forced re-research after a circuit breaker. Stops flailing, re-routes to deep research with full memory of dead ends.
 ---
 
-Caveman ULTRA mode.
+compression: user (.claude/ref/compression.md).
 
 Trigger: I chose "re-research" at a circuit breaker (see /phase step 5).
 

package/template/.claude/hooks/session-start.sh

@@ -44,17 +44,11 @@ if [ -f docs/research/INDEX.md ]; then
   emit ""
 fi
 
-# 3c. infra status + auth nudge
+# 3c. infra status
 if [ -f docs/INFRA.md ]; then
   INFRA_STATUS=$(grep -m1 '^phase 0:' docs/INFRA.md 2>/dev/null || true)
-  PROJECT_HASH=$(echo "$PWD" | md5sum 2>/dev/null | cut -c1-8 || echo "anpunkit")
-  MARKER="/tmp/anpunkit-auth-${USER:-unknown}-${PROJECT_HASH}"
-  if [ ! -f "$MARKER" ]; then
-    emit "## Azure infra present — auth check needed"
-    emit "Run scripts/auth-setup.sh once this session before any Azure work."
-    if echo "$INFRA_STATUS" | grep -qi 'NOT DONE'; then
-      emit "Phase 0 not complete — run /infra to provision before starting phase 1."
-    fi
+  if echo "$INFRA_STATUS" | grep -qi 'NOT DONE'; then
+    emit "## Infra: Phase 0 not complete — run /infra to provision before starting phase 1."
     emit ""
   fi
 fi
@@ -121,12 +115,12 @@ fi
 
 # 4. hard rule reminder
 emit "## RULES (enforced this session)"
-emit "- caveman ULTRA mode is active."
+emit "- compression active: profile user (.claude/ref/compression.md); subagents run profile internal."
 emit "- before debugging ANY error: grep ISSUES.md AND research/INDEX.md first."
 emit "- debug attempts: WARN at 2; first hard-stop at 3 STOPS and asks you."
 emit "- end of every phase: run /synthesize, then /clear."
 emit "- small obvious change? use /quick, not /phase."
-emit "- Azure project? run scripts/auth-setup.sh once per session before Azure work."
+emit "- infra project (infra_needed)? run the INFRA.md AUTH liveness command once per session before real/E2E work."
 if [ -f "$KB_CONFIG" ]; then
   emit "- KB active: researcher checks docs/.kb-snapshot.md before web search."
   emit "- learned something worth keeping? run /store-wisdom."