baseline-gap-reviewlisted

# Baseline Gap Review Built after the second dated occurrence of this pain (`_Improvements/` piled up again, 41 new notes since the 2026-07-29 pass, with no review cadence), which is what `process-vs-work-doctrine` rule 1 requires before building anything. **Don't state the occurrence count here.** Earlier versions of this file hardcoded one and it was wrong within a month, because the file cannot know how many times it has since been run. Count the dated manifests instead — `ls $IMPROVEMENTS_ROOT/Done/*-baseline-consolidation-manifest.md` is the number of passes, and `$IMPROVEMENTS_ROOT/.flow-log` is the running record. Per rule 3 this **stays a single file** — no spec directory, no install script, no CONTEXT.md, no supporting scripts. It has now run several times without needing any of them, which is evidence the constraint is right rather than a countdown to relaxing it. Do not scaffold on your own initiative. ## Paths Resolve all three from the environment. Do **not** prompt for them, and do not write literal machine paths back into this file: - `_Improvements/` root: `$IMPROVEMENTS_ROOT` (the same variable `improvement-extraction` writes to — they must agree) - work toolkit repo: `$WORK_TOOLKIT_ROOT` - personal toolkit repo (this repo): `$AI_TOOLKIT_ROOT`, or the repo root containing this skill If a variable is unset, ask for that one path once and use it for the run only. > Superseded 2026-09-09: these were previously three hardcoded absolute paths, > kept t