Skip to content

feat(dev-tools): add encrypted cloud files and package-signing keys - #838

Merged
hanthor merged 18 commits into
projectbluefin:mainfrom
mrbobbytables:hive/issue-485-remaining
Nov 1, 2026
Merged

hanthor merged 18 commits into
projectbluefin:mainfrom
mrbobbytables:hive/issue-485-remaining

Conversation

@mrbobbytables

@mrbobbytables mrbobbytables commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Summary: Bluefin’s software package builder is missing a tool for encrypted cloud files and a collection of keys used to verify software packages. This change adds recipes for both, along with the support packages needed to build the encrypted-file tool. It helps the builder offer a more complete set of developer tools.

What I need from you: Review the recipes; keep this batch open until hosted builds, publication, and runtime checks are complete.


Changes

  • Add CryFS for encrypted cloud files and distribution-gpg-keys for distribution package-signing keys.
  • Add Crypto++, range-v3, and Python versioneer, which CryFS needs to build.
  • Lock sources and verify checksums; verify the Crypto++ release signature and generate the distribution-gpg-keys archive reproducibly from a pinned upstream commit.
  • Register the packages with Packit and update architecture counts, provenance guidance, and the factory build backlog.

Validation

  • just check and just test passed (1,407 tests; 2 skipped in each run).
  • All five source-pipeline checks passed; the four direct-source Fedora lookaside fallback hashes matched. CryFS patches were checked against its pinned source archive.
  • Package builds, publication, runtime dependency solving, and runtime proof are not included in this recipe-import batch and remain outstanding.

Refs #485 — recipe imports are done; hosted builds, publication, dependency solving, and runtime proof remain.


🐝 Hive Agent: contributor | SHA: 22a88dcc

— hive: backend=copilot model=claude-fable-5.1

mrbobbytables added a commit to mrbobbytables/utah-packages that referenced this pull request Oct 31, 2026
Record pull request projectbluefin#838 for the CryFS and distribution-gpg-keys recipe imports.

Hive-Run: projectbluefin#485
Hive-Plan: issue-485-remaining-dev-tools
Hive-Spec: issue-485#dev-tools-parity
Assisted-by: Auto mode via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

stage 080-awaiting-merge-admission: no activity for 30m0s: merge-train:queued-behind#819:6/8:0/0:.packit.yaml,factory-build-backlog.toml,upstream-sources.json,architecture.md,+4

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary: This change adds build recipes for an encrypted-cloud-storage tool, a set of Linux distribution signing keys, and three helper libraries the first tool needs. I checked the recipes against the Fedora originals they were copied from, confirmed the pinned sources and signatures match what upstream publishes, and ran the repository's own validators. Everything holds up; the only note is one helper recipe drops a small optional piece from the Fedora original for a reason that turns out not to apply, so it could simply be kept identical to Fedora.


Reviewed at head 7c17d43c. Verified: tools/validate.py (675 recipes), tools/factory_contract.py, tools/factory_build_backlog.py --check, targeted tests/test_generated_sources.py all pass; tag distribution-gpg-keys-1.123-1 resolves to the pinned commit 6f5f4883; all three cryfs patches git apply --check cleanly against the pinned 0.11.3 archive; the tracked cryptopp public key's SHA-512 equals the one Fedora's dist-git sources records, and both lookaside URLs the pipeline will hit (.sig, .gpg) return 200.

style (low, advisory)

packages/python-versioneer/python-versioneer.spec:26-32 drops Fedora's %pyproject_extras_subpkg -n python3-versioneer toml and the -x toml flag, with the comment that the extra "requires python3-toml, which is not available in the factory buildroot". That is not what the extra needs: versioneer 0.29's pyproject.toml declares toml = ["tomli; python_version < '3.11'"], so on the Python 3.15 buildroot this spec already targets (changelog 0.29-9) the extra resolves to nothing. The deviation buys nothing, drops the python3-versioneer+toml provide Fedora ships, and leaves a misleading comment. Suggest restoring the Fedora lines so the recipe stays byte-identical to its source:

--- a/packages/python-versioneer/python-versioneer.spec
+++ b/packages/python-versioneer/python-versioneer.spec
@@
 %description -n python3-versioneer %_description
 
-# CryFS needs versioneer itself; its optional TOML extra requires python3-toml,
-# which is not available in the factory buildroot.
+%pyproject_extras_subpkg -n python3-versioneer toml
+
 %prep
 %autosetup -n versioneer-%{version}
 
 %generate_buildrequires
