v0.2.1 — Zinc design polish (macOS GUI still buggy)

Apply the Claude Design handoff bundle's Zinc visual direction across all seven wizard screens. Engine wiring unchanged from v0.2.0; this is purely visual polish on top of the existing functional GUI.

⚠️ The macOS GUI is still not stable — more bug-fixing required before it's safe for anything beyond exploration. Use the shell wizard (`bin/f13-config`) for any real work. See the Known issues section below.

What's polished

Foundation (`9c0993c`)

• Zinc design tokens: `--f13-border-strong`, `--f13-accent`, `--f13-radius-{sm,,lg}` scale, `--f13-font` and `--f13-font-mono`.
• Six animation keyframes: `f13-fadeUp`, `f13-spin`, `f13-pulse`, `f13-scanLine`, `f13-flowDash`, `f13-shimmer`.
• New `F13Logo.svelte` (clean 64×22 pixel mark, scalable).
• Layout primitives: `StepHeader`, `Footer`, `PageBody`, `PageTitle` — used by every step screen.

Welcome + Preflight (`f235bc4`)

• Welcome: pixel logo, green-dot preset badge, mono credit footer, 500ms fadeUp entry.
• Preflight: scan progress bar with shimmer overlay, mono check rows, three-state title pattern (Scanning / Some requirements missing / Environment ready).

Inference + Ollama (`cd6a7ef`)

• Tile component now fills with text-color when selected (high-contrast inversion).
• Recommended badge floats off the corner.
• Ollama picker gets the colored-left-border GPU warning, custom radio dots, cloud pill badges with cloud icon.

Ports + Run pipeline (`2558a1c`)

• Ports: bordered field cards, mono inputs with `--border-strong` outline, inline status icons, "Launch" CTA.
• Run: slim header with uppercase "LAUNCHING F13" kicker, six-node SVG pipeline graph with flowing dashes between stages and a pulsing aura on the active node, terminal-style live log (200px tall, dark mono) with auto-scroll.

Status (`2ca974b`)

• Dark gradient hero card with concentric circle decoration.
• Pulsing green status badge (with glow), big 24px title, mono URL line, white-on-black "Open F13 in browser" CTA.
• 2×2 service grid with green dots, mono service names, image tags, ports.
• "ACTIONS" panel with kicker.

Disclaimer wording (`5b43566`)

• "F13 can make mistakes" → "F13 uses AI models and those can make mistakes." Specific about the actual user-facing risk.

Known issues (not fixed in v0.2.1)

These were logged during v0.2.0 + v0.2.1 testing and need fixing before the macOS GUI is stable:

1. `f13-reset` is path-blind — only wipes `configurator_v1/generated/`, not the GUI's `gui/src-tauri/target/debug/generated/`. So the GUI's stale state survives reset attempts from the shell wizard.
2. GUI's run page defaults `generatedDir = "./generated"` (relative) — resolves against the Tauri dev process's CWD, so the GUI's stack ends up in `target/debug/generated/` rather than under `configurator_v1/`. Confusing and not where the shell wizard's `f13-stop`/`f13-reset` looks.
3. Wizard's "keep existing state" path is incomplete for the GUI — when `.state` exists, the wizard skips secrets/render/build/pull/health and only emits `step name=start`. The GUI's six-stage pipeline graph stays pending forever, looking stuck even though docker compose is actually running underneath.
4. No abort UX — the Cancel button only sets a JS-side flag; the underlying bash subprocess keeps running. Stopping mid-pipeline can leave half-built containers.
5. Sporadic "pull access denied" errors for the locally-built `f13-frontend:configurator-v1` image when compose's first pass races with image presence checks. Direct `docker compose up -d` works reliably; only seen via the GUI.

What's stable

The shell wizard from v0.1.0 is still the trustable surface — `bin/f13-config` for first-time deployment, `bin/f13-stop` / `bin/f13-reset` / `bin/f13-rebuild-frontend` for ops. The Phase 7 / 7.5 desktop GUI works end-to-end on macOS but expect the rough edges above.

What's coming

Next sprint: knock out the five known issues above, then v0.2.2 closes out Phase 7 with a usable GUI. Phase 8 (Linux runtime, signed bundles) follows.