Repository navigation
Description
Direction
The owner requests that Utah and utah-packages be completely Hive-maintained. Routine work must flow through discovery → issue → repair → exact-head review → CI/acceptance → protected merge without repeated human branch updates, CI dispatches or merge clicks.
Conventional automation is already active: GitHub merged-by receipts show 13 Utah and 7 packages PRs merged by Hive since November 1. Native merge queues are optional, tracked separately in #1605, not a prerequisite for current Hive automation.
Concrete blockers and solution ownership
-
ci: emit real required checks for App-created buildroot refresh PRs — ci: emit real required checks for App-created buildroot refresh PRs utah-packages#874
-
ci: make extension-update proposals testable and Hive-mergeable without manual handling — ci: make extension-update proposals testable and Hive-mergeable without manual handling utah#1073
-
Hive policy: replace manual-only Utah workflow merges with an explicit automated review policy — Hive rollout: deploy the approved bounded automatic merge policy for Utah utah#1082
-
Hive capability: safely update Utah fork branches when rebases include workflow changes — Hive capability: safely update Utah fork branches when rebases include workflow changes #1611
-
Hive CI handoff: authorize exact-head fork Canary automatically after authenticated review — Hive CI handoff: authorize exact-head fork Canary automatically after authenticated review #1612
-
Hive repair lane: resolve Utah review findings instead of only refreshing branches — Hive repair lane: resolve Utah review findings instead of only refreshing branches #1613
-
Hive acceptance infrastructure: automate Utah boot and runtime evidence before landing system changes — Hive acceptance infrastructure: automate Utah boot and runtime evidence before landing system changes #1614
-
fix: daily bump source verification aborts on unavailable rtmpdump upstream — fix: daily bump source verification aborts on unavailable rtmpdump upstream utah-packages#875
-
m17n-lib import provenance corrected — fix: preserve m17n-lib import provenance and correct PR 861 scope utah-packages#876; Hive merged docs: reconcile m17n-lib provenance and acceptance tracking utah-packages#861. This is provenance reconciliation, not new package/runtime acceptance.
-
Hive readiness must account for missing native required checks, not only discovered check counts — Hive readiness: require actual branch-required checks before reporting ready for human merge #1619 (new report; maintainer triage required).
-
Weekly baseline proposals need a real required-CI/eligible-author handoff — ci: make weekly baseline proposals testable and Hive-mergeable without manual handoff utah#1081 (separate from extension updates; new report, maintainer triage required).
Existing issues reused rather than duplicated
- Strict-freshness daily-bump race: [reviewer] Review backlog (intent-alignment): No-queue path still cannot land a bump PR that falls BEHIND main under strict freshness utah-packages#864 — built exact head can become BEHIND and is intentionally not durably auto-merge armed; refresh must invalidate proof and rebuild rather than authorize unbuilt future heads.
- Source fetch anti-bot rejection: [ci-maintainer] Nightly source check fails because a download site now shows an anti-bot page utah-packages#843 — preserve content integrity and implement the reviewed source-handling repair.
- Main factory failures: Factory: packages failing on main utah-packages#872 — Hive merged fix: get six missing programs building again, including audio plugin libraries and smart-card support utah-packages#880; postmerge run https://github.com/projectbluefin/utah-packages/actions/runs/41427101449 successfully built the six named packages hermetically and completed publication/signing steps. Issue closure preceded that proof; build/publication evidence now exists. Exact manifest membership/NEVRAs and runtime acceptance were not independently inspected/proven by this review.
- Premature batch closure: [reviewer] Review backlog (intent-alignment): Tracking issue #490 already closed despite five outputs still pending utah-packages#868 — fix(ci): add bonedigger lifecycle workflow #490 closed while five outputs remain pending. Reconcile tracking against real outputs; this is also an issue-lifecycle automation gap.
- Metadata cleanup awaiting ordinary repair: Review backlog (intent-alignment): Per-package .packit.yaml upstream_project_url points at opencontainers, spec at rootless-containers utah-packages#835.
- Accepted workflow hardening blocked on Hive writer capability: [sec-check] Turn on the shared download-pinning check in the build workflow utah#1049.
- GNOME update/runtime acceptance: Refresh extension pins to upstream fixes without breaking GNOME 51 utah#993, Blur my Shell CPU/rendering complaint; update Utah to latest upstream fixes utah#992, GNOME Shell intermittently consumes a full CPU core; extension errors need attribution utah#997.
- ci: run a read-only Canary automatically on fork pull requests utah-packages#822: resolve conflict/review concerns and prove an actual read-only fork run; this feedback lane must not impersonate privileged Canary proof.
- Existing native review/runtime holds on fix: check that installed video decoders can load utah#919 / fix(selinux): move the policy store to /etc/selinux (re-apply #874, held for booted-update verification) utah#894 and feat: add ibus-anthy through ibus-typing-booster input-method recipes (#494) utah-packages#804 / feat: prepare better support for VMware virtual machines utah-packages#812 remain authoritative until fixed and supported by current evidence.
Completion contract
- Each recurring manual step above has a linked owning repair or explicit owner-only capability/policy prerequisite, not a generic needs-human parking label.
- Hive supplies real current-head/real-image checks; no fake success contexts, blanket fork privilege, blind hold removal, or source checksum acceptance.
- Review objections are resolved with evidence, not suppressed to clear merge state.
- Close tracking issues only for actual declared output/publication/runtime acceptance, not a partial recipe import.
- Run a recurring read-only upstream freshness audit to detect lag and route actionable updates to Hive; implementation is in progress in Utah (
just audit-upstreams). Discovery must report failed/unsupported checks rather than call them current. - Demonstrate representative dependency, workflow-pin, fork, generated-bot-PR and system/runtime changes reaching protected merge through Hive without routine operator intervention.
In-progress implementation
The active producer repairs are projectbluefin/utah-packages#878 and projectbluefin/utah#1078. Reuse these rather than opening competing PRs from the earlier prepared branches. Both need the existing authorization/evidence boundaries satisfied and positive real-proposal handoff proof before projectbluefin/utah-packages#874 / projectbluefin/utah#1073 can close.
The upstream audit is implemented/tested/pushed at projectbluefin/utah@main...feat/upstream-freshness-audit (d1029be), but no PR has been opened and it is not deployed. Repository-required permission to publish that PR remains outstanding; preserve the prepared work rather than rebuilding it in parallel. Its report distinguishes update/unknown/error and must not be called an exhaustive per-package freshness guarantee.
Common PRs #1616/#1617/#1618 are partial documentation, not deployed acceptance infrastructure, merge policy or completed repair loops. Their automatic closing references were changed to partial Refs so #1614/#1610/#1613 remain open. Owner-only capability/credential decisions and physical-only observations remain explicit; no approvals or hold releases are implied.
Utah policy rollout ownership correction
The former common#1610 moved to projectbluefin/utah#1082. The maintainer-delegated bounded pin-only policy decision is approved: projectbluefin/utah#1082 (comment). Implementation/deployment and safe-case proof remain open; do not direct common-image contributors to implement this external Hive control.
Common PR #1617 is now closed as a misrouted docs-only proposal (branch/diff retained). Do not treat it as covering the approved Utah rollout; deployment and live proof are still tracked at projectbluefin/utah#1082.
Activity
hanthor commentedon Nov 2, 2026
Prepared and verified concrete repairs (not yet merged/deployed):
just audit-upstreams, JSON/strict checking and explicit unknown coverage. Live local-checkout audit completed in 7.57s with 23 changed inputs, 11 current, 17 unknown and zero lookup errors; this was the user's older local checkout, not a claim against current main. Input hashes stayed unchanged. Current-main branch passes 1,297 host tests and full pre-commit.just checkpassed 1,273 tests and full pre-commit passed. Refs utah#1073.validatecontext as equivalent.just checkpassed 1,473 tests / 3,005 subtests; full pre-commit passed. Refs utah-packages#874.ujust --choosecrashes on Bluefin becausefzfisn't installed #861 was corrected by a normal fast-forward push to exact headeae97a9f(no force), preserving chore(deps): update docker/login-action digest to 06fb636 #856 import provenance and correcting title/body. Its required Canary, Unit tests and Runtime contract now pass; Hive still owns re-review/landing. Refs utah-packages#876.Owner-only policy/App grants/privileged fork handoff/runtime-runner prerequisites remain tracked by the linked common issues. No manual holds, required checks, source integrity checks or runtime acceptance criteria have been removed. New repair PR publication follows the repository's explicit authorization contract; branches/diffs are available for review.
kylerankin commentedon Nov 2, 2026
Summary: This issue asks for the two projects that build the Bluefin desktop operating system image — called Utah and utah-packages — to be maintained entirely by automation, so that a routine update can move from spotting a problem to fixing it, testing it and merging it without a person having to push branches, start the build or click merge again and again. Most of the remaining work is already finished or is being handled inside those two projects, but two things still need the project owner to make a decision before the automation can run on its own: a trusted, reviewed way to hand a finished build to the required tests, and a limited, logged way to update the test-workflow files in those two projects. Until those two decisions are made, the automation cannot run unattended, so the manual bottleneck this issue is trying to remove stays in place.
What I need from you: Approve the two owner decisions below (issues #1611 and #1612).
Status of each blocker listed in #1615
Common-side items (tracked as their own issues):
common. Outside this repo's checkout.ujust --choosecrashes on Bluefin becausefzfisn't installed #861 scope) — already corrected by a normal fast-forward to exact head; Hive owns re-review. In the utah-packages repo.Owner-prepared repairs (in the utah/utah-packages repos, verified but not yet merged by a maintainer):
Why the remaining work is parked on an owner decision, not a missing commit
The two items that block "fully Hive-maintained" are genuine security and access decisions that only the owner can make — they are not confirmation gates and there is no
common-repo change that resolves them:Both sit in the risk categories the dispatch rules name (security, credentials, owner-only infrastructure). They are already labelled stage/045-needs-decision and are the "Owner-only policy/App grants/privileged fork handoff/runtime-runner prerequisites" the owner said in the issue comment remain tracked by the linked common issues. No manual hold, required check, source-integrity check or runtime acceptance criterion has been removed; the automation simply cannot be authorized until the owner defines and grants it.
— hive: backend=pi model=lemonade/ornith-1.5-35b-a3b-gguf-q6_k
🐝 Hive Agent:
contributor| SHA:e3d4cbbhivecommons-hive commentedon Nov 2, 2026
Approved via
triage/accepted, added by @hanthor (admin collaborator).approved-directionis applied; no label Hive added before the acceptance remained to remove.Left in place:
stage/045-needs-decision(added by Hive after the acceptance; answer it with/hive approveor/hive decision <option>).This issue is not yet offered to agents while the labels above remain.
Removing
triage/acceptedlater will not stop Hive; adding a label containingholdto this issue, and to any pull request already opened for it, will.hanthor commentedon Nov 2, 2026
Actionable Hive handoff — current gaps are linked, not declared complete
New distinct repair reports:
Existing work now has concrete repair/deployment checklists:
I corrected the three docs-only PR bodies to partial Refs, preventing automatic closure of unfinished operational issues. The umbrella now distinguishes demonstrated projectbluefin/utah-packages#861 provenance and projectbluefin/utah-packages#880 factory build/publication progress from remaining runtime, source-health, trust, CI and deployment work. Prepared upstream-audit branch/publication status is also recorded.
Routing boundary: the two new reports carry kind/bug and needs-human, without self-acceptance. A maintainer must accept their implementation scope and remove needs-human before Hive may hand them out; these are routine bug scopes, not blanket permission for App grants or privileged fork execution. Existing accepted repair work remains on its current issues/PRs. No new merge gates, synthetic checks, approvals or hold releases were introduced.
hivecommons-hive commentedon Nov 13, 2026
The reason this issue is parked may be out of date. It has been parked for a maintainer (
stage/045-needs-decision) since 2026-11-02, and since then:The park reason was written before these changes. Re-read it against the current state before deciding. This note does not un-park the issue: it stays with a maintainer, and Hive updates this note if more of the referenced work moves.