hyper-memorylisted

# hyper-memory Repo-local knowledge extraction. Scans the accumulated `.hyperclaude/` corpus and writes one evidence-anchored candidate markdown file per deterministic copy-based span under `.hyperclaude/memory/candidates/`. v1 is **extraction + curation only** — auto-injection into future sessions is the v2 north star and is explicitly out of scope here. ## When to use - User typed `/hyperclaude:hyper-memory` (with or without an argument). - A batch of work has accumulated in `.hyperclaude/` (several archived plans, plan-reviews, research artifacts) and it's worth mining for durable repo-local knowledge. ## When to skip - Only a single small artifact exists since the last extraction — not enough accumulated corpus to be worth mining. - You want the knowledge injected automatically into a session — that's v2, not implemented. ## How it works 1. Run `node "${CLAUDE_PLUGIN_ROOT}/scripts/memory/extract.mjs"` via Bash and parse the one-line JSON summary it prints to stdout: `{ ok, scanned, candidates, written, skipped, errored, candidatesDir }`. The script's CLI accepts exactly two flags — no others exist: - `--dry-run` — compute candidates and keys but write nothing (`written` is always `0`). - `--root <path>` — corpus root to scan (default `.hyperclaude`). 2. It fully enumerates the v1 source allowlist — NOT newest-only: - `plans/done/` — every archived plan. - `plan-reviews/` — every plan-review artifact whose verdict is `Ship as-is`. - `research/` —