-%pyproject_buildrequires
+%pyproject_buildrequires -x toml

No findings from: correctness, security, intent-alignment, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@mrbobbytables

Copy link
Copy Markdown
Contributor Author

Restored Fedora's toml extra subpackage and -x toml build-requires handling; this keeps the optional extra metadata without requiring python3-toml on supported Python versions. just check and just test pass: 1,407 passed, 2 skipped.


🐝 Hive Agent: contributor | SHA: unknown

@mrbobbytables

Copy link
Copy Markdown
Contributor Author

CI note: Unit tests and all other validation jobs pass. The Canary check fails because this fork head has no successful maintainer-run Canary proof; its workflow explicitly requires a maintainer to run the fork Canary, which I cannot trigger as the contributor.


🐝 Hive Agent: contributor | SHA: unknown

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (2 waiting): fixes are handed out before new work as soon as you have capacity.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

stage 080-awaiting-merge-admission → 072-returned-to-contributor: conflicting

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables the hive has adopted this PR (stage/074-adopted-by-hive): your hive has been offline since the nudge. The hive will rebase this branch on main here; your commits and sign-off stay. Push a new head yourself at any time and the hive yields it back to you.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed — no findings from correctness, security, intent-alignment, style, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive
hivecommons-hive Bot force-pushed the hive/issue-485-remaining branch from 20c40f9 to ec0f19c Compare October 31, 2026 15:07
hivecommons-hive Bot pushed a commit to mrbobbytables/utah-packages that referenced this pull request Oct 31, 2026
Record pull request projectbluefin#838 for the CryFS and distribution-gpg-keys recipe imports.

Hive-Run: projectbluefin#485
Hive-Plan: issue-485-remaining-dev-tools
Hive-Spec: issue-485#dev-tools-parity
Assisted-by: Auto mode via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

Rebased onto current main to clear the merge conflict (resolved upstream-sources.json by union, regenerated factory-build backlog report and architecture counts with the repo tools). Original authorship preserved.

The Canary check needs a maintainer to run the "Canary for a fork pull request" workflow for this head.

hive/awaiting-ci: CI pending — sweep will merge when green.


🐝 Hive Agent: scanner | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: 74a1ebe00051a45c647c2a3f32dae84814e1796b

— hive: agent=scanner backend=copilot model=claude-opus-5.5 copilot=1.0.88

@hivecommons-hive

Copy link
Copy Markdown
Contributor

stage 080-awaiting-merge-admission → 074-adopted-by-hive: base-branch-red:Factory build backlog

@hivecommons-hive

Copy link
Copy Markdown
Contributor

stage 080-awaiting-merge-admission: no activity for 30m0s: merge-train:queued-behind#652:3/5:0/0:.packit.yaml,factory-build-backlog.toml,upstream-sources.json,architecture.md,+2

mrbobbytables and others added 3 commits October 31, 2026 16:40
Add recipes for CryFS, distribution-gpg-keys, and the packages CryFS needs to build.

Hive-Run: projectbluefin#485
Hive-Plan: issue-485-remaining-dev-tools
Hive-Spec: issue-485#dev-tools-parity
Assisted-by: Auto mode via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
Record pull request projectbluefin#838 for the CryFS and distribution-gpg-keys recipe imports.

Hive-Run: projectbluefin#485
Hive-Plan: issue-485-remaining-dev-tools
Hive-Spec: issue-485#dev-tools-parity
Assisted-by: Auto mode via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
Assisted-by: Auto mode via GitHub Copilot

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
@mrbobbytables
mrbobbytables force-pushed the hive/issue-485-remaining branch from ec0f19c to 45483cd Compare October 31, 2026 16:40
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR has a new head without confirmed hive push evidence, so the hive has handed this PR back to you (stage/074-adopted-by-hive → stage/072-returned-to-contributor). It will nudge again if CI stays red.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed — no findings from correctness, security, intent-alignment, style, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

Refresh architecture and backlog state from the current inventory. Add one inventory regeneration command, repair invalid imported YAML whitespace, and preserve workflow output values with grouped redirection.

Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: James Reilly <jreilly1821@gmail.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

  • Canary

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Your relay session received this as a fix-pr task and launched a parallel fix session; your current work continues.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

stage 080-awaiting-merge-admission → 072-returned-to-contributor: required-check-failing:Canary

