rewritelisted

# rewrite — rebuild it from scratch Do the work **once more, from scratch**; **score** it; **fight** it against the previous version; the winner takes the throne; repeat until a challenger loses; finish with an **analysis and a table**. The goal is not "polish it a bit" — it is to **measure whether rewriting it a different way is actually better**. That is why copy-paste between rounds is banned and every verdict comes from a rubric frozen before the first round. Siblings, same tournament, different move: **refactor** improves the existing code in place with reviewable diffs; **reskin** redesigns an interface and judges the pixels; **audit** builds nothing and judges what is already there. If the honest answer here turns out to be *"the design is fine, it just needs sharpening"*, hand off to `refactor`. --- ## 0. Pick the target If the user passed an argument, that is the target (`/rewrite GameUI cast ring`). If not, ask **one question**: what should be remade. A target can be a file, a class, a function, a system, or a document. Once the target is clear, **write the spec** (3-8 bullets: what this code must do, which rules it must obey, what it must not break). The spec is **fixed for every round** — growing the target mid-run makes the comparison meaningless. ## 1. Setup (round 0) 1. **Champion = what exists now.** Take the target's current code as-is; that is "Round 0 / incumbent". If nothing exists yet, there is no Round 0 and the first version written becomes