policy(porting): a model port documents the WEIGHTS it was fed, not just the code (#672)

[localai-bot]

Records only — no src/, include/ or tests/ change. Supersedes #951, which
carried a force-push artifact in its commit range; this is the identical diff
rebuilt on a clean branch with no rewritten history.

Developer-directed. MiniMax-Music3 is the case that made it concrete: the port
landed complete, and a reader still could not run it without being told that the
57.4 GB repository is ~28.5 GB in the arm we actually load, split across six
component directories, with a native .pth layout we refuse by name and
fourteen community quantized repositories we do not implement.

None of that is inferable from a header file. The code is the easy half to
publish; saying what to feed it is the half that makes the port usable — and it
was nowhere in the checklist.

The rule

.agents/porting-a-model.md §2.1, with a checkbox in §2 and a pointer from
AGENTS.md's quantized-arms paragraph: every ported model documents the
checkpoints it was built and gated against in docs/USAGE.md, in the same
change that makes the capability reachable, mirroring the table MiniMax-H3
already carries — file name, size, and a link to the exact HuggingFace repo,
grouped by arm.

What a row owes, and why each clause exists

Clause	The thing that bit us
repo id and revision; sha256 for a quantized artifact	unsloth/Qwen3.6-27B-NVFP4 was silently re-quantized in place under an unchanged name; Music3's GGUF lineage is published four ways under one model (audiocpp, mm3, qwen3, wan) and wan collides with genuine Wan video GGUFs
which arms are refused	same polarity as the refuse-by-name rule one paragraph above: a user should read the refusal in the docs, not discover it at load time
the resident size	it is not the repository's size, and it is what decides whether a reader can run it at all
whether a third party published it	community quant repos are the arm most users reach for, and carry different provenance from a first-party release

Placement

In porting-a-model.md rather than verification.md or benchmarking.md,
because it is a property of shipping a model rather than of gating or
measuring one — and because that file is the checklist an implementer already has
open. AGENTS.md carries it in prose so the rule is reachable without opening the
guide.

Its first application is the MiniMax-Music3 weights table in #966.

Gate: check-agent-record OK, check-doc-checkpoint OK, check-commit-trailers
OK over the PR range.

🤖 Generated with Claude Code

FOLLOWING_AGENTS_PROTOCOL

Following-Agents-Protocol: true
AI-Assisted: true
Assisted-by: AGENT:claude-opus-5 [Claude Code]