compaction-checklisted

# Compaction check Global. Runs in any project. The **method** here is portable; a project may add its own audit script, and if it has one, that script runs first and this file is the part it cannot do. Known project-specific audits, checked by existence and never assumed: - `DEV/Learning` and `DEV/Learning/vcc-2026`: `DEV/Learning/vcc-2026/.venv/Scripts/python.exe DEV/Learning/vcc-2026/research/_compaction_audit.py` (ten checks, fails closed; that project's own `.claude/skills/compaction-check/SKILL.md` documents them). Do not run it outside those projects: its checks name HANDOFF, MISSION, submission rows and science messages, which do not exist elsewhere, and it would ERROR at step one. ## What he is actually asking Two things, and neither is "have you been diligent": 1. Would compacting **right now lose anything**? 2. Is anything **he could act on** sitting unsaid? Answer both, with numbers, in plain English. He keeps twelve phrasings of this in `~/PC/Downloads/compound, compact, handoff.txt`; they reduce to: everything compounded, nothing stale, nothing outstanding. He asks more than once in an evening because the answer must be **re-derived each time**. Re-deriving it is the whole job. ## Never answer from recall Measured repeatedly: the honest answer was reached by checking and would have been wrong from memory. On 2026-09-19, three consecutive "is it ready to close" asks each turned up something real, and the third one corrected the second. The check i