Skip to content

Make Utah and utah-packages fully Hive-maintained: remove recurring manual PR bottlenecks #1615

Open

Description

@hanthor

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

Existing issues reused rather than duplicated

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

  1. added
    needs-kindA maintainer must classify this issue; the intake source did not establish its kind.
    on Nov 2, 2026
  2. removed
    needs-kindA maintainer must classify this issue; the intake source did not establish its kind.
    on Nov 2, 2026
  3. hanthor commented on Nov 2, 2026

    @hanthor
    MemberAuthor

    Prepared and verified concrete repairs (not yet merged/deployed):

    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.

  4. kylerankin commented on Nov 2, 2026

    @kylerankin
    Contributor

    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):

    Owner-prepared repairs (in the utah/utah-packages repos, verified but not yet merged by a maintainer):

    • utah-packages#874 — fix/bot-pr-required-check-handoff (App proposals start real required workflows).
    • utah#1073 — fix/extension-pr-required-check-handoff (main-only App PR creation).
    • These are forks/branches; a maintainer publishes and merges them.

    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: e3d4cbb

  5. added
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    on Nov 2, 2026
  6. hivecommons-hive commented on Nov 2, 2026

    @hivecommons-hive
    Contributor

    Approved via triage/accepted, added by @hanthor (admin collaborator). approved-direction is 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 approve or /hive decision <option>).

    This issue is not yet offered to agents while the labels above remain.

    Removing triage/accepted later will not stop Hive; adding a label containing hold to this issue, and to any pull request already opened for it, will.

  7. hanthor commented on Nov 2, 2026

    @hanthor
    MemberAuthor

    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.

  8. hivecommons-hive commented on Nov 13, 2026

    @hivecommons-hive
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    approved-directionkind/featureA new capability.stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it uptriage/acceptedScope accepted; ready for work. Use `/triage accepted`.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions