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/hooks/notify.sh

@@ -1,4 +1,32 @@
 #!/usr/bin/env bash
+
+# --- work from the project root ----------------------------------------------
+# Every path below is repo-relative, so a hook invoked with a working directory
+# that is not the repo root would silently read and write the WRONG TREE --
+# returning a near-empty result instead of the session-recovery block, and
+# creating stray trees such as docs/production/session-logs/ on write.
+#
+# PRECEDENCE IS LOAD-BEARING. A cwd that IS a project root carries real
+# information and must win: a caller sitting inside another project means that
+# project, not this one. Resolving to the script's own location first would
+# override them. So, in order:
+#   1. cwd holds project.yaml   -> cwd   (a project root)
+#   2. cwd holds .claude/       -> cwd   (a project root not yet configured)
+#   3. CLAUDE_PROJECT_DIR       -> that  (populated in the hook environment)
+#   4. this script's location   -> <root>/.claude/hooks/../.. by construction
+# Rule 4 always works and needs no environment at all; rules 1-2 stop it from
+# overriding a caller that legitimately means somewhere else.
+#
+# NOT an upward search: that resolves a nested project to its parent's config.
+if [ -f "project.yaml" ] || [ -d ".claude" ]; then
+  CCGS_ROOT="$PWD"
+elif [ -n "${CLAUDE_PROJECT_DIR:-}" ] && [ -d "${CLAUDE_PROJECT_DIR}" ]; then
+  CCGS_ROOT="$CLAUDE_PROJECT_DIR"
+else
+  CCGS_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." 2>/dev/null && pwd)"
+fi
+[ -n "$CCGS_ROOT" ] && cd "$CCGS_ROOT" 2>/dev/null || true
+
 # Notification hook — fires when Claude Code sends a notification
 # Shows a Windows toast via PowerShell
 
@@ -9,15 +37,24 @@ INPUT=$(cat)
 if command -v jq &>/dev/null; then
   MESSAGE=$(echo "$INPUT" | jq -r '.message // empty' 2>/dev/null)
 fi
-if [ -z "$MESSAGE" ]; then
-  MESSAGE=$(echo "$INPUT" | grep -oE '"message":"[^"]*"' | sed 's/"message":"//;s/"//')
+if [ -z "${MESSAGE:-}" ]; then
+  # `[[:space:]]*` around the colon, like every other hook's fallback. This one
+  # required `"message":"` with no space, so a pretty-printed or space-separated
+  # payload fell through to the generic text below and the real notification was
+  # lost. Nothing reported that -- the hook still fired, just saying nothing.
+  MESSAGE=$(echo "$INPUT" | grep -oE '"message"[[:space:]]*:[[:space:]]*"[^"]*"' \
+            | head -1 | sed 's/"message"[[:space:]]*:[[:space:]]*"//;s/"$//')
 fi
 if [ -z "$MESSAGE" ]; then
   MESSAGE="Claude Code needs your attention"
 fi
 
-# Sanitize message for PowerShell string embedding (escape single quotes)
-MESSAGE_SAFE=$(echo "$MESSAGE" | sed "s/'/''/g" | head -c 200)
+# TRUNCATE FIRST, then escape. Escaping doubles each `'` into `''`, so cutting
+# at a fixed byte count afterwards can land between the two halves of a pair and
+# hand PowerShell an unbalanced quote. The command then fails to parse, and
+# because it is backgrounded with stderr discarded the only symptom is a
+# notification that never appears.
+MESSAGE_SAFE=$(printf '%s' "$MESSAGE" | head -c 200 | sed "s/'/''/g")
 
 # Show Windows balloon tip notification (works on all Windows 10/11 without extra modules)
 powershell.exe -NonInteractive -WindowStyle Hidden -Command "