Merge pull request #1 from txn2/docs/mcp-logos

add mcp project marks to the home page

add DESIGN.md and tokens.json: canonical visual identity spec

DESIGN.md follows the Google Labs spec format (apache-2.0, alpha,
April 2026): YAML front matter mirroring the token namespaces,
then the eight required H2 sections in fixed order:

  1. Overview
  2. Colors
  3. Typography
  4. Layout
  5. Elevation and Depth
  6. Shapes
  7. Components
  8. Do's and Don'ts

Two extension sections after the canonical eight:

  9.  Voice and Copy        (no em-dashes, no AI-tell vocabulary,
                             no invented project names, terse voice)
  10. Downstream contract   (three valid adoption levels for sibling
                             sites: reference, token alignment, full
                             re-skin; today all six downstream sites
                             are at level 1 and that is fine)

tokens.json is a W3C DTCG-compliant sidecar at the repo root. Top
groups: color, font, size, radius, border, shadow, breakpoint,
typography, mermaid, blueprint, grain, vignette, focus, component.
Every leaf has $type / $value. References use {token.path}.
Composite shadow token for the terminal block.

Source of truth: static/css/site.css. Every hex and font value in
DESIGN.md and tokens.json was lifted directly from the running CSS.
The mermaid theme block is mirrored verbatim from layouts/index.html.

Verification:
- YAML and JSON parse cleanly
- zero em-dashes / en-dashes anywhere
- 13 colour tokens round-trip CSS, DESIGN.md, tokens.json
- hugo --minify --gc clean; root files do not leak into docs/

README updated with rows pointing at the new files. No downstream
sites touched (kubefwd.com, txeh.txn2.com, mcp-*.txn2.com remain on
their existing MkDocs Material setup).

remove invalid repos, reorder MCP-first, swap ASCII diagram for mermaid

Stack list, ItemList JSON-LD, llms.txt, and the hero ticker had
entries that were not real txn2 repos. Removed: mcp-amp, n2proxy,
n2x, dmk, port-proxy. Replaced with verified repos and their
GitHub-published descriptions: portpxy, jwtpxy, amp, rxtx, asws,
mcp-common.

Section reorder per request:
  § 01 — model context protocol servers (lead)
  § 02 — utilities (kubefwd, txeh)
  § 03 — other components

Rail nav matches: mcp / utilities / stack.

Diagram in the mcp-data-platform card switched from ASCII <pre> to
Mermaid (lazy-loaded from jsdelivr CDN, only when a .mermaid
element is on the page). Themed to the site palette: ink-3 nodes,
parchment text, signal-orange border on the platform node, mute
edges, JetBrains Mono. Hidden until rendered. Init uses
startOnLoad:false + explicit mermaid.run() since the ESM build
does not auto-fire on DOM ready.

Copy refresh: mcp-data-platform now uses the GitHub blurb
(semantic data platform composing mcp-s3/mcp-trino/mcp-datahub
with bidirectional cross-injection). mcp-datahub mentions the
composable Go library.

Workflow: deploy now triggers on master pushes AND v* tag pushes
AND release publish AND workflow_dispatch. github-pages env
configured via API to allow v* tag deploys.

fix CI deploy: trigger on master pushes, not tag refs

The github-pages environment defaults to "deployments only from
master" — tag pushes (refs/tags/v*) fail that rule, which is why
the v9.0.0 deploy step errored with HTTP 400.

- Trigger on push to master + workflow_dispatch + pull_request
  (build-only).
- Drop tag and release triggers — release flow is now: tag the
  commit, then `git push origin master <tag>` so the deploy fires
  from the master push event and `git describe --tags` resolves
  the version.
- workflow_dispatch accepts a version input for manual overrides.
- Added images/og.png to the build verification step.
- README updated with the new release flow + reminder that Pages
  source must be set to "GitHub Actions" (otherwise the legacy
  pages-build-deployment workflow keeps running and failing).