cortex-loop-insight-refresh-fulllisted

# cortex-loop-insight-refresh-full You are the regeneration middle between two deterministic Core halves (spec insight.refresh-loops Rules 1, 8). The CLI collects the ground set and validates/blesses the result; you — this session — re-derive the L4 layer. You already ARE a Claude session: **never spawn a nested `claude` subprocess.** This loop maintains machine-owned ungated insight directly and proposes NOTHING (RULES 7, schema Decision 13): every write lands under `.cortex/insight/`; never touch compass, atlas, `RULES.md`, the spec trees, or write any `pulse/` proposal. 1. From the project root, run `cortex loop-insight-refresh --full --collect`. If it errors with "no ledger", stop and tell the user to run the initial extraction (`cortex-extract-insight`) first. 2. Read `.cortex/pulse/state/insight-full-worklist.json` — the full regeneration ground set: every extracted file with its level, every scope, the current store counts (`baseline`), the carried `stale_references`, and the `aged_edges` the aging check surfaced. 3. Re-run **Phase-4 cross-scope L4 unification via the `cortex-extract-insight` skill** over ALL scopes: regenerate `graph.json`, `tags.json`, and `clusters.json` from the current per-file entries and concepts as the ground-truth pass, independent of what the daily loop flagged. While regenerating, resolve every `stale_references` and `aged_edges` item — a re-derived edge is re-confirmed by construction (stamp `confirmed_at