record(intake): place five issues filed during the Nemotron campaign (#514, #515, #547, #569, #573) - #580
Merged
Merged
Conversation
…514, #515, #547, #569, #573) FOLLOWING_AGENTS_PROTOCOL "No work without an open issue" only holds if the issue is reachable from the intake surface. These five were filed and worked but never linked from the roadmap table, so the table understated what is open and none of them was findable from the place the protocol says to look. #569 is the one that matters most and is already fixed on a branch: the Nemotron revision pin was existence-only, so a directory holding a DIFFERENT model resolved as long as a `trees/<rev>.json` manifest sat beside it -- and the manifest can be empty. It is placed on the model row because it gates W6's token-exact gate, which is exactly the instrument that cannot see a substituted checkpoint. #515 and #573 are both check-doc-checkpoint creating a shared-write surface, so both go on ENG-RECORD-CONFLICT-SURFACES: the first classifies any root CMakeLists.txt edit as a usage change, the second evaluates its obligation per COMMIT rather than per change, which forced this campaign to squash a branch and lose its RED-first history. #514 is placed on ENG-RELEASE-WINDOWS: both windows-msvc jobs fail on EVERY pull request while main stays green, because those jobs are skipped on push. That makes CI unusable as a signal from the one place it is read. #547 is left unplaced. It is a shared-seam defect -- GB10 reports UnifiedMemory() true, so ReferenceTierEligible(kCUDA) installs the CPU host kernel over cudaMalloc pointers where it needs DeviceMemoryIsHostAddressable() -- and I am not confident which row owns the op-provider seam. The table documents an em dash for exactly that case, and guessing a row would put wrong data in a keyed record. Records only, no product code touched. Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:claude-opus-5 [Claude Code]
FOLLOWING_AGENTS_PROTOCOL Correcting my own characterisation. I described both windows-msvc jobs as failing on #514's POSIX setenv/unsetenv. They do not. windows-msvc-vulkan fails on #514, the C3861 compile error. windows-msvc-cpu fails on #512, a PowerShell workflow defect -- "Cannot bind argument to parameter 'Arguments' because it is an empty array" -- with ZERO compile diagnostics. Verified on the #514 fix branch's own run: the cpu job's failure is byte-identical to the baseline PRs and has nothing to do with the POSIX APIs. That matters because it changes what fixing #514 buys: the vulkan job only. windows-msvc-cpu stays red on every PR until #512 lands too, so CI is not restored as a signal by either fix alone. Records only, no product code touched. Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:claude-opus-5 [Claude Code]
localai-bot
pushed a commit
that referenced
this pull request
Aug 13, 2026
…pin gate and the intake record (#517) Fourth re-merge of this land-prep; `origin/main` `51ec6bed5` -> `751325460`. Both new commits are clean auto-merges and neither collides with W2: - `751325460` (#579) re-pins the Nemotron checkpoint by CONTENT in `tests/parity/hf_snapshot.h` and `tests/parity/test_hf_snapshot_pinning.cpp`. That is the same file this branch resolved in its FIRST merge, so it is re-checked rather than assumed: `git diff origin/main -- tests/parity/hf_snapshot.h` is EMPTY, i.e. main's version stands whole, and the branch contributes nothing to it. - `ce7071122` (#580) is a records-only intake placement. `.agents/specs/nemotron-h-model.md` is unchanged on main across this pair, so the hand-merged version from the previous commit still holds; re-verified block by block anyway -- 16 blocks, 13 BYTE-IDENTICAL to main, and the 3 that differ are W2's own (§2's one table row, the new §6a, §7 `Now`). The delta vs `origin/main` remains exactly this branch's eight W2 files, and `src/vt/cuda/cuda_moe.cu` and `vt/ops.h` are untouched by this merge, so the GPU-verified CUDA arm is still unchanged. FOLLOWING_AGENTS_PROTOCOL Refs #517. Refs #579. Following-Agents-Protocol: true AI-Assisted: true Assisted-by: AGENT:claude-opus-5 [Claude Code]
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.
Five issues were filed and worked during the Nemotron campaign but never linked from
.agents/roadmap_v1.md's issue table — the intake surface the protocol says to check before claiming a row. The table understated what is open.MODEL-TEXT-nemotron-h-…ENG-RECORD-CONFLICT-SURFACESENG-RELEASE-WINDOWSmainstays greenRecords only. No lifecycle move, no measurement, no product code.
agent-preflight.sh --stagedgreen.🤖 Generated with Claude Code