- Add insta + tempfile to _assembler/Cargo.toml [dev-dependencies]. - Create tests/common/mod.rs with helpers: seed_tempdir (copies fixtures into an isolated AGENT_ROOT), run_assemble (invokes the built binary via std::process::Command), and assemble_one (end-to-end single-manifest helper). - Seed tests/fixtures/ with the 4 manifests covered by the golden snapshots (code-implementer, researcher, cost-guardian, patent-compliance) and the 7 blocks they reference (baseline, evidence-grading, memory-protocol, rule-pre-dev-gate, rule-test-first, rule-error-budget, rule-double-audit). Binary-only crate (no lib target), so integration tests invoke the assemble binary in-process instead of calling internal functions. This exercises the full main.rs I/O + validator + assembler pipeline end-to-end, which is exactly what the determinism claim covers. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1,012 B
1,012 B
MEMORY PROTOCOL
At start:
- Read
~/.claude/memory/MEMORY.md(or your index file) → find relevant project file - Read
memory/{project}.md→ constraints, stack, status, learnings - If ML / research work: also check your
wrong-paths.mdnotes (dead ends worth avoiding)
At end (if stage completed — feature/phase/milestone/audit/bug+fix/deploy/decision/blocker):
- Append to
memory/{project}.mdwith format:### Feature Name (YYYY-MM-DD) [E-grade] - Result: specific metrics (numbers, not "works well") - Decision: what was done - Benchmark: numbers vs baseline - Learnings: what was learned - Next: what's next - If dead end / wrong path → append to your
wrong-paths.md - If architectural decision → project's
DECISIONS.md - Session chatlog (if significant):
memory/chatlogs/{ml|projects}/YYYY-MM-DD-{topic}.md
Forbidden: transitioning without saving; writing "works" without metrics; leaving credentials only in conversation context.