fix(record): repair the five red preflight record gates to their own contracts - #3369
Merged
Merged
Conversation
ISSUE-LOCAL-01M3WMKTBEDAHF226YSATSR7BF: five record/doc gates are red on origin/main. The spec names each checker's contract and the record each repair restores; the commit order that follows proves the spec landed before the implementation it governs. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:zai/glm-5.3-flash [maki]
…anchors
check-release-binary-contract requires the single `| REL | ROAD-V1-RELEASE |`
row to carry `ACTIVE` with the v0.0.2-published text and the pending Windows
publication gate ("Windows W14-W16 are implemented for one PR", "publication
and 32-asset audit remain pending", issue PREFLIGHT-GATE-REPAIRS /
ISSUE-LOCAL-01M3WMKTBEDAHF226YSATSR7BF); check-windows-release-state requires
exactly one `<!-- ENG-RELEASE-WINDOWS: state=ACTIVE publication=pending
artifact=unpublished -->` anchor and the `v0.0.3-pre.1` pending phrase on the
same surface. The record restructure dropped both from .agents/roadmap_v1.md
while engine-matrix, coordination.md, the release spec's machine block and the
state event all still carry the published-v0.0.2 state the checker's
EXACT_MACHINE_FIELDS pin, so the roadmap row was the drifted surface. Both
anchors are restored verbatim from history (10a64f8 for the row, a0a8fed
for the anchor); no expectation was reconciled away, and no published-binary
denial survives to contradict the four sibling surfaces.
FOLLOWING_AGENTS_PROTOCOL
Following-Agents-Protocol: true
AI-Assisted: true
Assisted-by: AGENT:zai/glm-5.3-flash [maki]
check-benchmark-index fails closed on any docs/benchmarks/*.md that no `| \`id\` | ... | [label](benchmarks/file.md) |` row in the `## Benchmark detail index` table of docs/BENCHMARKS.md owns, with the ID required to equal the file stem; 16 legitimate public benchmark detail files had lost their rows (ISSUE-LOCAL-01M3WMKTBEDAHF226YSATSR7BF). Each is indexed with a one-line disposition taken from its own content; no file is deleted. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:zai/glm-5.3-flash [maki]
check-env-doc fails closed on any VT_*/VLLM_* name read from src/ or include/ that is neither documented in docs/ENVIRONMENT.md nor listed on scripts/env-doc-allowlist.txt (ISSUE-LOCAL-01M3WMKTBEDAHF226YSATSR7BF). VT_VK_DISABLE and VT_VK_DISABLE_PAGED_ATTN are temporary kernel-internal bisect hooks in src/vt/vulkan/vulkan_ops.cpp (982, 1296) that force ops down the fallback tier, so they are allowlisted. VT_VK_FENCE_TIMEOUT_MS is a user-facing operational watchdog (src/vt/vulkan/vulkan_context.cpp:174) that aborts instead of spinning forever on a wedged dispatch, so it is documented as a deployment knob with its block-forever default. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:zai/glm-5.3-flash [maki]
…peats it check-oracle-pins requires each declared pin surface's `<!--pin:commit-->` span to be a lowercase-hex prefix of upstream-sync.md's vllm_commit and its `<!--pin:label-->` span to equal the public version of vllm_runtime_version, because the parity-pin block is the authority and a surface that restates it must restate the current value; .agents/oracles/vllm.md's oracle-pin block is held to the same identity (ISSUE-LOCAL-01M3WMKTBEDAHF226YSATSR7BF). The 2026-09-26 sync 4f11dfc advanced the pin to a7c23ac96d / 0.3.0.dev267 but left the oracle record and five prose surfaces at e126687a9a / 0.28.1rc1.dev132. Every span now restates the current pin, and the surrounding "since 2026-09-03" claims are re-dated to the advance that actually produced it. NOW.md also gives back one line so the live digest is not exactly at its cap. FOLLOWING_AGENTS_PROTOCOL Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:zai/glm-5.3-flash [maki]
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
1 participant
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.
Five preflight record gates are red on main; this branch repairs each to its checker's own contract, reconciled to the true state throughout.
Verification: all five gates plus check-agent-record exit 0; record suites 258 passed, gate suites 149 passed. Issue: ISSUE-LOCAL-01M3WMKTBEDAHF226YSATSR7BF, spec committed first.
FOLLOWING_AGENTS_PROTOCOL
Following-Agents-Protocol: true
AI-Assisted: true
Assisted-by: AGENT:zai/glm-5.3-flash [maki]