Docs: knit the public explainer pages into one "How MateMate Works" site (hub + shared nav + fleet page)

[testtest126]

Goal: turn the standalone public explainer page(s) on GitHub Pages into one small, coherent "How MateMate Works" site, borrowing the information architecture of Google's "How Search Works" — question-based section headers, progressive disclosure (overview → deep dive), consistent modular cards, and a light shared top-nav across pages.

Current state (main @ cf20ef7, 2026-07-12)

• docs/architecture/index.html — live at testtest126.github.io/chess/architecture/ ("What is MateMate?"). Self-contained, theme-aware, interactive.
• docs/agent-interaction-guide.md — Markdown source describing how the concurrent Claude sessions coordinate. This is the content source for the "How it was built" page.
• No docs/index.html root hub exists (testtest126.github.io/chess/ has no landing page).
• The "How the Agents Talked" page at docs/the-fleet/index.html does not exist yet despite being referenced as prepared — it needs to be authored.

Scope

1. Author docs/the-fleet/index.html — a self-contained, theme-aware "How the Agents Talked" page (how MateMate was built) derived from docs/agent-interaction-guide.md, matching the architecture page's design system.
2. Add docs/index.html — a "How MateMate Works" hub with plain-language, question-based entry points: What is MateMate? → architecture, How was it built? → the-fleet.
3. Add a lightweight shared top-nav tying all three pages together with consistent card styling and overview-to-detail progressive disclosure.

Constraints

• Each page stays a single self-contained HTML file — no external fonts/scripts/assets (Pages renders as-is).
• Preserve the existing theme-aware (light/dark + data-theme) design and reduced-motion handling.
• PII-clean: no emails, surnames, bundle ids, or private paths; scan before publishing.

Done looks like

• Three pages under docs/ cross-linked by a shared nav; hub fronts two question-based entry points; both deep pages self-contained and theme-aware; PII scan clean. GitHub Pages publishes on merge to main under /docs.

[testtest126]

Claimed — docs hub/nav + fleet page session (worktree clever-kapitsa-57c6a3), 2026-07-12

[testtest126]

Status / re-scoping. Breaking this umbrella into what's done and what remains:

• Fleet page ("How the Agents Talked") — ✅ done independently in docs: publish 'How the Agents Talked' (the making-of, public/softened… #160 (+ evolved in docs: publish 'The Fleet Went Wide' — night two of the making-of #178/Docs: multi-theme cultural skin switcher for The Fleet #179/Docs: rename the-fleet page title to "How the Legents Talked" #180/Docs: roll the cultural theme switcher onto night-two and architecture #181). My duplicate was dropped; docs: publish 'How the Agents Talked' (the making-of, public/softened… #160's page is canonical.
• "How MateMate Works" hub (docs/index.html) — ✅ in Docs: add a "How MateMate Works" hub landing page (refs #174) #176 (mergeable, hub-only, conflict-free).
• Shared cross-page top-nav on architecture + the-fleet — ⏳ split into Docs: add the shared cross-page top-nav to the architecture and the-fleet pages #188. Those two files are under active concurrent redesign (theme switcher rolled across them in Docs: multi-theme cultural skin switcher for The Fleet #179/Docs: roll the cultural theme switcher onto night-two and architecture #181), so a shared-nav PR against them conflicted 3×; better coordinated with that rollout. A verified implementation is preserved on branch claude/clever-kapitsa-57c6a3 @ 5a24bee.

Once #176 merges and #188 lands, #174 is fully resolved.