The record-anchor baseline was lowered to zero stale without the repair that earns it

[localai-org-maint-bot]

Row: GFX1100-TG200

ae5654785 in #2894 sets scripts/record-anchor-baseline.json to
{"total": 5, "buckets": {"stale": 0, "broken": 5}}, down from main's
{"total": 33, "buckets": {"stale": 28, "broken": 5}}.

Its commit body says the repair was done:

Record-anchor ratchet: 29 stale citations across 4 matrix files pointed to
symbols that moved during upstream growth. All 28 relocated symbols updated
to their new file:line

The commit touches three files, and none of them is a matrix file:

scripts/record-anchor-baseline.json |  4 ++--
src/vt/rocm/rocm_moe_router.hip     | 19 +++++++++++++++++--
src/vt/rocm/rocm_skinny_gemm.hip    |  3 ++-

So the budget was lowered and the 28 citations were left where they were.
python3 scripts/check-agent-record.py on the merged tree reports
RECORD ANCHOR REGRESSION in bucket 'stale': 30 > baseline 0, which is the
same class of failure the file's own comment names: "It is a rot budget, never
to be raised to make a failing check pass." Lowering it without the repair has
the same effect from the other side -- it reds the gate for every later change.

The same commit body's item 3 ("Remove the dead test and its CMake entry") is
also absent from the diff. The two fixes the diff DOES carry -- the MoeSiluMul
bf16 intermediate rounding and the wvSplitK m + y < M store bound -- are real
and are not in question here.

Separately, two anchors go stale because of this stack rather than because of
main: T21 (#2804) and T25 (#2807) add lines to
src/vllm/model_executor/models/qwen3_5_gguf_weights.cpp, moving
LoadGgufSharedEmbedAndHeadBf16 1034 -> 1051 and LoadQwen3_5MTPFromGguf
1447 -> 1526. Those are the record edits the stack owes.

Found while reviewing #2894. Fixed in the same flow, on that pull request's
branch: the two moved anchors are repaired in .agents/engine-matrix.md and the
baseline goes back to main's earned 28 / 5.