meta-refreshlisted

## What this maintains Reference skills are every `skills/*/SKILL.md` not prefixed `flow-`, `audit-`, `write-`, or `meta-`. Each carries a `## Version notes` section that this skill owns: ``` ## Version notes Checked: <YYYY-MM-DD> against <source: library id or URL> - <version> (<release date>): <what changed for the guidance in this skill> - <older version>: ... ``` Retention: at most 3 version entries, newest first. A pattern that changed moves into a `### Legacy (<version>)` block at the end of the reference file it came from, one short paragraph, at most 2 legacy blocks per file. Anything older is deleted with a one-line note "Older guidance removed <date>; see git history." Git holds the rest. ## Procedure 1. Scope. Get the scratch directory: `!`scratch-dir.sh``. The arguments are: $ARGUMENTS - One or more skill names: refresh those. - `--all`: every reference skill. - Blank: list every reference skill with its `Checked:` date (or "never"), oldest first, and ask which to refresh via AskUserQuestion (multi-select, at most 5 unless the user picks `--all`). 2. Read each selected skill's SKILL.md and every file under its `reference/`. Extract: the claimed current version (intro lines and Version notes), every version-specific claim ("since 3.4", "renamed in 16", "deprecated"), and the References URLs. 3. Research, never from memory. For each skill dispatch one researcher agent (Agent tool, subagent_type: researcher, same message for up to 3 at a time) with: t