fix(site): make generated themes readable and simplify the catalog

[pathscale]

The theme builder now keeps default text, muted text, controls, and the top navigation readable across generated light/dark surface ladders. Generated, randomized, restored, persisted, and whole-site themes normalize every base, semantic, accent, foreground, soft, and hover token, and exported CSS includes every live token.

The component catalog is one Components destination. It opens on Surfaces, where Honey's AuthPoweredBy example and the Complete Coverage lab are visible. The homepage headline is Build Exceptional UI/. Glass exposes only the material switch, Blur, Refraction, Depth, and Reset.

The QA profile reaches Complete Coverage through Components → Surfaces → Complete Coverage, preserving the full strict denominator. The production-policy check accepts the deliberately unenforced deployment, rejects Google Fonts runtime downloads, and validates runtime-style compatibility whenever a real CSP is enabled.

Validation on pushed commit d6f3f45 with the published registry @pathscale/ui@3.2.3:

• typecheck and production build pass
• theme/export property suite: 9/9, 71,460 assertions
• full native site suite: 675/675
• strict inventory: 353/353 outcome-declared, including the 164-control Complete Coverage lab; zero anonymous, missing, unstable, duplicate, manual, or unverified controls
• published-package theming suite: 233/233 under the unscaled local deadline; persisted strength recomposition now carries the same explicit outcome budget as every equivalent strength check
• production-policy verifier accepts both the deliberately unenforced js.software response and the enforced compatible house policy
• source and built output contain no Google Fonts URLs; product source/dependencies contain no Canvas or Cytoscape

No deployment is included.