record(ORACLE-LLAMACPP-OWED-CPU): the boundary, the decision, and three counts that did not re-derive (#857)

[localai-bot]

FOLLOWING_AGENTS_PROTOCOL

Closes the two GPU-free ## Owed items from the llama.cpp repin (#857,
283c7e492) and files one issue. Records only: the diff is
.agents/specs/oracle-llamacpp-repin-stock.md and one appended
.agents/issue-index.md row.

The leading word boundary is restored

Stage 2 was rebuilt to compile from the same FAV dict as stage 1, which fixed a
real disagreement, but the retired pipe carried a leading \b that FAV did
not. Restoring it, measured on a clean detached worktree at 0f8580e269 with the
instrument extracted from the spec's own fence:

ratio branches	files	stage 1	files hit	stage 2
as they were	4525	1278	146	1042
leading \b restored	4525	1260	145	1024

18 removals, zero insertions. All 18 adjudicated by shape and site: 14
C2x/C3x, 2 sm8x/sm_12x, 2 Q8_0, every one glued text with no verdict
among them.

The safety claim is the one that mattered, since trading a false positive for a
false negative is the unsafe direction. Verified structurally rather than by
sampling: each of the 18 carried exactly one stage-1 alternative, the loose
ratio, and zero other comparison tokens, with zero tight-ratio matches.
No verdict was lost.

It also closes a question the spec had left open. Of the 38 candidates that match
a ratio and are invisible to the retired pipe, the boundary drops 34 and keeps
4, and the four it keeps are exactly the fractional-leading-zero spellings. So
the boundary removes glued text and keeps every real ratio, including every one
below 1.0.

The instrument stays in this document, with the condition that would reverse it

The open question was whether to keep growing per-shape controls inside a
markdown fence or move the sweep to tools/ with a suite under tests/tools/.

A caution I had raised turned out to be wrong, and was re-derived rather than
inherited. check-pr-size.py:510 attaches the mutation-evidence contract to
class governance_checker, defined at :162 as scripts/check-*.py|sh;
tools/*.py and tests/tools/test_*.py both fall through to :448 as
product. The contract would not have attached.

What refuses the move is what CI would enforce instead. tests/CMakeLists.txt:12
auto-discovers tests/tools/test_*.py, so the suite would run every build, and
what it would schedule green is a self-test that proves liveness and not shape
coverage. Scheduling that green raises its authority without changing its
content, beside a paragraph saying the green is no evidence about coverage.
Secondarily, check-role-discipline.py:63-71 makes tools/ a feature prefix, so
every later edit needs a reviewed row/* PR where .agents/ is integration, and
the sweep has no consumer after #1003.

The decisive argument is the policy one: nothing lands dead. After #1003 the
instrument is reachable only from its own test, which proves the class works and
never that anything reaches it.

The condition that reverses this is recorded, because a refusal without one
reads as permanent: if #1003 ever gains a second consumer, the decisive argument
evaporates and the move to tools/ should be taken again. Also recorded is the
weakest of the three reasons, and that a scheduled self-test genuinely would
catch a recurrence of the sixth hole.

Per-shape controls on every alternative are refused separately: a control is a
string its author writes, so seventeen invented shapes would read as coverage
while establishing nothing.

A third option killed itself under measurement

A per-alternative census was proposed, on the theory that an alternative with
near-empty reach is the signature of the × defect. It was measured against the
very defect it was meant to catch: the historical dead branch reaches 5312
lines and its dead ×\b half still reaches 470, against the repaired
branch's 2121. It would have printed 470, not something near 1, giving no
threshold a reader could act on.

Rejected, with its numbers recorded in place of the feature. Measuring a proposed
instrument against the bug it is meant to catch is cheaper than shipping it and
discovering the same thing later.

Counts that did not survive re-derivation

Three small counts in this document were wrong, in a document whose own thesis is
that a count without a re-derivable enumeration is untrustworthy. They were
repaired by re-deriving, and the section now carries a second fence, extracted
verbatim and run, that prints every corrected number:

stop 35 leave 18 survive 17
blind 38 dropped 34

• The four kept ratios are four lines and three spellings, 3+1 rather than
  2+1+1, since one line carries two of them.
• 35 candidate lines stop matching a ratio, 18 leave and 17 survive. The
  34/18/16 reading is true only when scoped to the 38 lines invisible to the
  retired pipe, and that scope is now stated, with the differing line named.
• Two antecedent slips corrected: three obligations rather than "all three" after
  naming two, and one anchor moved rather than two.

The same class caught the row again while it was being repaired:
origin/main landed check-cuda-op-arch-gate mid-flight, moving the recorded
gate blocks from 26/45/77 to 27/46/79. Both moves are now named, with the reader
told to re-derive the pair per run rather than trust either.

Also recorded: the adjudication table assigns one shape per line, so sm_12x
appears on five lines with four filed under C2x/C3x; all five are glued text
either way, so the adjudication does not move. And the recipe's single-fence
filter raises ValueError if a second matching python fence is ever added to
this spec, which fails loud rather than selecting the wrong block, and which
keeping the instrument in a document inherits.

Filed

#1058 — e34d71379e70 carries
none of the required trailer lines, verified by re-running the checker rather
than by taking the report. Owned by GATE-SQUASH-TRAILERS, since #870's CI
--filled PR-body guard is the missing enforcement. The commit is not repaired,
because history is not rewritable here.

Gates

scripts/agent-preflight.sh: 79 ok, 0 FAIL, 0 SKIP, exit 0, gated against
origin/main 100026481, named in both range headings, with the trailer block
executed rather than skipped.

The instrument's own mutation pass was rebuilt independently in review: 43 red,
3 green, 0 defects, every red row reporting applied=True with a non-zero line
delta, compiles=True, rc=1. The two dict-regeneration controls apply cleanly
and stay green, which is what shows the rewrite mechanism is not what turns the
other rows red.

Owed

The remaining ## Owed items on this row all need hardware and are unchanged:
the twelve re-takes under #1003, the keep-f16 default's decision, and a chosen
revision for Laguna's Poolside figure before it can be re-taken at all.

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