[justinchuby]

Context

This is a follow-up investigation, not a fix for a currently-broken state. On fresh main (post #1884/#1893), both tests/fixtures/tiny-deepseek-v4-qmoe and tests/fixtures/tiny-glm52-full-attention already load and decode correctly — the missing-policies/*.onnx problem I'd flagged in a prior cycle was already fixed by #1883 (re-emitting inference_metadata.yaml with migrate_model_io --reemit, dropping ten hand-authored, never-real auxiliary policy components) and #1888 (test-matrix follow-up). That fix is correct, already reviewed, and this PR does not revisit it.

What this PR actually fixes

Regeneration determinism. Re-running generate.py (and its --full-attention variant) against each fixture's pinned Mobius commit reproduces model.onnx.textproto/tokenizer.json byte-for-byte, but not inference_metadata.yaml — it reproduces the pre-canonicalization document write_onnx_genai_config emits, not the canonical single-decoder-component shape actually committed. This is true for all three tiny fixtures (not just the two #1883 touched), meaning a naive future regeneration would silently reintroduce the exact bug #1883 fixed.

Fix: document the required two-step recipe (generate.py, then migrate_model_io --reemit <output-dir>) directly in each generator's docstring. Docstring-only change — no functional/behavior change, no fixture artifacts touched.

Verification (2026-08-23, idle A100, CUDA_VISIBLE_DEVICES pinned, hostlock-gated)

• generate.py alone vs committed: textproto/tokenizer byte-identical, metadata differs — confirmed for all 3 fixtures.
• generate.py + migrate_model_io --reemit vs committed: metadata byte-identical — confirmed for all 3 fixtures.
• cargo test -p onnx-genai-metadata --test decoder_recognizer_agreement: 14/14 pass (existing matrix from test(metadata): follow the re-emitted DeepSeek-V4/GLM-5.2 fixtures in the matrix (main is red) #1888 already guards the committed shape; no new test needed for a docstring-only change).
• cargo test -p onnx-genai-engine --features native-cuda --test deepseek_v4_tiny_qmoe_e2e --test glm_tiny_full_attention_e2e --test glm_tiny_qmoe_native_cuda_e2e: 12/12 pass, CPU/CUDA tokens byte-identical to ANCHOR_IDS for all 3 fixtures.
• DeepSeek-V4 CUDA: captures=1 replays=10 fallbacks=0 (native e2e test) / captures=5 replays=310 fallbacks=0 (profile_native, n=3 steady). GLM full-attention CUDA: captures=1 replays=10 fallbacks=0 in a small run / captures=3 replays=186 fallbacks=0 (n=3 steady) — capture state recorded, not forced. GLM IndexShare CUDA: captures=0 replays=0 fallbacks=0, growing-KV-prefix decline (unchanged from prior cycle).

Independent review (code-review agent) caught and this PR fixes: a \ vs \\ line-continuation bug that silently collapsed a documented shell command onto one line in the deepseek docstring, and confirmed the default GLM-5.2 IndexShare variant also needs the reemit step (verified directly via regenerate+reemit-vs-committed diff, since #1883 never touched that fixture so there's no "pre-1883 blob" to diff against for it).

Scope

No fixture regeneration performed or needed. No Mobius changes. No coarse-residency files touched. Independent of #1854.

Closes the "regenerate missing policies" instruction as superseded — see full task report for the baseline-measurement portion of this cycle.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.71%. Comparing base (31d0380) to head (c0ce121).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1902      +/-   ##
==========================================
- Coverage   80.80%   80.71%   -0.09%     
==========================================
  Files         415      415              
  Lines      204440   204440              
  Branches   204440   204440              
==========================================
- Hits       165201   165018     -183     
- Misses      33664    33847     +183     
  Partials     5575     5575              

Flag	Coverage Δ
cli-ort-linux	72.51% <ø> (ø)
cli-ort-windows	72.01% <ø> (-0.10%)	⬇️
mlas	85.20% <ø> (ø)
offline	80.86% <ø> (-0.10%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 6 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.