Release 1.1.0 — one config file, and a process weight you choose

`project.yaml` at the repo root is now the single source of truth for a
project's configuration, replacing `production/stage.txt`,
`production/review-mode.txt` and `.claude/docs/technical-preferences.md` (all
three still read as a fallback; nothing is force-deleted).

**`modes.rigor` — one question instead of six.** `minimal`, `standard` or
`full` fronts six knobs: `modes.workflow`, `docs.density`, `qa.level`,
`modes.story_granularity`, `modes.review_mode` and `team.size`. It defaults to
`minimal`, which is a change from 1.0's behaviour: the heavier tier was
measured costing several times more to reach working code without producing a
better result, and returning nothing when a fresh developer inherited the
project. Pin `modes.rigor: standard` to keep 1.0's process level.

Also in this release:

- `/settings` to view or change any setting, and `project.local.yaml` for
  per-developer preferences that should not be committed.
- `system_overrides` to hold one system to a higher standard than the rest of
  the project, and `testing.strict` to set per test type whether missing
  evidence blocks a story or warns.
- A story that changes anything the player sees is not closed until the game
  has been launched, observed, and a screenshot retained in
  `production/qa/evidence/`. A parse check is not a run. This holds at every
  rigor level, including `minimal`, where automated tests are waived but the
  look is not.
- The code root is engine-specific and enforced as such: Godot `src/`, Unity
  `Assets/`, Unreal `Source/<Module>/`. Two of the three will not build a
  project laid out any other way.
- Migration tooling for existing projects: `.claude/scripts/migrate-v1-config.sh`
  converts a 1.0 layout, non-destructively by default, with a report to review
  before `--finalize` deletes anything.
- Ask-before-write holds regardless of personal automation settings.

Upgrading from 1.0 or earlier: see UPGRADING.md. Full list of changes:
CHANGELOG.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016xvzG3i7pWQg4LjyDwWMXd

.claude/skills/regression-suite/SKILL.md

@@ -1,12 +1,18 @@
 ---
 name: regression-suite
-description: "Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate."
+description: "Map test coverage to GDD critical paths, find fixed bugs lacking regression tests, flag drift from new features."
 argument-hint: "[update | audit | report]"
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Write, Edit, AskUserQuestion
 model: sonnet
 ---
 
+!`source "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/yaml-helper.sh" 2>/dev/null && resolve_config --keys automation,workflow,qa.level,system_overrides`
+
+Resolved above — use as-is. No block → defaults in
+`.claude/docs/config-resolution.md`.
+
+
 # Regression Suite
 
 This skill ensures that every bug fix is backed by a test that would have
@@ -27,8 +33,30 @@ and known failure points. This skill maintains that list.
 
 ---
 
+Every `AskUserQuestion` call follows `.claude/docs/automation-modes.md`
+(collaborative asks always · guided major-only · autonomous logs and proceeds;
+`automation_always_ask` categories always prompt).
+
+**Workflow tier**: `modes.workflow` as resolved above — supplied by `modes.rigor`
+unless set explicitly — per `.claude/docs/workflow-modes.md`; in `audit` mode consider
+`workflow_overrides.system_overrides.<system>` per system as each GDD is read. It
+sets whether GDD critical paths are mapped or coverage is smoke-only — see Step 2c.
+
+**`qa.level`**: controls whether the suite is generated at
+all. At `minimal`, the regression suite is **not generated** (report that and
+stop); at `standard`, generate it at Polish-stage entry; at `full`, at
+Production-stage entry. Distinct axis from `workflow`.
+
 ## 1. Parse Arguments
 
