DonchitosandClaude Opus 5
d05699707f
`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
2.8 KiB
Active Session State — [project or branch]
` is free-form narrative for humans and for a returning agent that wants detail. No hook ever injects it, so
it may grow — but see Rotation below.
Why the split exists: before it, active.md was one append-only file doing
both jobs. It reached 712 lines / 44 KB, and each consumer invented its own
slice of it — the status line parsed for a STATUS block nothing wrote,
pre-compact injected head -100 (12.7 KB), and session-start previewed
tail -20, the opposite end. They disagreed because there was no contract to
agree on. Now every consumer reads the named region.
ROTATION. When the narrative below grows past ~200 lines, move it to
production/session-logs/ and start it fresh:
bash .claude/scripts/rotate-session-state.sh
Nothing is lost — and the commit history already records most of what the
narrative repeats.
-->
Epic: Feature: Task:
Updated: [YYYY-MM-DD]
Branch: [branch]
Current task: [one line — what is actively being worked on]
Next step: [one line — the very next action, concrete enough to resume cold]
Blocked on: [one line, or nothing]
Files in progress: [paths, comma-separated, or none]
Open questions: [one line each, or none]
Notes
[Free-form. Decisions and their rationale, what was tried and rejected, context that would be expensive to reconstruct. Not machine-read — write for the person or agent picking this up cold.]