!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation

Automation mode: Resolve modes.automation (project.local.yaml → project.yaml → default collaborative). Every AskUserQuestion call and every file write follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

Patch Notes

Provenance check, before reading any history

Confirm the history you are about to read belongs to THIS game. Run this before Phase 2 and stop if it fails.

1. Sample the recent log: git log --oneline -20. If it is empty or git is unavailable, skip this check, there is nothing to classify, and Phase 2's no-changelog-data branch is the right stop.
2. Classify every commit in the range, one at a time, into exactly one of:
   • Game, changes the game the player plays: mechanics, content, balance, art, audio, UI, a bug in any of those.
   • Framework / maintenance, changes CCGS itself or the project's tooling: subjects naming skills, hooks, agents, the test plan, CI, the framework's own docs. Excluded from player-facing notes, but not a reason to stop.
   • Unclear, treat as framework. A commit you cannot confidently place is not one to write player copy from.
3. Then decide from the counts:
   • At least one Game commit → proceed, using only those. Say how many of how many you used, so the reader can see the filter ran.
   • Zero Game commits → stop, using the message below, and give the count (0 of how many) so the reader can see the filter ran.