whodecided: Agent for Claude Code

You review the current change to whodecided (see AGENTS.md). Start by reading the diff (git diff and git diff --staged); if nothing is staged/modified, review against HEAD. Report findings ranked most-severe first, with file:line and a concrete failure scenario. Only flag things you're confident are real. Do not modify files.

1. Invariants (must hold)

• Single write path. Every ledger mutation goes through applyOps (src/patch/apply.ts). The only other writer is the distill append in commands/distill.ts. Flag any other write to .wdd/ledger.jsonl.
• Precedent is human-ruled only. recall / the memory digest never surface unratified (pending) decisions. Flag any path that leaks pending entries.
• Never auto-commit by default. Commits happen only when config.commit === "on". Flag any commit not gated on it.
• Hooks never disturb the session. hook trace / hook autodistill swallow all errors and exit 0.
• Latest ruling wins. verdictOf / isPinned / noteOf scan ratify lines from the end.
• One runtime dependency (yaml). Flag any new import that adds a dependency.
• html.ts template escaping. Inside the emitted <script>, regexes/newlines must be double-escaped (\\n, /[/]/, \\"); a single backslash silently breaks the page.

2. Test coverage

Run npm test and read it. For every changed behavior (not pure display strings), check there's a *.test.ts covering it — schema validation, applyOps (idempotency / overrule / unknown target), gateStatus, recallHits (pending excluded), the extract heuristics, the parser. If changed logic has no test, say exactly which behavior is uncovered and what the test should assert. Don't demand tests for trivial rendering strings.

3. What needs a human in the loop (call this out explicitly)

Unit tests can't cover these; if the diff touches any, list them as a "Verify by hand before merge" checklist so the human knows what to click/run:

• HTML workbench (render/html.ts): drawer open/close, Approve/Reject → in-page banner, the "save as a rule" switch + confirm modal, light/dark theme, timeline. Must be opened in a real browser.
• Live server flow (commands/review.ts serve path): POST /apply actually lands in the ledger and the page reflects it.
• Distiller output (distill/*): claude -p is non-deterministic; you can't assert exact decisions - a human judges whether the distilled what/by/aware are right.
• Interactive terminal ratify (--term readline loop).
• Real transcript parsing: behavior against actual ~/.claude/projects/*.jsonl (format can drift) vs. synthetic fixtures.
• Git side effects: commit gating / gitignored .wdd beyond the temp-repo unit test.