Skip to content

parity: track Bluefin's effective package payload #11

Closed

Description

@hanthor

This was generated by AI during triage.

What to build

Type: AFK

Replace the disconnected manifest comparison with a machine-readable contract derived from the package transaction that current Bluefin actually executes. Utah should either install each effective requirement or carry a documented, issue-linked exception.

Acceptance criteria

  • The parity source covers Bluefin's effective base, version-specific, external, and multimedia transactions.
  • CI detects additions/removals in the effective Bluefin payload rather than only changes to an unused manifest.
  • Every Utah exception has rationale and a tracking issue.
  • The resulting image records and verifies the exact resolved contract.

Blocked by

None - can start immediately

Activity

  1. mrbobbytables commented on Sep 22, 2026

    @mrbobbytables
    Contributor

    This issue's goal is covered by open PR #117 (feat(parity): compare the built image with Bluefin's image, not list with list), which superseded the manifest-parsing approach in PR #60 by comparing Utah's built image against Bluefin's rechunked inventory (dev.hhd.rechunk.info). PR #117 is currently open and undergoing maintainer review (@hanthor and @castrojo) with pending design decisions around baseline management.

    When PR #117 is merged, note that a maintainer editing the PR body to link/close this issue can resolve it.

    — hive: backend=copilot model=gemini-3.8-flash

    🐝 Hive Agent: contributor | SHA: unknown

  2. hanthor commented on Oct 3, 2026

    @hanthor
    MemberAuthor

    Closing: the acceptance criteria are met on main, though not through #117 (closed unmerged):

    • Effective payload as the parity source: baselines/bluefin/rpms.tsv and surface.tsv are measured from the published ghcr.io/ublue-os/bluefin:stable image (scripts/image-baseline.py, feat(baselines): measure Utah against the published Bluefin and Dakota images #264). That covers the base, version-specific, external and multimedia transactions, not just base.toml.
    • CI notices payload changes: .github/workflows/image-baselines.yml re-measures every week and opens a PR. just check fails that PR if any new gap has no entry in baselines/triage.toml.
    • Every exception has a rationale and an issue: baselines/triage.toml covers image gaps, and [unavailable] in packages/utah.toml requires a tracking issue for each entry, enforced by feat(contract): fail CI on stale [unavailable] entries #418.
    • Resolved contract recorded in the image: scripts/verify-rpm-contract.py writes /usr/share/utah/package-origins.{json,txt}.

    If part of this is still missing, please reopen and name the criterion.

    Evidence: 46bc45d (#264) baselines/ + scripts/image-baseline.py; .github/workflows/image-baselines.yml weekly re-measure PR; just check fails on untriaged gap (baselines/README.md); 2aeacba (#417) scripts/audit-bluefin-parity.py; scripts/verify-rpm-contract.py generate_provenance_report -> package-origins.json

    Closed in a backlog sweep after verifying against current main; reopen if this is still reproducible.

    🤖 Generated with Claude Code

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions