v3.0.2

Summary

Website release. The site is rebuilt on the developer-vertical anatomy with a
fluid token system, a new cinematic showreel replaces the old terminal
recording, and the qa-launch release gate becomes executable code that runs in
CI.

No engine behaviour, public API, CLI surface or MCP tool name changes.

Full Changelog: v3.0.1...v3.0.2

The site

• Copy — the AIDA spine across the page, with PAS driving the problem
  block. Written for a developer deciding whether to install something.
• Layout — the developer anatomy: hero → demo → architecture → code grid
  → proof → quickstart → licence.
• Tokens — a token-first stylesheet with fluid clamp() spacing and type
  ramps, logical properties throughout, and no fixed values in components.
• Graphics — a twelve-icon line set on a 24px grid, plus three inline-SVG
  figures: a recall latency chart, the memory lifecycle state machine, and the
  system topology with a "your machine only" band around the engine and the
  store. Every figure is bound to claims.json, so no figure can drift from
  the code.

The showreel

An original twelve-second film, "The Memory Lattice": the agent forgets →
the note is checked against the code it cites → verified, versioned, local →
the wordmark and the one command. A constellation of nodes whose focus thread
draws from the note to the code and snaps green when the check passes.

Every visual is a pure function of t, with a seeded PRNG for the dust field,
so the render is reproducible. The pipeline is Playwright + ffmpeg — the
browser was already a devDependency, so there is no extra download, and the
old HyperFrames composition (which needed a 150MB browser to flatten a vector)
is gone.

The copy rule

The project now says "the majority of coding agents" rather than a number.
A number ages badly and invites a precision the registry cannot promise; the
precise count stays in claims.json, where it is a fact about the code
rather than a promise about the market. A test enforces it.

The gate

apps/website/scripts/qa-gate.ts runs the qa-launch gate checklist as
code — critical paths, the keyboard-only path, 200% zoom reflow, the
no-JavaScript first frame, animation performance, the header/footer chrome, a
placeholder/debug sweep, the payload budget and a second rendering engine. It
exits non-zero on any blocking failure, so CI runs it.

17/17, SHIP.

Defects the gate found (all fixed)

Severity	Finding
P0	With JavaScript disabled, all 43 .reveal elements stayed at opacity: 0 — the page below the hero rendered blank.
P1	The mobile menu sheet overflowed the viewport (x = -73).
P1	The header rendered as raw inline text. A missing CSS rule does not throw — it is invisible to axe and to an overflow check, so the site passed every automated gate while looking broken.
P1	A <p> inside a <dl>'s wrapper div — an axe-core definition-list violation.
P1	The copy button's fallback hint said "Press ⌘C" on every platform.
P2	Two animated elements combined filter: blur() with a transform animation, forcing a per-frame re-rasterisation of the blur.

Verification

• bun test — 1354 pass, 0 fail, 6172 assertions across 206 files
• bunx tsc --noEmit — clean
• bun run site:qa — 17/17, SHIP
• axe-core — 0 critical/serious on 4 pages; 26/26 contrast pairs at WCAG 2.2 AA
• Firefox 155 — renders without overflow