docs: graphite re-skin (technical type, cool palette) + content clarity

[cjimti]

Summary

Re-skins the documentation site's type and color system and fixes several legibility and content issues across the homepage and reference pages. The changes are token-driven and apply site-wide (homepage and inner docs) with no structural changes to the MkDocs Material layout.

Type system

Headings and code are set in Geist Mono and body in Geist; the Fraunces display serif is removed everywhere. Inner-page and homepage headings are non-italic mono. Emphasis in prose is Geist italic rather than a display face.

Color

The palette is a cool graphite grey ground (--ink #1E232A) with a single restrained cyan accent (--signal #4FC7E6). The previous warm palette, the orange radial glow, and the edge vignette that crushed the background toward black are removed; the remaining hardcoded orange tints are remapped to cyan and the blueprint grid lines are cooled. Code-syntax hues are tuned for the grey ground.

Chrome

The header uses the real mcp-data-platform symbol (concentric aperture plus accent square) in place of the glyph mark, and the live UTC clock is removed from the header and footer.

The top-rail navigation now tracks the current section. Each rail link declares the path prefixes it owns via data-scope, and a small tracker subscribes to Material's document$ so the active item follows navigation — including instant navigation, which swaps content without re-rendering the header — instead of remaining on "home".

Admonitions and the active nav item no longer use an accent left rail; type is signalled through the title and icon color, and Material's built-in per-type admonition border colors are neutralized so every callout reads as a plain bordered box on the grey ground.

The previous/next footer links drop the cramped title box for clean labels with a hover state, and the copyright line links Craig Johnston to imti.co, Deasil Works, Inc. to deasil.works, and adds Plexara at plexara.io.

Homepage

The intro paragraph no longer splits the product name with a dropcap, and the closing "open source" paragraph is set at normal reading size rather than display size.

The "what it does" feature list drops the 001–00N numbering and the uppercase tag chips; it is now an unordered list of capability name plus description.

Reference content

The benchmarks page gains a "How to read this page" legend up front that defines the shorthand in plain language: the arms (A0 raw tools, A2 platform, A3 lifecycle), the suites (S1 discovery, S3 knowledge traps, S5 memory lifecycle), the scores (3/3, pass^k, median and p90 tool calls), and the trap classes (units_cents, net_revenue). Every definition is derived from the page's existing content.

Mermaid

Mermaid under-sizes sequence-diagram note rectangles, so note text can exceed the rect by roughly twenty pixels. The note box now uses a fill-matched border instead of a hard accent border, so the overflow reads as a soft label rather than a broken box. Styling is applied through the --md-mermaid-* custom properties, which reach the diagram across the Shadow DOM boundary.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.04%. Comparing base (dd6dc58) to head (a6ba6e8).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #954   +/-   ##
=======================================
  Coverage   89.03%   89.04%           
=======================================
  Files         424      424           
  Lines       48581    48581           
=======================================
+ Hits        43256    43257    +1     
  Misses       3549     3549           
+ Partials     1776     1775    -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.