rite-polishlisted

# /rite-polish: finish before review Polish code for every feature. When the feature touches UI, normalize and polish the UI as well. Complete this self-review before `/rite-review`. The code and UI phases live in `reference/code.md` and `reference/ui.md`; read only the phase in scope. ## Operating rules - **Functionality complete first.** Polish runs after `/rite-prove` (full feature proven). - Follow the shared [`candidate-integrity.md`](../devrites-lib/reference/candidate-integrity.md). Polish owns every candidate-affecting correction and durable rollup before Review. - Feature scope only. - For UI, **normalize before polishing**. Do not add decoration on top of drift. - **Root selects; wright edits.** The controlling chat assesses and reconciles, but every accepted source/test correction is dispatched to the sole writer, `devrites-slice-wright`, through [`agents.md`](../devrites-lib/reference/standards/agents.md). Never edit source inline or run two correction writers concurrently. ## Orchestration 0. **Read** `.claude/skills/devrites-lib/reference/standards/core.md` first (the always-on operating rules). The per-phase rule files (`coding-style.md`, `error-handling.md`, …) load on demand from `reference/code.md` / `reference/ui.md` when their phase runs; for UI scope also read `.claude/skills/devrites-lib/reference/standards/browser-proof-checklist.md`. Then read the explicit or active workspace's `state.md` directly. 1. **Read** `state.md`,