+**Early `qa.level` guard (resolved above):** if `qa.level: minimal`, the
+regression suite is **not generated** — report "Regression suite not generated at
+qa.level minimal" and **STOP here, before any scan**, in every mode
+(`update` / `audit` / `report`). This is the `qa.level` axis; it is distinct from
+the `workflow`-tier `minimal` branch in Step 2c (which only changes the
+critical-path *source*, not *whether* the suite runs). Do not enter Step 2c's
+`minimal` branch on account of `qa.level`.
+
 **Modes:**
 - `/regression-suite update` — scan new bug fixes this sprint and check
   for regression test presence; add new tests to the suite manifest
@@ -70,8 +98,21 @@ Do not read test file contents unless needed for name-to-test mapping.
 
 ### Step 2c — Load GDD critical paths
 
-For `audit` mode: read `design/gdd/systems-index.md` to get all systems.
-For each MVP-tier system, read its GDD and extract:
+For `audit` mode: read `design/gdd/systems-index.md` to get all systems, then
+scope the scan by each system's workflow tier (resolved above):
+- **`full`** — read the GDD and map critical paths from all sections.
+- **`standard`** — same, from the required sections (Acceptance Criteria, Edge
+  Cases, and Formulas where the system defines numeric rules).
+  A system pinned higher via `system_overrides` is mapped at its higher tier.
+- **`minimal`** — **skip the GDD critical-path scan**. Instead read the latest
+  smoke-check report in `production/qa/smoke-*.md` and take the critical paths it
+  exercises as the regression scope (Step 3 maps coverage against those, not GDD
+  acceptance criteria). If no smoke report exists, report that and stop — there is
+  no critical-path source at minimal without one.
+
+(Tier affects `audit` mode only; `update` and `report` modes are tier-independent.)
+
+For each in-scope MVP-tier system's GDD, extract:
 - Acceptance Criteria (these define the critical paths)
 - Formulas section (formulas must have regression tests)
 - Edge Cases section (known edge cases should have regression tests)
@@ -90,7 +131,9 @@ or `Status: Fixed` field. Note:
 
 ## 3. Map Coverage — Critical Paths
 
-For `audit` mode only:
+For `audit` mode only. (At `minimal` the critical paths come from the smoke-check
+report identified in Step 2c, not from GDD acceptance criteria — map coverage
+against those smoke paths and skip the GDD-criterion loop below.)
 
 For each GDD acceptance criterion, determine whether a test exists:
 
@@ -179,6 +222,24 @@ Check for drift indicators:
 
 ### Suite manifest format (`tests/regression-suite.md`)
 
+> **Before computing coverage, check the denominator.** If the GDD
+> glob returns **zero critical paths**, or the test globs return **zero test
+> files**, do not emit a percentage — report
+> `Coverage: NOT ASSESSED — [no GDDs found | no test files found]` and name which
+> side was empty and the skill that produces it (`/map-systems` and
+> `/design-system` for GDDs, `/test-setup` for the test scaffold).
+>
+> A percentage computed from an empty denominator is not a low score; it is not a
+> number. `0%` reads as "measured and terrible" and `100%` as "measured and
+> perfect" — both are claims about a comparison that never happened. This is the
+> same defect `/scope-check` carries a Phase 4 guard against, in the same words:
+> *"a percentage computed from no baseline items is not a small number; it is not
+> a number."*
+>
+> **A hand-written list of skills required to carry `NOT ASSESSED` pins what was
+> known when it was written**, so a skill added later inherits no obligation and
+> nothing notices. Derive that set rather than enumerating it.
+
 The manifest is a curated index — not the tests themselves, but a registry
 of which tests should always pass before a release:
 
@@ -245,6 +306,10 @@ Verdict: **COMPLETE** — regression suite updated. (If user declined write: Ver
 
 ## Collaborative Protocol
 
+**Applies in `collaborative` mode (the default).** For `guided` and
+`autonomous` modes, see `.claude/docs/automation-modes.md` — the rules below
+describe what collaborative mode requires, not universal behavior.
+
 - **Never remove existing regression tests from the manifest** without
   explicit user approval — removing a test that was deliberately written is a
   regression risk itself