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/consistency-check/SKILL.md

@@ -1,12 +1,16 @@
 ---
 name: consistency-check
-description: "Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variables. Grep-first approach — reads registry then targets only conflicting GDD sections rather than full document reads."
+description: "Scan GDDs against the entity registry for cross-document conflicts. Grep-first approach targets conflicting sections, different stats."
 argument-hint: "[full | since-last-review | entity:<name> | item:<name>]"
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Write, Edit, Bash, AskUserQuestion
 model: sonnet
 ---
 
+!`source "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/yaml-helper.sh" 2>/dev/null && resolve_config --keys automation,workflow`
+
+
+
 # Consistency Check
 
 Detects cross-document inconsistencies by comparing all GDDs against the
@@ -28,6 +32,15 @@ catches too late.
 
 ---
 
+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`** (see `.claude/docs/workflow-modes.md`):
+- `full` — full entity-registry cross-check against all GDD sections.
+- `standard` — cross-check against the required sections only.
+- `minimal` — not meaningful (no GDDs to check).
+
 ## Phase 1: Parse Arguments and Load Registry
 
 **Modes:**
@@ -281,9 +294,15 @@ Then append the new conflict entries. Never skip logging — a missing file is n
 Silently append to `production/session-state/active.md` (create the file if it does not exist):
 
 ```
-<!-- CONSISTENCY-CHECK: [date] | GDDs checked: [N] | Conflicts found: [N] | Report: docs/consistency-report-[date].md -->
+<!-- CONSISTENCY-CHECK: [date] | GDDs checked: [N] | Conflicts found: [N] | Log: docs/consistency-failures.md -->
 ```
 
+> **Point at `docs/consistency-failures.md` — the file Phase 6 actually appends
+> to.** A breadcrumb is a pointer left for a future session to follow. One that
+> names a file nothing writes sends that session looking for conflict history it
+> will never find, and nothing errors along the way. Never invent a report
+> filename here.
+
 Then close with an `AskUserQuestion` widget:
 
 - **Prompt**: "Consistency check complete — [N] conflicts found. What next?"
@@ -293,7 +312,9 @@ Then close with an `AskUserQuestion` widget:
   - `[C] Run /design-review on the most conflicted GDD`
   - `[D] Stop here`
 
-Never end the skill with plain text. Always close with this widget.
+In collaborative and guided modes, never end the skill with plain text — always
+close with this widget. In autonomous mode, print the findings and recommended
+next step, then record via `log_decision` (no widget).
 
 ---