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

@@ -1,13 +1,82 @@
 ---
 name: changelog
-description: "Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions."
+description: "Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions."
 argument-hint: "[version|sprint-number]"
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Bash, Write
-context: |
-  !git log --oneline -30 2>/dev/null
-  !git tag --list --sort=-v:refname 2>/dev/null | head -5
-model: haiku
+model: sonnet
+---
+
+!`source "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/yaml-helper.sh" 2>/dev/null && resolve_config --keys automation`
+
+**Automation mode**: Resolve `modes.automation` (`project.local.yaml` →
+`project.yaml` → default `collaborative`). Every `AskUserQuestion` call and
+every file write follows `.claude/docs/automation-modes.md`
+(collaborative asks always · guided major-only · autonomous logs and proceeds;
+`automation_always_ask` categories always prompt).
+
+## Recent History
+
+Recent commits:
+
+!`git log --oneline -30 2>/dev/null`
+
+Recent tags (newest first):
+
+!`git tag --list --sort=-v:refname 2>/dev/null | head -5`
+
+## Provenance check — before trusting the history above
+
+**The commits above may not belong to this game.** This skill's history blocks are
+auto-resolved *before* the body runs, so the read has already happened — what this
+check governs is whether that output is usable, not whether it is fetched.
+
+1. Read the injected commit subjects above.
+2. **Classify each one** as **Game** (mechanics, content, balance, art, audio,
+   UI, or a bug in those), **Framework / maintenance** (subjects naming skills,
+   hooks, agents, the test plan, CI, or the framework's own docs), or **Unclear**
+   — and treat Unclear as Framework.
+3. Decide from the counts:
+   - **At least one Game commit** → proceed using only those, and state how many
+     of how many you used.
+   - **Zero Game commits** → stop, using the message below.
+
+> **Filter per commit; a repo containing maintenance work is not a wrong repo.**
+> Every project on this framework accumulates commits touching hooks, CI and
+> skills — the game repo *is* the framework repo. Listing those as a hard STOP
+> fires on virtually every real project and contradicts step 2 whenever the
+> history is mostly the game's. The harm is those commits becoming release copy,
+> and excluding them prevents that precisely.
+>
+> This rule is kept identical to `/patch-notes`' on purpose — the two read the
+> same history for different audiences, and they must not disagree about whose
+> history it is. Change both together.
+
+The genuine wrong-history signal is different: Game commits naming a product that
+`design/` and `src/` never mention. If you see that, stop.
+
+If **no** commit in the range is this game's, say so and stop:
+
+> "The git history in this repo does not appear to belong to [game]. The recent
+> commits describe [what they actually describe]. I cannot generate a changelog
+> from it — point me at the right history, or supply the change list directly."
+
+**Why this is a hard stop, not a warning.** This exact failure is real, not
+hypothetical: a batch of framework-internal commits produced player-facing copy
+reading *"Fixed an issue where progress from your last session could be lost on
+launch"* — a
+session-hook timeout rendered as a gameplay fix for a game with **no save
+system**. It was fluent, plausible, and entirely false. A reader cannot tell the
+difference; only this check can.
+
+**Do not treat the preamble's existence as evidence.** Injected output means the
+command ran, never that its subject is your game.
+
+---
+
+Both blocks are resolved before this skill runs. Use them as the starting point
+for Phase 2 rather than re-running the same commands.
+
 ---
 
 ## Phase 1: Parse Arguments
@@ -26,7 +95,11 @@ Read the git log since the last tag or release:
 git log --oneline [last-tag]..HEAD
 ```
 
-If no tags exist, read the full log or a reasonable recent range (last 100 commits).
+If no tags exist, bound the range explicitly — `git log --oneline -n 100`. Do not
+fall back to the full log: on an established repo that is thousands of lines for
+a changelog covering one release, and the oldest of them are the least relevant.
+If 100 commits does not reach far enough back, say so and ask for a start ref
+rather than widening blindly.
 
 Read sprint reports from `production/sprints/` for the relevant period to understand planned work and context behind changes.