Skip to content

claude-memory: /init-then-prune eval fixture — static bloated CLAUDE.md graded against expected audit findings #2989

Description

@kyle-sexton

Context

Implementation deliverable of course lane 9 (#2911; decision locked 2026-08-17, user-confirmed). The course's "Trying Out Pruning" lesson suggests generating a bloated memory file with /init and grading the pruning pass; the lane adopted it as an eval fixture against claude-memory:audit's existing eval suite (plugins/claude-memory/skills/audit/evals/evals.json, prompt/files/expectations shape). A static fixture was chosen over live /init generation for determinism. Decision rows: docs/upstream/aihero-steering-lanes.md (lane 9).

Proposed work

Acceptance criteria

  • Static fixture committed and referenced from evals.json
  • Expected-findings expectations cover C1/C2/C5 at minimum
  • Eval suite passes with the new case included
  • Version bump + CHANGELOG entry land for claude-memory

References

Metadata

Field Value
Category unspecified
Area claude-memory, evals
Ecosystem unspecified

Metadata

Metadata

Assignees

Labels

priority: mediumReal value, no hard deadline; normal backlog flow.

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions