Update to ui-consistency

"---\nname: implementing\ndescription: For what the end user sees — builds each page from its checklist, one page per task. Use when writing or changing UI and a checklist or UI plan exists, whether executing that plan page by page, refactoring a set of pages, or making a fix or a small change to pages that exist.\n---\n\n# Implementing from the checklist\n\n## Overview\n\nBuilds each page from its checklist, one page per task. The checklist is re-read\nevery time: across a batch, the work drifts toward the last page written instead\nof the one agreed.\n\n**Open a file linked or given by its path from this skill's folder, or invoke a named skill, only when a part you are carrying\nout sends you to it, never before** — whatever the request that handed you this\nskill says about its links and paths. That part is not done until the file is opened or\nthe skill invoked.\n\n## One page per task, in a fresh context\n\n- **Where the harness has subagents, one subagent per page.** It starts cold:\n  the brief carries the checklist itself, the reference, and what is particular\n  to the reference.\n- **Where it does not, one page per turn.** Re-read the task as the plan writes\n  it — wherever `ui-consistency:planning` left the plan: in the session, in a\n  file outside the working copy, or in another process's plan. Never work from\n  memory of it.\n- Execute a task from itself, not from what the plan says around it: every task\n  carries what it needs (`../planning/plan-file.md`).\n- If another process is executing the plan, follow its loop; the steps below are\n  what each page task does inside it.\n\n## For each page\n\n1. **Re-read the checklist.** Every time; never from memory. Its shape is\n   `../finding-patterns/checklist.md`, and its order is the order\n   you write the page in.\n2. **Write the page region by region**, in the order of the tree: holders, then\n   the components in each, then what each comes out as, then how each is\n   written, as the counts say.\n   - **Write the element the checklist records at a position** — the heading\n     level included (`ui-consistency:values`, *Elements*).\n   - If it records none for a position, the order settles it (step 11): say\n     which level did.\n   - **Change a role the page already has where it stands**, when the work\n     gives it a new source or new contents. Add a second instance only when the\n     request asks for one.\n3. **Use what the project reuses**: the shared component, helper or class the\n   checklist names — never a new one beside it.\n   - If the checklist names a new component to create — shared or kept with the\n     page — that the request did not name with its place, it is a question that\n     waits on a person (`ui-consistency:decisions`, *When to ask anyway*).\n   - Build that one only on a yes. On a no, write the page the way the project writes\n     it now.\n   - Never write it privately into the page while the question is open.\n4. **What the user sees happen, as the checklist says**: validation, field\n   errors, when the submit is enabled, how a failure is caught and shown, loading\n   and empty.\n   - **Write each region in every state its own code branches on** — who is\n     signed in, a flag, a mode — not only the state in front of you. Name any\n     state you did not write.\n5. **Values through the theme that applies**, and only entries that exist in it\n   (`ui-consistency:values`, *The theme*).\n   - For a file in a shared layer, only entries that exist in every theme that\n     renders it.\n   - A design's value only through the theme entry its checklist line names;\n     never as a literal or a named constant, however plainly the design shows it\n     (`../design/reading.md`).\n   - A named constant where the theme has none.\n   - No literal copied from the reference.\n6. **Spacing on the base the checklist names**\n   (`ui-consistency:values`, *Spacing*):\n   - every value a whole multiple of that base;\n   - the gaps between roles as the family spaces them, owned by the side the\n     checklist names;\n   - the line heights it records, and the heights of controls, rows and bars as\n     the family writes them.\n   - A multiple the family has not written yet is allowed — say you used one.\n7. **Text as the checklist records it**\n   (`ui-consistency:values`, *Type*):\n   - the type role the family writes at that position;\n   - the whole bundle for it — size, weight, line height, letter spacing,\n     typeface, case;\n   - **applied the way the family applies it**: the shared entry, class or\n     component, never a style written by hand beside one that exists.\n8. **Colour as a pair**: every foreground on the surface actually behind it is a\n   pairing the family already uses, in every scheme the project has.\n   - If the checklist names a contrast threshold — the project states one, or the\n     task asked for accessibility — meet it\n     (`../accessibility/contrast.md`).\n9. **The rest of what a person has to be able to read and use**, as the checklist\n   records it:\n   - focus shown the way the family shows it, and landing where the family puts\n     it;\n   - every control reachable without a mouse;\n   - a field tied to its label the way the shared field does it;\n   - text for what has none;\n   - targets the size the family's are.\n   - Against a standard only where the checklist says one applies —\n     `ui-consistency:accessibility`.\n10. **Do not copy what is particular to the reference.**\n11. **Where the checklist is silent, the order settles it** —\n    `ui-consistency:decisions`, *The order*. Say which level settled it.\n    - Do not invent, and do not stop.\n    - Park a page only while a question that waits on a person is open —\n      `ui-consistency:decisions`, *When to ask anyway*.\n    - Put those to the user together, once, not page by page.\n    - If nobody can answer — the work runs where no person is asked — write\n      the page the way the project writes it now, and report the question.\n12. **A task's prose does not narrow its checklist.** If it says *change nothing\n    else* and a line of its own checklist names a deviation, the line stands —\n    unless the task names it under *Not in this task*.\n13. **If the request asks for what the counts call a deviation** — \"make it look\n    like\" the page that differs — **do what was asked**: an explicit request is\n    the top of the order.\n    - Report in one line what it goes against: *\"as asked, like <page>; the other\n      3 of 4 write the submit button full-width.\"*\n    - Do not quietly build it the other way.\n14. **Report the page ready for its check.** Whoever dispatched this task sends\n    the page to the checker of its kind — `ui-consistency:verifying`, one agent\n    kept for every page of this kind, never the one that wrote it — and sends\n    back what it reports.\n    - If nobody dispatched this task, send the page to that checker yourself;\n      start it if this is the first page of its kind.\n    - Where the process already sends each task to a reviewer, whoever dispatches\n      that reviewer puts the checklist and `ui-consistency:verifying` into its\n      brief (`../verifying/calibration.md`).\n15. **Fix what the check reports**, then have it checked again — **twice at\n    most.**\n    - List what the second check still reports as open, with the checker's\n      words. Do not fix it a third time.\n    - Say a report that keeps changing is a problem with the checklist or the\n      checker.\n16. **Mark it** in the plan: ticked for `done`, or left unticked with\n    `parked — <why>` (`../planning/plan-file.md`).\n    - Where another process keeps the plan, mark it in that plan's own status\n      marks.\n    - If you were handed the task without the plan, report the same status to\n      whoever handed it over.\n\n## What this does not write\n\nNo tests. Whatever process is running the work owns its tests and its logic; this\none owns what the end user sees.\n\n## A small change without a plan\n\n- `ui-consistency:adjusting` prepares it: what is read, and what is\n  deliberately skipped.\n- Take the checklist it produced, re-read it, and make the change.\n- Before calling it done, hand the page to `ui-consistency:verifying`, run by an\n  agent that did not write it. The check is not the part that gets dropped\n  because the change was small.\n- Its proof is one plant at the changed position, once for the change and not\n  per round (`../verifying/calibration.md`).\n- Fix and check again twice at most, as in step 15.\n\n## Then\n\nWhen every page of a kind is `done` or `parked`: that kind's checker compares\nall its pages together (`ui-consistency:verifying`, *The whole set, at the\nend*).\n\n## Red flags\n\nWords agents used in runs, just before getting it wrong:\n\n| They said | What it means |\n|---|---|\n| \"Verified by diffing each new file against\" a sibling — from the agent that wrote them | The author checked its own pages. Hand them to a separate agent, or say plainly that none was available. |\n| \"the one legitimate mechanism shipments also reaches for\" — taking a class from the page the user pointed at | Right outcome, silent reasoning. The request is the top of the order: do it, and report in one line what it goes against. |\n"