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/docs/director-gates/td-change-impact.md

@@ -0,0 +1,25 @@
+> Gate definition. The spawning skill passes this file's path to the director agent; the AGENT reads it — the parent session should not.
+
+# TD-CHANGE-IMPACT — Design Change Impact Review
+
+Agent: `technical-director` | Model tier: Opus | Domain: Architecture, engine risk, performance
+
+**Trigger**: After the Design Change Impact Report is produced
+(`/propagate-design-change` Phase 6), before the resolution workflow begins
+
+**Context to pass**:
+- The full Design Change Impact Report from Phase 6 — change summary, every
+  affected ADR with its Still Valid / Needs Review / Likely Superseded
+  classification, and the recommended actions
+
+**Prompt**:
+> "Review this design-change impact assessment before any ADR is revised. Are the
+> impact classifications correct — in particular, is any ADR under-classified
+> (marked Still Valid when the change actually contradicts its assumptions)? Are
+> the recommended actions architecturally sound? Were any cascading effects on
+> other ADRs or systems missed — decisions that depend on the ones already
+> flagged? Return APPROVE, CONCERNS [the specific ADRs or recommendations to
+> revisit], or REJECT [the assessment must be re-analyzed before resolution
+> begins — say what was missed]."
+
+**Verdicts**: APPROVE / CONCERNS / REJECT