Include provenance and license notices for bundled documentation fonts #395

Part of #382 — v1.0.0 alpha readiness.

Problem

The documentation redistributes seven Inter/Roboto Mono WOFF2 files referenced by docs/styles/fonts.css:1-L102, but matching font license/attribution files are not tracked or emitted with the generated site.

The review found Inter project copyright metadata and Roboto Mono/Google metadata, including an Apache 2.0 license URL in the sampled Roboto Mono file. Do not assume a current upstream font release has exactly the same licensing/provenance as these older bundled binaries; verify the actual assets.

Acceptance criteria

• Identify the source/version and applicable license for each bundled font family/asset set, including the subset Inter files.
• Include the required copyright/license notices in the repository and generated documentation distribution (for example through docs/public).
• Record provenance and any relevant subsetting/modification information.
• Verify the notices are present in the built site artifact and discoverable from documentation attribution.
• If provenance cannot be established, replace the assets with verifiably licensed equivalents or an appropriate system-font fallback.
• Preserve the npm source-only packaging boundary; fonts/tools are not part of the npm tarball.

Scope is documentation distribution hygiene, not a claim that the npm package is missing its MIT license.