refreshlisted

# Refresh rules for a framework version Clawness rules can carry a version stamp — `applies_to`, `verified`, `sources` — recording the range they were established against. When a project runs past that range, a SessionStart note says so once and deliberately does nothing else. This skill is the **remedy**. The note is only the diagnosis: it fires before you have said what you came for, so it cannot propose a session's worth of destructive work. You invoking this skill *is* the consent it couldn't ask for. **This is the only path permitted to author rule files.** Nothing automatic may invoke it — not the note, not a hook, not your own initiative mid-task. An earlier version of this feature let the automatic path write rules and it produced heaps of them, consuming a session opened for something else. **Say this before starting.** It takes a while, it writes files into the project, and the rules it writes will govern every future prompt in this repo. Get an explicit go-ahead, and tell them nothing is written until they approve the list. ## Argument `/clawness:refresh <domain>` — one domain (`nextjs`, `react`, `python`, `fastapi`, …). With no argument, use the detected stack, and if that spans several domains ask which one. **One domain per run.** Reviewing several at once is how a careful pass becomes a bulk stamp, which is the failure this whole feature exists to prevent. ## Steps ### 1. Establish what is actually installed The **lockfile is authoritative; the manifes