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-assets.sh

@@ -1,10 +1,48 @@
 #!/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: Validates asset files after Write/Edit
 # Checks naming conventions for files in assets/ directory
 #
 # Exit behavior:
-#   exit 0 = success or advisory warnings only (non-blocking)
-#   exit 1 = blocking error (build-breaking issues: invalid JSON, missing required fields)
+#   exit 0 = success or advisory warnings only
+#   exit 2 = build-breaking issue (invalid JSON, missing required fields)
+#
+# A PostToolUse hook CANNOT block -- the write has already happened by the time
+# this runs (see .claude/docs/hooks-reference/hook-input-schemas.md). The only
+# question is who hears about it, and that is what the exit code selects:
+#   exit 1 -> stderr goes to the USER only. Claude never sees it, so a JSON file
+#             it just corrupted looks like it wrote cleanly and it moves on.
+#   exit 2 -> stderr is fed back to CLAUDE as actionable feedback, so it can fix
+#             the file it just wrote.
+# Exiting 1 while printing "ERRORS (Blocking) ... fix before proceeding" would be
+# a promise the hook cannot keep, delivered to the one party who cannot act on it.
 #
 # Input schema (PostToolUse for Write/Edit):
 # { "tool_name": "Write", "tool_input": { "file_path": "assets/data/foo.json", "content": "..." } }
@@ -15,11 +53,16 @@ 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, order significant -- see the long note in validate-skill-change.sh.
+# Short version: hook input is JSON, so a Windows path arrives as `\\`. Without
+# jq the fallback cannot unescape it, and a single-rule sed turns each escaped
+# pair into two slashes, so `assets/` never matches and this hook silently
+# validates nothing on Windows.
+FILE_PATH=$(printf '%s' "$FILE_PATH" | sed 's|\\\\|/|g; s|\\|/|g')
 
 # Only check files in assets/
 if ! echo "$FILE_PATH" | grep -qE '(^|/)assets/'; then
@@ -54,6 +97,13 @@ if echo "$FILE_PATH" | grep -qE '(^|/)assets/data/.*\.json$'; then
             if ! "$PYTHON_CMD" -m json.tool "$FILE_PATH" > /dev/null 2>&1; then
                 ERRORS="$ERRORS\n  FORMAT: $FILE_PATH is not valid JSON — fix syntax errors before continuing"
             fi
+        else
+            # Say so rather than skipping in silence. This is the only BLOCKING
+            # check in this hook, so without an interpreter the hook exits 0 on
+            # a file it never opened -- indistinguishable from valid JSON. The
+            # sibling validate-commit.sh already warns in exactly this case;
+            # this half was the one that did not.
+            echo "WARNING: Cannot validate JSON (python not found) — $FILE_PATH unchecked" >&2
         fi
     fi
 fi
@@ -63,10 +113,11 @@ if [ -n "$WARNINGS" ]; then
     echo -e "=== Asset Validation: Warnings ===$WARNINGS\n==================================\n(Warnings are advisory. Fix before final commit.)" >&2
 fi
 
-# Report errors and block if any build-breaking issues found
+# Report build-breaking issues. exit 2 routes this to Claude, not just the user,
+# so the file that was already written can actually be corrected.
 if [ -n "$ERRORS" ]; then
-    echo -e "=== Asset Validation: ERRORS (Blocking) ===$ERRORS\n===========================================\nFix these errors before proceeding." >&2
-    exit 1
+    echo -e "=== Asset Validation: ERRORS ===$ERRORS\n================================\nThe file was written but is broken. Fix it now, before continuing." >&2
+    exit 2
 fi
 
 exit 0