cortex-extract-insightlisted

# cortex-extract-insight ## When to use Use when the user says "extract insight", "run the extraction", "build the insight layer", "map this codebase", "run the initial extraction", "Cortex doesn't understand this codebase yet", or "refresh insight for <file/scope/concept>"; when a scheduled task invokes the extraction directly; or when an insight refresh loop hands this skill a dirty-file worklist to re-extract — `cortex-loop-insight-refresh-daily` (daily bundle) or `cortex-loop-insight-refresh-full` (weekly-quality bundle). Builds the per-file, per-concept understanding of a codebase stored under `.cortex/insight/`, in four phases: a deterministic L1 structural pass (Core), extraction planning with a scope registry, parallel per-scope L2/L3 execution, and cross-scope L4 unification. There is **no `cortex extract-insight` CLI command** — this skill IS the extraction. ## What you do You produce the `.cortex/insight/` layer — an inferred, persistent, queryable understanding of the codebase (design §5.1) — as **a plan, not a pipeline** (design §5.3): you read the deterministic L1 output and *decide* how to analyze the rest, in four phases. Everything you write MUST conform to `cortex-schema.md` §4.10 (the storage contract) — field names, enums, and id grammars come from there and from `src/insight/storage.ts`/`entry.ts`; never invent fields. Two non-negotiables up front: - **No CLI wrapper (RULES 3, design §5.3).** There is no `cortex extract-insight` command and you m