chore(agentic): require GLM 5.2 for major UI/UX work

[rickylabs]

Summary

Locks the owner-ratified 2026-07-12 policy that every major UI/UX work item is either led by the supported GLM 5.2 design lane or receives its mandatory adversarial design pass before merge. The machine policy derives the OpenRouter profile, model, and effort from the existing claude-design-glm-5-2 preset.

Scope

• Archetype / area: internal harness and agentic routing policy
• Evidence: dashboard-design slice 4b on design/dev-dashboard-revamp, .llm/runs/dashboard-design--orchestrator/analysis/glm-design-pass-agentic.md
• Related delivery: design: dev-dashboard revamp umbrella (analysis + Claude-Design prompts) #685 and fix(agentic): durable OpenRouter lane repair (launcher profile/exit bugs, GLM lane viability, preset canaries) #696

Slices

• S1 Add matching human and machine routes for GLM-led UI/UX work and the mandatory adversarial minimum — a8c0d0f0

Definition of Done

• Major UI/UX scope is explicit: design-system work, dashboard/console surfaces, and significant frontend UX.
• Lead and adversarial routes bind to claude-design-glm-5-2 / claude-openrouter at xhigh.
• The prior Opus design row explicitly excludes major UI/UX work.
• Routing tests and the volatile-value guard pass.

Validation

• Focused routing policy + volatile guard: 13 passed, 0 failed.
• Full agentic suite: 240 passed, 0 failed.
• Scoped runtime check: 67 files, 0 findings.
• Scoped runtime lint/format: 67 files, 0 findings.
• deno.lock unchanged.

Harness

• Run dir: N/A — small, owner-ratified policy-lock follow-up.
• Phase: review.

Drift / Debt

• None.