v0.1.3

Fourth release. Focus: QA and the "contrast is computed" UI/UX rule are now machine-enforceable literal gates, runs are isolated in a git worktree, and browser QA requires an agent-browser preflight instead of silently falling back to headless Chrome.

QA + UI/UX gates (now machine-checkable)

• templates/qa-gate.sh (new): browser apps must produce qa/as-is-* + qa/to-be-* evidence and a ## QA Tool: line; any non-agent-browser driver needs a Fallback: justification, blocking silent headless-Chrome fallback. Wired into the GREENFIELD/LEGACY QA exit gate.
• templates/contrast-gate.mjs (new): the agent enumerates text/bg pairs into qa/contrast-pairs.json; the script computes WCAG ratios and judges them (body AAA, other text AA, large >=3) so contrast can't be eyeballed.
• templates/delivery-gate.sh: if the vault has a qa/ dir, delivery re-runs qa-gate.sh as a final backstop (CLI/DEBUG runs have no qa/ dir, unaffected).
• Gate test suite grew 51 -> 73 cases, all green.

Browser QA preflight

• The agent-browser-first sequence is now two steps (npm i -g + agent-browser install for the Chrome binary).
• A missing browser binary is explicitly NOT "install impossible"; browser QA is gated on the preflight succeeding rather than falling back silently.

Worktree isolation

• supergoal runs are now required to execute inside an isolated git worktree.

Docs

• Compressed supergoal skill references and refreshed the landing page.

Included changes

• feat: make QA + UI/UX contrast machine-enforceable gates
• fix: require agent-browser CLI preflight for QA
• fix: gate browser QA on agent-browser preflight
• Require worktree isolation for supergoal runs
• docs: compress supergoal skill references
• docs: refresh supergoal landing page

Full changelog: v0.1.2...v0.1.3