prune

Govern eval and evolve work inside the prune repo. Use when a no-context agent needs to understand eval/evolve entrypoints, inspect local report artifacts, judge whether a manual eval or evolve run is warranted, review uncommitted working-tree changes as possible evolve output, and promote durable workflow conclusions into tracked docs, rules, and skills without committing raw artifacts.

Use for repository-understanding work when inspection should go through prune instead of raw grep/cat/find. Covers when to survey, how to search multiple likely paths, how to choose read --start vs --around, how to inspect diffs, and how to stop once evidence is sufficient.