Distinguish inventory-only recipe imports from source-generator changes that require maintainer-reviewed Canary proof. Preserve the privileged review boundary when a repair request names this expected failure.

Assisted-by: Auto mode via GitHub Copilot

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
@mrbobbytables

Copy link
Copy Markdown
Contributor Author

The returned Canary failure is a maintainer-review prerequisite, not a package build failure: run 41220933599 skipped all build passes and failed in Decide because this fork head had no maintainer-run Canary proof. The PR adds distribution-gpg-keys source-generation support in tools/generated_sources.py, so the inventory-only exception does not apply.

Pushed signed follow-up 11ab14fc854bdcd4091cee9ecdef5d23711bb154 to the existing branch, correcting contradictory lane-validation guidance. just check and just test passed. The existing sign-off is preserved: Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>.

Blocked on maintainer review and dispatch, not an author-side code repair. After reviewing the final head, a maintainer must run Canary for a fork pull request (canary-fork-pr.yml) with pr=838 and head_sha=11ab14fc854bdcd4091cee9ecdef5d23711bb154. The privileged gate and required generator support remain intact; no approval was fabricated and no privileged workflow was dispatched by this fix session.


🐝 Hive Agent: contributor | SHA: 11ab14f

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

  • Canary

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Your relay session received this as a fix-pr task and launched a parallel fix session; your current work continues.

@mrbobbytables

Copy link
Copy Markdown
Contributor Author

Rechecked the returned head 11ab14fc854bdcd4091cee9ecdef5d23711bb154: Canary run https://github.com/projectbluefin/utah-packages/actions/runs/41224637731 fails only in Decide because there is no successful maintainer-run proof for this exact fork head. All build passes were skipped. The proof API returns no completed dispatch runs for this SHA, and there is no maintainer approval recorded for this head.

This is blocked on maintainer review/dispatch, not an author-side code defect. The existing source-generator change legitimately requires Canary. A maintainer must review this head and run canary-fork-pr.yml with pr=838 and head_sha=11ab14fc854bdcd4091cee9ecdef5d23711bb154. Please route this prerequisite to a maintainer rather than returning it repeatedly as a contributor repair.

No new commit or push was made: changing the head cannot supply the missing proof, and the relevant guidance was already corrected in the previous signed follow-up. The privileged gate and required generator support remain unchanged.


🐝 Hive Agent: contributor | SHA: 11ab14f

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

  • Canary

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Your relay session received this as a fix-pr task and launched a parallel fix session; your current work continues.

@mrbobbytables

Copy link
Copy Markdown
Contributor Author

Canary repair triage: the failing check on 13078eac2eaa417d369edb3d605d6e571283d54e is missing maintainer-reviewed fork proof, not a package-build failure. All configuration checks passed; the build jobs were skipped. Failure log: https://github.com/projectbluefin/utah-packages/actions/runs/41231266398/job/124625854009

Maintainer action requested: review this exact head, manually copy the reviewed commit into an upstream branch, and run Canary with the repository publication permissions. The automatic canary-fork-pr.yml copy refuses this PR because it changes .github/workflows/rebuild-rpms.yml; tools/generated_sources.py also requires pipeline proof. Preserve the gate and source registration. Please use the documented canary/pr-838 proof branch so the successful dispatch can satisfy the fork check, and refresh the PR check afterward.

Per the requester’s decision, this repair session stops here without adding a commit or pushing a new head: that would not supply the missing review and would invalidate any proof for this SHA. Recipe-scoped builds and runtime acceptance remain separate from the default pipeline Canary.


🐝 Hive Agent: contributor | SHA: 13078ea

Drop the style-only grouped GITHUB_OUTPUT edit carried in from the interim baseline branch; main intentionally kept the original workflow so recipe PRs do not touch pipeline paths.

Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: James Reilly <jreilly1821@gmail.com>
@hanthor

hanthor commented Oct 31, 2026

Copy link
Copy Markdown
Member

Follow-up df14a8a7bb2714d4c77f6328035c9abba64831bc: restored .github/workflows/rebuild-rpms.yml to match main. My earlier sync carried a style-only edit from an interim baseline revision; this PR no longer touches workflow files. just check passes.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

  • Canary

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (0 waiting): fixes are handed out before new work as soon as you have capacity.

mrbobbytables and others added 2 commits October 31, 2026 19:29
Assisted-by: Auto mode via GitHub Copilot

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (0 waiting): fixes are handed out before new work as soon as you have capacity.

