v0.9.0 — break + purpose-driven rethink

What's new

Split the radical-redesign command into two complementary tools:

break (renamed from rethink)

The 'question the system' command. Metaphorically breaks the design system to escape its gravity, then reconciles via KEEP / UPDATE / NEW per token with blast-radius surfaced. Use when the brand itself is part of what's wrong.

rethink (new, purpose-driven)

The default creative refine after a rebrand or migration. Treats brand tokens as read-only vocabulary and forces five purpose questions before any visual decision:

1. Where does this live (which screens, which step of which flow)?
2. What job is it doing (decision / action / feeling enabled at this moment)?
3. Who's reading it, in what posture?
4. What are the neighbors saying (relative volume)?
5. What would make this component unmistakably this, in this place, for this purpose?

Every visual decision must trace back to one of the answers. Token policy: KEEP-first, NEW only when the brand vocabulary genuinely lacks a word, never UPDATE (that's break or migration).

New rethink-scan.mjs outputs brandSurface (read-only), usageSites, flowNeighbors, and siblingTreatment with a same-treatment flatness signal.

When to use which

• brand is wrong → break
• brand is right, component is generic / doesn't earn its place in the flow → rethink
• whole system needs to move → migration

Other changes

• Cross-references updated in migration.md, design-system.md, rebrand.md
• Registered break across SKILL.md, command-metadata.json, pin.mjs, utils.js
• Command count 27 → 28
• 84/84 tests pass