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/validate-skill-change.sh

@@ -1,4 +1,32 @@
 #!/bin/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
+
 # Claude Code PostToolUse hook: Advises running skill-test after skill file changes
 # Fires when any file inside .claude/skills/ is written or edited.
 #
@@ -14,11 +42,23 @@ INPUT=$(cat)
 if command -v jq >/dev/null 2>&1; then
     FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty')
 else
-    FILE_PATH=$(echo "$INPUT" | grep -oE '"file_path"[[:space:]]*:[[:space:]]*"[^"]*"' | sed 's/"file_path"[[:space:]]*:[[:space:]]*"//;s/"$//')
+    FILE_PATH=$(echo "$INPUT" | grep -oE '"file_path"[[:space:]]*:[[:space:]]*"[^"]*"' | head -1 | sed 's/"file_path"[[:space:]]*:[[:space:]]*"//;s/"$//')
 fi
 
-# Normalize path separators (Windows backslash to forward slash)
-FILE_PATH=$(echo "$FILE_PATH" | sed 's|\\|/|g')
+# Normalize path separators (Windows backslash to forward slash).
+#
+# TWO rules, and the order matters. The hook input is JSON, so a Windows path
+# arrives escaped: "C:\\Users\\x". jq unescapes it to a single backslash, but
+# the grep fallback CANNOT -- it hands back the raw two-character `\\`. A
+# single `s|\\|/|g` then turns each of those into its own slash, producing
+# `.claude//skills//help//SKILL.md`, which no path test below matches. The hook
+# went silent on every Windows edit whenever jq was absent -- and jq is absent
+# on a stock Windows Git Bash, which is this project's primary platform.
+#
+# Rule 1 collapses the escaped pair to one slash; rule 2 handles an already
+# unescaped separator (the jq path, or a POSIX caller). Running both is safe
+# for either input because rule 1 finds nothing to do on unescaped text.
+FILE_PATH=$(printf '%s' "$FILE_PATH" | sed 's|\\\\|/|g; s|\\|/|g')
 
 # Only act on files inside .claude/skills/
 if ! echo "$FILE_PATH" | grep -qE '(^|/)\.claude/skills/'; then