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

@@ -1,12 +1,20 @@
 ---
 name: tech-debt
-description: "Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling."
+description: "Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register."
 argument-hint: "[scan|add|prioritize|report]"
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Write, AskUserQuestion
 model: sonnet
 ---
 
+!`source "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/yaml-helper.sh" 2>/dev/null && resolve_config --keys automation`
+
+
+
+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).
+
 ## Phase 1: Parse Subcommand
 
 Determine the mode from the argument:
@@ -41,6 +49,22 @@ Categorize each finding:
 - **Dependency Debt**: Outdated packages, deprecated APIs, version conflicts
 - **Performance Debt**: Known slow paths, unoptimized queries, memory issues
 
+**Before presenting anything, establish that there was something to scan.**
+Count the source files the scan actually covered. If that count is **zero** —
+no `src/` directory, or it holds no source files — report:
+
+> **NOT ASSESSED — no source files to scan.** `src/` contains no code, so
+> "no debt indicators found" would be a statement about an empty search, not
+> about the codebase. Run this once implementation is under way.
+
+and stop. Do not write to the register and do not emit a COMPLETE verdict.
+
+The distinction is the whole point of the scan: **zero findings over 400 files
+is a clean codebase; zero findings over zero files is no information at all.**
+Rendering both as "COMPLETE — scan findings written to register" reads as the
+first. State the denominator whenever findings are reported,
+including when it is large and the count is genuinely zero.
+
 Present the findings to the user.
 
 Ask: "May I write these findings to `docs/tech-debt-register.md`?"