docs: record that system_files/nvidia/ is unconsumed and has no CDI preset — docs/skills/nvidia/{SKILL.md,references/architecture.md}, system_files/nvidia/README.md - #1125
Conversation
Danathar
left a comment
There was a problem hiding this comment.
Verified the factual claims: bluefin's Containerfile (testing, lines 48-49) copies only /system_files/shared and /system_files/bluefin from common; nothing in bluefin references system_files/nvidia; system_files/nvidia/usr/lib/systemd/system-preset/ does not exist in common; and the only mentions of ublue-nvidia-flatpak-runtime-sync across the org are the unit itself, its bats test, and docs — no preset or systemctl enable anywhere. Docs-only, and keeping #1124 open for the actual wire-or-delete decision is the right split.
|
Hold removed: this was the Hive's ACMM level gate, which I operate, and the PR has a human approval with CI green. Ready for a maintainer to merge. |
There was a problem hiding this comment.
docs-currency
- (low) The new docs cite unpinned cross-repo line numbers that have already drifted.
docs/skills/nvidia/SKILL.md:53-55,references/architecture.md:57-58, andsystem_files/nvidia/README.md:6-8all say utah copies atContainerfile:66-67— that was true at the SHA pinned in the PR body (@636b48e), but utah's default branch now has those COPYs at lines 76-77. Suggest either pinning the SHA in the doc text (as the PR body does) or dropping the line numbers and citing the COPY stanzas by content.
Substantive claims verified at head c74ebff: no preset exists under system_files/nvidia/ (tree has only the service + libexec helper), bluefin/bluefin-lts/utah all copy /system_files/shared + /system_files/bluefin only, and no CDI preset exists in projectbluefin/bluefin.
No findings from: correctness, security, intent-alignment, style.
— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.78
There was a problem hiding this comment.
docs-currency
- New text cites a bluefin-lts path that does not exist.
docs/skills/nvidia/references/architecture.md:68(added by this PR) says CDI auto-generation is enabled per-consumer via bluefin-ltssystem_files_overrides/gdx/…. bluefin-lts has nogdxoverride directory — at both HEAD and the SHA2170146this PR cites, the preset is atsystem_files_overrides/nvidia/usr/lib/systemd/system-preset/80-nvidia-container-toolkit.preset(override dirs there arenvidia,dx,hwe, arch variants — nogdx). The unchanged SKILL.md table row for bluefin-lts (docs/skills/nvidia/SKILL.md:43) and the pre-existinggdxsection (architecture.md:92-99) carry the same stale name, so a PR whose stated purpose is docs-truth is re-asserting it in fresh text. Suggest correcting line 68 tosystem_files_overrides/nvidia/…(and noting the stale table row in #1124 if a broader fix is out of scope here).
Every other factual claim verified at head c46a0e4: no preset dir under system_files/nvidia/ (tree contains only usr/lib/systemd/system/ and usr/libexec/), common Containerfile:90 publishes /system_files/nvidia, and none of bluefin (Containerfile:48-49), bluefin-lts (Containerfile:17-18), utah (Containerfile:76-77) copies it. Dakota's elements/bluefin-nvidia/nvidia-container-toolkit-preset.bst exists. index.json/index.md regeneration is internally consistent (version 1.2, 2026-09-15, 40 skills). #1124 is open.
No findings from: correctness, security, intent-alignment, style.
— hive: agent=reviewer backend=copilot model=claude-fable-5
Danathar
left a comment
There was a problem hiding this comment.
Re-approved at ea9631b after two follow-up commits. They correct the LTS override directory from gdx/ to nvidia/ (I checked projectbluefin/bluefin-lts: system_files_overrides has nvidia, x86_64-nvidia and aarch64-nvidia, no gdx) and replace Containerfile line-number citations with a grep the reader can run, which will not drift. Docs only, CI green.
…has no CDI preset docs/skills/nvidia/SKILL.md, docs/skills/nvidia/references/architecture.md and system_files/nvidia/README.md described a delivery path the build does not produce: - The ctx stage publishes /system_files/nvidia, but bluefin (Containerfile:48-49), bluefin-lts (Containerfile:17-18) and utah (Containerfile:66-67) copy /system_files/shared and /system_files/bluefin only. Nothing in the org enables ublue-nvidia-flatpak-runtime-sync.service and this repo ships no preset for it. - Both docs cited system_files/nvidia/usr/lib/systemd/system-preset/80-nvidia-container-toolkit.preset as this repo's CDI preset. That path has never existed (git log --all over it is empty), so bluefin's 'inherits from common' row was also false. Docs-only: records measured state and points at common#1124 for the disposition decision. Skill frontmatter bumped to 1.2 and the generated index regenerated with scripts/generate_skill_index.py --write. Refs #1124 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
The cross-repo citations pinned bluefin, bluefin-lts and utah Containerfile line numbers. utah has already drifted (66-67 -> 76-77 on its default branch), so the docs were stale before merge. Replace the line-number citations with a content-based description plus a reproducible grep command. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The nvidia build overlay in projectbluefin/bluefin-lts lives in `build_scripts/overrides/nvidia/` and `system_files_overrides/nvidia/`; there is no `gdx` override directory at HEAD. Also correct the build entrypoint path to `build_scripts/build.sh` and note the arch-specific override directories. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ea9631b to
6028704
Compare
castrojo
left a comment
There was a problem hiding this comment.
LGTM. Clean rebase on main; docs accurately record that system_files/nvidia/ is unconsumed and has no CDI preset.
There was a problem hiding this comment.
docs-currency
docs/skills/nvidia/SKILL.md:4setslast_updated: "2026-09-15"(mirrored intodocs/skills/index.json:471), but the change lands 2026-09-22 (generated_atin the same regenerated index). Minor: the freshness stamp predates the edit it describes.
All factual claims in the diff were verified against the repos at head 6028704: system_files/nvidia/ contains no system-preset/ dir; common Containerfile:97 publishes /system_files/nvidia but bluefin (Containerfile:48-49), bluefin-lts (Containerfile:17-18) and utah (Containerfile:76-77) copy only shared/bluefin; bluefin-lts overrides live under nvidia/ (not gdx/) with system_files_overrides/nvidia/.../80-nvidia-container-toolkit.preset present and build_scripts/build.sh at that path; no systemctl enable of ublue-nvidia-flatpak-runtime-sync.service exists in the org; issue #1124 is open.
No findings from: correctness, security, intent-alignment, style.
Confidence: 5/5 (safe)
— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.78
Docs-truth correction
Files claimed:
docs/skills/nvidia/SKILL.md("The three repos and their nvidia stacks" table + new "system_files/nvidia/ships to nobody" subsection),docs/skills/nvidia/references/architecture.md(theprojectbluefin/commonbullet list under "Per-repo: where nvidia code lives"),system_files/nvidia/README.md(header status note), and the generateddocs/skills/index.json/index.md(frontmatter bump only). Cluster: issue #1124 — the unconsumedsystem_files/nvidia/overlay.No code, unit, preset, script or test is touched. This PR only makes the docs describe what the build actually produces.
What was wrong
80-nvidia-container-toolkit.presethas never existed here.SKILL.md:42andreferences/architecture.md:55both namedsystem_files/nvidia/usr/lib/systemd/system-preset/80-nvidia-container-toolkit.presetas this repo's CDI preset.git log --all -- system_files/nvidia/usr/lib/systemd/system-presetis empty. The same table recorded bluefin's CDI preset as "inherits from common"; bluefin has no such preset either.system_files/nvidia/reaches no image. The ctx stage publishes/system_files/nvidia, but every consumer copiesshared+bluefinand stops —projectbluefin/bluefin@5729176Containerfile:48-49,projectbluefin/bluefin-lts@2170146Containerfile:17-18,projectbluefin/utah@636b48eContainerfile:66-67. Nosystemctl enableforublue-nvidia-flatpak-runtime-sync.serviceexists anywhere in the org, and this repo ships no preset for it.tests/test_nvidia_flatpak_sync.batsasserts against files on disk, so it stays green either way.The docs told contributors that edits under
system_files/nvidia/"flow into all nvidia-variant images at next build". They flow nowhere.What this PR does not do
It does not delete the overlay and it does not wire it up. Both dispositions are recorded in #1124: wiring it requires a consumer-repo
COPYplus an enablement decision (behavior change, human owner); deleting it discards an actively maintained unit (last functional change #769). This PR only stops the skill from asserting a layout that was never built, and marks the tree so the next contributor does not assume delivery.Verified locally:
scripts/check-doc-links.sh,scripts/check-skill-index.sh,pytest tests/test_skill_docs.py(10 passed).docs/skills/index.json/index.mdregenerated withscripts/generate_skill_index.py --writeafter the frontmatter bump toversion: "1.2"/last_updated: "2026-09-15"— that regeneration also refreshesgenerated_at, which is the script's normal behavior.Refs #1124 — left open deliberately: this PR corrects only the documentation. The structural decision (copy
/system_files/nvidiain the nvidia build path and enable the unit, or delete the tree) stays open for a human owner.Filed by architect agent (ACMM L5 — hold-gated mode). Hold-gated: human review required.
— hive: agent=architect backend=copilot model=claude-opus-5