bootstraplisted

# Bootstrap rules for an uncovered stack Clawness ships corpus for ~29 domains. Open a session in a stack it has no rules for and, beyond the always-on mandatory block, it adds little. 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 work. You invoking this skill *is* the consent it couldn't ask for. **This is a rule-authoring path, so the same discipline as `/clawness:refresh` applies.** Nothing automatic may invoke it — not the note, not a hook, not your own initiative mid-task. An earlier version of a related 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:bootstrap [stack]` — the ecosystem to write rules for (`ruby`, `elixir`, `haskell`, …). With no argument, use the uncovered stack the note named; if the repo mixes several uncovered stacks, ask which one. **One stack per run** — a broad pass over several is how a careful review becomes a batch of slop. ## Steps ### 1. Establish what the project actually is Read enough of the codebase to know the stack, its versio