Ticket 04: design-guard stops judging what already has a judge

[Tradebaas]

What changed and why

The installed design method owns the making of a frontend, and design-guard was still carrying a
second rulebook for one: nine visual rules restating the craft floor that ticket 03 made the single
source. It now routes before it checks.

• A web, iOS, Android or adaptive interface goes back to the method that built it. What is left on
  that route is a re-check, never a second hunt: the direction contract kept, the FINISH line
  discharged, the finish verdict traveling with its open items under the reviewer's own word, the
  live-surface contract on a redesign, and DESIGN.md section 3 still mirroring the build.
• Everything the method does not carry stays here and is judged in full: generated documents,
  e-mails, exports, error strings, CLI and log output.
• The platforms it does not carry are named rather than left implied (Unity, Godot and other
  game engines, console UIs, embedded and kiosk displays, TV, print), so nobody assumes coverage
  that does not exist. On one of those, the platform's own published guidelines are the missing
  rulebook and the verdict says so.

Two floors sit above every route, because nothing else states them: the accessibility floor with
its COMPLIANCE.md link (carried over unchanged, extended with reading order for a document and
never-color-alone for any medium), and reduced motion, which decision 0020 moved to DESIGN.md
principle 7. Both are exercised, not read out of the source.

verify's pointer follows the same split, and the AGENTS.md row says what the skill is now for.

Verified by

• The non-interface half, proven on real output rather than asserted. Ran section 3 over this
  repo's own gate output. mkdir docs/emptyprobe produced FAIL [empty-dirs] docs/emptyprobe/ is empty: delete it, or add a .gitkeep if it must exist. - what happened plus what to do, a named
  gate rather than a bare code. Piped to a file: zero escape sequences, so meaning never rides on
  color alone. One finding left unbuilt: 1 finding(s). carries a parenthetical plural in an
  otherwise properly pluralized register. Not a defect, so the intake freeze holds it out.
• Gates green on this head. node checks/check.mjs OK with the enforcement line reporting all
  four signals; node checks/links.mjs clean; node checks/progress.mjs runs.
• All ten suites green: 70 runner and document, 35 code, 24 config, 48 trace, 5 stack, plus
  progress 25, links 19, cockpit-path 11, cockpit 21, drill 11.
• Review found two copies of somebody else's knowledge in the first draft (DESIGN.md principles
  9 and 10, and VOICE.md's banned-phrasing examples, restated inside the checklist). Both are now
  pointers carrying only the medium-specific angle, which is the rule this ticket exists to apply.
• Not verified here: the frontend re-check route against a real built surface. The one built
  through this method so far was a throwaway scratch project from ticket 02, already discarded;
  ticket 06's reconciliation and the spec's own verify pass are where that gets exercised.