Assisted-by: Auto mode via GitHub Copilot

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Review asks:

  • the branch conflicts with the base and needs a rebase

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (1 waiting): fixes are handed out before new work as soon as you have capacity.

Assisted-by: Auto mode via GitHub Copilot

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

  • Canary

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (1 waiting): fixes are handed out before new work as soon as you have capacity.

@mrbobbytables

Copy link
Copy Markdown
Contributor Author

hive-base-moved: merged projectbluefin/utah-packages main at 85df87e. Regenerated the architecture counts and backlog snapshot; just check and just test pass.


🐝 Hive Agent: contributor | SHA: 347b753

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Needs a decision, not a merge: check Canary refuses pull requests from a fork, so neither the author nor the hive can turn it green: a maintainer must push this branch to the repository (or approve the run as the repository requires).

Head: verdict pending @602a184, 20/21 checks green, red: Canary, soak 0s of 30m0s.

Clear the cause and the hive re-evaluates on its next pass; the stage moves to stage/090-ready-for-human-merge, stage/095-pre-merge-soak or the merge queue on its own. An approval does not bypass CI, hold labels or other merge gates.

Merge current main and regenerate derived inventory with just regenerate-inventory.

Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: James Reilly <jreilly1821@gmail.com>
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

  • Canary

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (2 waiting): fixes are handed out before new work as soon as you have capacity.

@github-actions

Copy link
Copy Markdown
Contributor

Canary was run on this pull request at 48880ecc8b4f115178ccbd8fcc0331f8f9efc3cc by @hanthor after review, from the in-repository copy canary/pr-838: https://github.com/projectbluefin/utah-packages/actions/workflows/canary.yml?query=branch%3Acanary%2Fpr-838. When that run passes, this pull request's own Canary check is re-run and turns green by itself. A new push to the pull request needs a new review and a new run.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Needs a decision, not a merge: check Canary refuses pull requests from a fork, so neither the author nor the hive can turn it green: a maintainer must push this branch to the repository (or approve the run as the repository requires).

Head: verdict pending @48880ec, 20/23 checks green, red: Canary, soak 0s of 30m0s.

Clear the cause and the hive re-evaluates on its next pass; the stage moves to stage/090-ready-for-human-merge, stage/095-pre-merge-soak or the merge queue on its own. An approval does not bypass CI, hold labels or other merge gates.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

stage 080-awaiting-merge-admission → 072-returned-to-contributor: conflicting

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables the hive has adopted this PR (stage/074-adopted-by-hive): the review asks stayed open (the branch conflicts with the base and needs a rebase) for 2h after the nudge and the relay nudge went unanswered. The hive will rebase this branch on main here; your commits and sign-off stay. Push a new head yourself at any time and the hive yields it back to you.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed — no findings from correctness, security, intent-alignment, style, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

hanthor and others added 3 commits October 31, 2026 23:02
Preserve all five cryfs-family source locks and both generator/source-location proof requirements while removing obsolete committed counts.

Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: James Reilly <jreilly1821@gmail.com>
Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions

Copy link
Copy Markdown
Contributor

Canary was run on this pull request at eef95fec994d951faa4e5c29eff6c355347cc525 by @hanthor after review, from the in-repository copy canary/pr-838: https://github.com/projectbluefin/utah-packages/actions/workflows/canary.yml?query=branch%3Acanary%2Fpr-838. When that run passes, this pull request's own Canary check is re-run and turns green by itself. A new push to the pull request needs a new review and a new run.

@hanthor
hanthor enabled auto-merge (squash) October 31, 2026 23:44
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR has a new head without confirmed hive push evidence, so the hive has handed this PR back to you (stage/074-adopted-by-hive → stage/072-returned-to-contributor). It will nudge again if CI stays red.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@mrbobbytables this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

  • Canary

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (0 waiting): fixes are handed out before new work as soon as you have capacity.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Needs a decision, not a merge: check Canary refuses pull requests from a fork, so neither the author nor the hive can turn it green: a maintainer must push this branch to the repository (or approve the run as the repository requires).

Head: verdict pending @eef95fe, 29/33 checks green, red: Canary, soak 0s of 30m0s.

Clear the cause and the hive re-evaluates on its next pass; the stage moves to stage/090-ready-for-human-merge, stage/095-pre-merge-soak or the merge queue on its own. An approval does not bypass CI, hold labels or other merge gates.

@hanthor
hanthor merged commit 1faf915 into projectbluefin:main Nov 1, 2026
195 of 197 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants