You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: describe Utah's current architecture, parity, and installer status #23
Bring user and contributor documentation in line with the implemented Hummingbird-only package model, current factory closure, Utah identity, installer/offline payload, four deferred packages, and the distinction between local implementation and publicly shipped artifacts.
Acceptance criteria
README no longer claims the installer/offline payload is unimplemented.
Package counts and all deferred packages match machine-readable manifests.
Documentation does not describe Fedora or Rawhide as a Utah runtime package source.
Public image/ISO availability is stated separately from local implementation status.
Build, test, rollback, and artifact verification instructions reflect the adopted Dakota-style gates.
Running python3 scripts/check-doc-counts.py today confirms the documented counts are current: 57 Bluefin contract / 49 Utah additions / 10 genuinely unavailable, matching packages/bluefin.toml and packages/utah.toml.
README.md's opening banner and "Known gaps" section state the installer and offline payload are implemented (not a future milestone), while separately noting nothing is published to a registry or released as an ISO — satisfying the local-vs-public distinction.
No documentation describes Fedora or Rawhide as a Utah runtime package source; the only Fedora/Rawhide mentions are contextual (builder-only toolchain, or explaining why a package is unavailable).
docs/building.md's "Validate the release-readiness gates" section (added by docs: close README/skill package-count drift against the manifests #225) documents the adopted Dakota-style gates: just iso, boot-iso, luks-test, try-installed, check-desktop-contract, check-repos, plus rollback/uupd policy pointers.
Two later attempts to re-do this same work (PR #142, PR #63) were both closed by a maintainer as superseded/stale once #225 and related PRs (#143 Secure Boot docs, #253 grub2 tracking) landed on main.
I'm not opening a new PR since there is nothing left to change against the stated acceptance criteria.
Closing as completed: resolved by PR #225 ("docs: close README/skill package-count drift against the manifests"), aligning manifest package counts and adding scripts/check-doc-counts.py as an automated drift gate.
Activity
docs: close README/skill package-count drift against the manifests
docs: close README/skill package-count drift against the manifests (#225
buggtb commentedon Sep 25, 2026
Verified against current main (upstream/main @ 369e3f2): all five acceptance criteria in this issue are already satisfied.
scripts/check-doc-counts.pyas a permanent drift gate wired intojust check.python3 scripts/check-doc-counts.pytoday confirms the documented counts are current: 57 Bluefin contract / 49 Utah additions / 10 genuinely unavailable, matchingpackages/bluefin.tomlandpackages/utah.toml.docs/building.md's "Validate the release-readiness gates" section (added by docs: close README/skill package-count drift against the manifests #225) documents the adopted Dakota-style gates:just iso,boot-iso,luks-test,try-installed,check-desktop-contract,check-repos, plus rollback/uupdpolicy pointers.Two later attempts to re-do this same work (PR #142, PR #63) were both closed by a maintainer as superseded/stale once #225 and related PRs (#143 Secure Boot docs, #253 grub2 tracking) landed on main.
I'm not opening a new PR since there is nothing left to change against the stated acceptance criteria.
— hive: backend=pi model=pi-claude-code-provider/sonnet
🐝 Hive Agent:
contributor| SHA:b01bacfcastrojo commentedon Sep 26, 2026
Closing as completed: resolved by PR #225 ("docs: close README/skill package-count drift against the manifests"), aligning manifest package counts and adding
scripts/check-doc-counts.pyas an automated drift gate.