[chmjkb]

Description

Part of #70: a new docs page, Zoo → Guides → Exporting weights, on how to get your own weights into runntime.

• The weights file: one safetensors file with the names the model's loader expects, how a runner gets it (modelPath, spreading a models config).
• How a file loads: header and name check before any download, 8 MB range chunks, browser cache keyed by the URL, file dtype vs the model's dtype.
• Exporting float weights from a Hugging Face checkpoint, and checking a file (CHECKPOINT_MISMATCH and what it reports).
• Quantizing with runntime quantize (feat(tools): add runntime quantize, a uv Python CLI that writes int8/int4 checkpoints in format v1 #93): command, defaults, --f16, --drop, --include/--exclude, reading the report, measured MiniLM file sizes.
• The quantized format and shape rules, now in one place; the Embedding page's quantized section keeps only MiniLM's own rule (q/k/v together) and links here.
• Picking the setting: int8 in groups of 32 is the safe pick; int4 costs quality on the real MiniLM weights (worst cosine 0.94, top-3 changes on 8 of 20 queries).
• QAT: a float QAT checkpoint quantizes like any other; the tool's exact rule; no zero points or int8 activations.
• Three diagrams as Astro components on the site's theme tokens: the path from checkpoint to load, what a quantized file holds, how one group of 32 weights is quantized.

Introduces a breaking change?

• Yes
• No

Type of change

• Bug fix (change which fixes an issue)
• New feature (change which adds functionality)
• Documentation update (improves or adds clarity to existing documentation)
• Performance (kernel tuning, graph building, anything related to performance)
• Other (chores, tests, code style improvements etc.)

Testing instructions

1. pnpm typecheck && pnpm lint && pnpm format:check
2. pnpm --filter docs... run build, then pnpm dev:docs and open /zoo/exporting-weights/ in light and dark theme, desktop and phone width.
3. Every bash and Python snippet on the page was run as written; the file sizes and report lines come from quantizing the hosted MiniLM f32 file.

Related issues

Part of #70. Stacked on #93.

Checklist

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings

Additional notes

• Only all-MiniLM-L6-v2 loads a quantized file on main so far; the page says so in one place, to extend as Moonshine and EmbeddingGemma 2 land.
• No speed numbers on the page: the benchmarks page gets measured ones separately.