v1.7.0 — om-ds-guardian absorption

Added

• DS Guardian (om-ds-guardian) — Design System enforcement skill absorbed from Open Mercato repo PR #1707. Five capabilities: ANALYZE (DS violation scan), PLAN (migration plan), MIGRATE (script-based + surgical + raw-HTML→DS-primitive recipes), REVIEW (compliance review with scoring), REPORT (health metrics with delta).
• Reference: references/component-guide.md — when to use which DS component, API quick reference, MUST rules per primitive (Input, Select, Switch, Radio, Textarea, Tooltip, etc.) — required reading for any skill that generates UI code.
• Reference: references/token-mapping.md — full color/typography mapping tables, raw-HTML→DS-primitive diff recipes
• Reference: references/page-templates.md — canonical DS-compliant List/Create/Detail page templates — required reading for om-module-scaffold and om-implement-spec.
• Scripts: ds-health-check.sh, ds-migrate-colors.sh, ds-migrate-typography.sh — bundled bash codemods (also live in OM repo at .ai/skills/ds-guardian/scripts/ since PR #1707)
• om-auto-review-pr step 6a: invokes DS Guardian REVIEW on UI-touching PRs (.tsx/.ts under packages//apps/ non-test paths). Severity maps to existing CRITICAL/MEDIUM/LOW pipeline. Skipped on non-UI PRs.

Changed

• Updated plugin tagline: 20 → 21 skills
• om-module-scaffold step 6 (Create Backend Pages): now requires consulting om-ds-guardian/references/page-templates.md, component-guide.md, and token-mapping.md before emitting any page. Hard-rules listed inline (no raw HTML controls, no hardcoded status colors, no arbitrary text sizes, etc.).
• om-implement-spec Pre-Flight: new step 4 — load DS references when the spec touches UI. UI rule in code-review enforcement table extended with DS primitives + tokens + typography scale requirements.
• om-backend-ui-design and om-code-review collaboration table cross-references om-ds-guardian for design-system-specific checks (build vs. enforce split).

Architectural decision

• DS Guardian does not write code. It shapes inputs (via reference docs that primary scaffolders consume) and polices outputs (via REVIEW at PR time). The original SCAFFOLD capability from PR #1707 was dropped during absorption — primary scaffolders (om-module-scaffold, om-implement-spec) own page creation and consume the DS templates as required input. Single source of truth for templates, single enforcement gate at PR time.