record(ENG-TRAILER-MERGE-ARTIFACTS): close the row DONE at 157080c8 - #416
Merged
Conversation
Closing the row BEFORE deleting its branch, which is the ordering that matters: audit-live-rows calls an ACTIVE row with no branch ABANDONED, and doing the cleanup first is exactly how main went red after dbd0d51 landed. The branch is still on the remote as this lands. State ACTIVE -> DONE with closing commit 157080c and a parity-ledger closure anchor, matching how ENG-NOW-DERIVED was closed. The claim file is deleted, which is what closing a claim means under the one-file-per-claim shape, and RUNNABLE_BASELINE shrinks by the row because a DONE row leaves the gated population entirely rather than taking a weaker verdict. The pre-existing `departed` set in test_check_gate_commands.py grows from three runnable DONE rows to four. That literal is updated rather than loosened, and my own near-duplicate guard is dropped: the canonical mutation test already covers re-adding a departed row, and two tests asserting the same thing is how a set like this drifts. The spec's `## Outcome` records what this row did NOT do. It fixed one of five observed shapes; f64f2b7 (bot co-author) is a real violation the broken parse had been hiding and now correctly fails, which looks like a regression and is the opposite; and the remaining three are merge-method artifacts whose fix is a process decision, not a checker change. That is why the row does not claim to have made main green. Gates: preflight rc=0; check-agent-record OK; check-doc-checkpoint OK; test_check_gate_commands 31. Issue: #406 FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:claude-opus-5 [Claude Code]
This was referenced Aug 11, 2026
localai-bot
pushed a commit
that referenced
this pull request
Aug 11, 2026
…418) check-pr-size correctly refused the change: scripts/check-agent-record.py moved without added evidence in its PAIRED suite. The bump is only a data re-pin, but the gate does not distinguish that, and it is right not to -- a bump with no row behind it looks exactly like a bump for a new row, which is the failure the pin exists to catch. Adds two cases keyed to THIS row rather than to the constant in general: the row appears exactly once in the engine matrix, and moving the pin by one must make the count disagree. The second is the mutation; without it the first would pass against a decorative constant. Not fixed here, and stated rather than left implicit: documentation-checkpoint also reds this PR, because adding a row as ACTIVE is a lifecycle claim that owes docs/STATUS.md and docs/BENCHMARKS.md. For a records-and-checker row those pages are the wrong home -- STATUS is the per-capability surface and a commit-trailer policy is not a capability -- so writing a line there to satisfy the gate would be dishonest documentation. #409 and #416 both landed with that same gate red. That is a real gap in the gate rather than in this change, and it deserves its own issue instead of a paper-over here. Gates: test_agent_record 31; check-pr-size now OK over this PR's range. Issue: #418 FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:claude-opus-5 [Claude Code]
joral
pushed a commit
to joral/vllm.cpp
that referenced
this pull request
Aug 11, 2026
Main advanced one commit (mudler#416, `ENG-TRAILER-MERGE-ARTIFACTS` closed DONE) between the gate and the push. Merged forward rather than pushed over. It touches both keyed records this branch also edits, and git auto-merged both. Neither auto-merge was kept (AGENTS.md "Records"): each file was reset to `origin/main` wholesale and the branch's one scoped edit reapplied against an anchor asserted to match exactly once. - `.agents/engine-matrix.md` — mudler#416 rewrote the `ENG-TRAILER-MERGE-ARTIFACTS` row and its lifecycle counts. The `KV-EVENTS` row is untouched by it and stays `ACTIVE`, so no count moves and none of the branch's totals are carried. - `scripts/check-gate-commands.py` — mudler#416 removed `ENG-TRAILER-MERGE-ARTIFACTS` from `RUNNABLE_BASELINE` (DONE is closed evidence, not live gated work). Took that set entire and reinserted only the `KV-EVENTS` entry. No product source is touched by this merge, so the 385/385 CPU `ctest` recorded one commit earlier still describes this tree's product code; the record gates are re-run below it. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: ClaudeCode:claude-opus-5 [ClaudeCode]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the row landed by #409. Issue #406.
Ordering matters here, and it's the whole point of the PR.
audit-live-rowscalls anACTIVErow with no branchABANDONED. Deleting the merged branch first is exactly howmainwent red afterdbd0d51clanded — so the row is closed before any cleanup, androw/ENG-TRAILER-MERGE-ARTIFACTSis still on the remote as this lands.What changes
ACTIVE→DONE, closing commit157080c8, with aparity-ledgerclosure anchor — matching howENG-NOW-DERIVEDwas closed.RUNNABLE_BASELINEshrinks by the row: aDONErow leaves the gated population entirely rather than taking a weaker verdict.departedset intest_check_gate_commands.pygrows from three runnable-DONErows to four. Updated, not loosened. My own near-duplicate guard is dropped — the canonical mutation test already covers re-adding a departed row, and two tests asserting the same thing is how a set like this drifts.The spec's Outcome records what the row did NOT do
f64f2b71(bot co-author) is a real violation the broken parse had been hiding, and now correctly fails. That reads like a regression and is the opposite.That's why the row doesn't claim to have made
maingreen.Gates
preflight rc=0;
check-agent-recordOK;check-doc-checkpointOK;test_check_gate_commands31.🤖 Generated with Claude Code