Skip to content

feat: add the prefix name shifter to the long-tail backlog (#505) - #819

Merged
hanthor merged 15 commits into
projectbluefin:mainfrom
kylerankin:parity-505-long-tail
Nov 1, 2026
Merged

hanthor merged 15 commits into
projectbluefin:mainfrom
kylerankin:parity-505-long-tail

Conversation

@kylerankin

@kylerankin kylerankin commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Refs #505

Import the prefixdevname Rust crate (the prefix-name shifter) into the
long-tail backlog parity set.

  • Add packages/prefixdevname/: spec, source lock, Packit entry and the
    Hummingbird upstream metadata. Upstream publishes no release asset, so the
    source lock pins prefixdevname-0.2.0-vendored.tar.xz, produced by
    tools/generated_sources.py from the sha512-pinned GitHub tag v0.2.0
    archive plus every Cargo.lock crate vendored as cargo vendor --versioned-dirs lays it out (with tests for the generator).
  • Move prefixdevname from the long-tail backlog area to [resolved] and
    regenerate the backlog report (audit set and audit_names_sha256 are
    unchanged).
  • Refresh the architecture counts in docs/architecture.md.

No hosted build, publication or runtime closure is claimed.

Hive-Run: #505
Hive-Plan: issue-505 implementation step 3 (prefixdevname source family)
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com


🐝 Hive Agent: contributor | SHA: 719ac78f

kylerankin pushed a commit to kylerankin/utah-packages that referenced this pull request Oct 29, 2026
…uefin#819)

* feat: add the prefixdevname tool that shifts Windows-style prefix names

Import the prefixdevname Rust crate from the GitHub tag v0.2.0 archive,
unmodified, and lock that archive sha512 since upstream publishes no
release asset. Register the build in Packit, refresh the source-lock and
the architecture counts, and move prefixdevname from the long-tail
backlog area to [resolved] and regenerate the backlog report. No hosted
build, publication or runtime closure is claimed.

Refs projectbluefin#505

Hive-Run: projectbluefin#505
Hive-Plan: issue-505 implementation step 3 (prefixdevname source family)
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>

* docs: link the prefixdevname closing record to its pull request

Fill in the pr field on the prefixdevname [resolved] record now that the
import PR has a number.

Refs projectbluefin#505

Hive-Run: projectbluefin#505
Hive-Plan: issue-505 implementation step 5 (closing record)
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>
@kylerankin
kylerankin force-pushed the parity-505-long-tail branch from 719ac78 to 28d1257 Compare October 29, 2026 23:28
@hivecommons-hive hivecommons-hive Bot added author/clanker A contributor's own hive authored this PR under their login dco All commits are DCO signed-off stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act labels Oct 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@kylerankin 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.

kylerankin pushed a commit to kylerankin/utah-packages that referenced this pull request Oct 29, 2026
…uefin#819)

* feat: add the prefixdevname tool that shifts Windows-style prefix names

Import the prefixdevname Rust crate from the GitHub tag v0.2.0 archive,
unmodified, and lock that archive sha512 since upstream publishes no
release asset. Register the build in Packit, refresh the source-lock and
the architecture counts, and move prefixdevname from the long-tail
backlog area to [resolved] and regenerate the backlog report. No hosted
build, publication or runtime closure is claimed.

Refs projectbluefin#505

Hive-Run: projectbluefin#505
Hive-Plan: issue-505 implementation step 3 (prefixdevname source family)
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>

* docs: link the prefixdevname closing record to its pull request

Fill in the pr field on the prefixdevname [resolved] record now that the
import PR has a number.

Refs projectbluefin#505

Hive-Run: projectbluefin#505
Hive-Plan: issue-505 implementation step 5 (closing record)
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>
@kylerankin
kylerankin force-pushed the parity-505-long-tail branch from 28d1257 to dfdcbc6 Compare October 29, 2026 23:37
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@kylerankin 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.

@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 a small network-card naming helper to the package set, with a fully pinned and reproducible source bundle (I regenerated it and the checksum matches exactly). The source bundle and bookkeeping are fine, but the build recipe itself cannot succeed as written: three of its four install commands use a form that fails outright, and every file would land in the wrong directory, so the system's device manager would never see the rule or find the helper. Both problems have a two-line fix below.

What I need from you: Apply the suggested %install/%files fix.


correctness

  1. %install fails: install -D with a trailing-slash destination is "Not a directory" — packages/prefixdevname/prefixdevname.spec:34-36. GNU coreutils install -D src dir/ treats dir/ as the final file path and aborts (install: cannot create regular file '…/rules.d/': Not a directory, reproduced with coreutils 9.7). Line 33 (the binary) is the only one that names the destination file. The spec will never reach %files.

  2. %{_libdir} puts udev/dracut files under /usr/lib64, where nothing reads them — packages/prefixdevname/prefixdevname.spec:33-36,42-47. udev reads /usr/lib/udev/rules.d, dracut reads /usr/lib/dracut/modules.d, and the upstream rule itself hardcodes PROGRAM="/usr/lib/udev/prefixdevname" (rules/71-prefixdevname.rules in the v0.2.0 tag). Upstream's Makefile install and redhat/prefixdevname.spec:37-42 both use /usr/lib (%{_prefix}/lib). The repo's other udev packagers use %{_udevrulesdir}/%{_prefix}/lib/udev (e.g. packages/bolt/bolt.spec:73, packages/alsa-utils/alsa-utils.spec:131). Both issues fixed together:

 %install
-install -D -m 0755 target/release/prefixdevname %{buildroot}%{_libdir}/udev/prefixdevname
-install -D -m 0644 rules/71-prefixdevname.rules %{buildroot}%{_libdir}/udev/rules.d/
-install -D -m 0755 dracut/71prefixdevname/module-setup.sh %{buildroot}%{_libdir}/dracut/modules.d/71%{name}/
-install -D -m 0755 dracut/71prefixdevname-tools/module-setup.sh %{buildroot}%{_libdir}/dracut/modules.d/71%{name}-tools/
+install -D -p -m 0755 target/release/prefixdevname %{buildroot}%{_udevdir}/prefixdevname
+install -D -p -m 0644 rules/71-prefixdevname.rules %{buildroot}%{_udevrulesdir}/71-prefixdevname.rules
+install -D -p -m 0755 dracut/71prefixdevname/module-setup.sh %{buildroot}%{_prefix}/lib/dracut/modules.d/71%{name}/module-setup.sh
+install -D -p -m 0755 dracut/71prefixdevname-tools/module-setup.sh %{buildroot}%{_prefix}/lib/dracut/modules.d/71%{name}-tools/module-setup.sh

 %files
 %license LICENSE
 %doc README.md
-%{_libdir}/udev/prefixdevname
-%{_libdir}/udev/rules.d/71-prefixdevname.rules
-%dir %{_libdir}/dracut/modules.d/71%{name}
-%{_libdir}/dracut/modules.d/71%{name}/*
-%dir %{_libdir}/dracut/modules.d/71%{name}-tools
-%{_libdir}/dracut/modules.d/71%{name}-tools/*
+%{_udevdir}/prefixdevname
+%{_udevrulesdir}/71-prefixdevname.rules
+%dir %{_prefix}/lib/dracut/modules.d/71%{name}
+%{_prefix}/lib/dracut/modules.d/71%{name}/*
+%dir %{_prefix}/lib/dracut/modules.d/71%{name}-tools
+%{_prefix}/lib/dracut/modules.d/71%{name}-tools/*

(%{_udevdir}/%{_udevrulesdir} come from systemd-rpm-macros, pulled in by the existing BuildRequires: systemd-devel.)

Verified clean: tools/generated_sources.py:980-1065 mirrors _pydantic_core_* (lines 760-825); regenerating prefixdevname-0.2.0-vendored.tar.xz from the pinned tag archive reproduces sha512 223679b0… exactly as locked in packages/prefixdevname/sources:1 and config/upstream-sources.json; tests/test_generated_sources*.py, test_architecture_counts.py, test_factory_build_backlog.py (125 passed), tools/factory_build_backlog.py --check and tools/validate.py (651 / 645 rawhide / 6 upstream) all agree with the diff.

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

Confidence: 1/5 (needs attention) — 2 high findings

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

kylerankin pushed a commit to kylerankin/utah-packages that referenced this pull request Oct 29, 2026
…uefin#819)

* feat: add the prefixdevname tool that shifts Windows-style prefix names

Import the prefixdevname Rust crate from the GitHub tag v0.2.0 archive,
unmodified, and lock that archive sha512 since upstream publishes no
release asset. Register the build in Packit, refresh the source-lock and
the architecture counts, and move prefixdevname from the long-tail
backlog area to [resolved] and regenerate the backlog report. No hosted
build, publication or runtime closure is claimed.

Refs projectbluefin#505

Hive-Run: projectbluefin#505
Hive-Plan: issue-505 implementation step 3 (prefixdevname source family)
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>

* docs: link the prefixdevname closing record to its pull request

Fill in the pr field on the prefixdevname [resolved] record now that the
import PR has a number.

Refs projectbluefin#505

Hive-Run: projectbluefin#505
Hive-Plan: issue-505 implementation step 5 (closing record)
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>
@kylerankin
kylerankin force-pushed the parity-505-long-tail branch from dfdcbc6 to 57b8755 Compare October 29, 2026 23:53
@hivecommons-hive hivecommons-hive Bot added the role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) label Oct 29, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@kylerankin 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.

@hivecommons-hive hivecommons-hive Bot added stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue and removed stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act labels Oct 30, 2026
@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 @57b8755, 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.

@hivecommons-hive hivecommons-hive Bot added stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act and removed stage/085-needs-decision A human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue labels Oct 30, 2026

@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 a small network-card naming helper to the package set and, since the last review, now builds a reproducible source bundle that includes all of its Rust dependencies. The bundle and its checksum verify correctly, but the two problems from the previous review are still there: the recipe's install step uses a command form that fails outright, and it places files under a directory where the system never looks for them. The package still cannot build or work as written.

What I need from you: Fix the two install issues in the spec (patch below).


Re-review of delta dfdcbc6…57b8755. New generator verified: running tools/generated_sources.py prefixdevname reproduced the locked sha512 223679b0…c13f1 byte-for-byte (config/upstream-sources.json:3089, packages/prefixdevname/sources:1).

correctness

  1. Still present (high) — packages/prefixdevname/prefixdevname.spec:33-35: install -D … <file> …/dir/ with a trailing-slash destination. GNU install treats it as the destination file; reproduced with coreutils 9.7: install: cannot create regular file '…/rules.d/': Not a directory. %install aborts before %files.

  2. Still present (high) — prefixdevname.spec:32-35,40-45 install under %{_libdir} (/usr/lib64 on x86_64/aarch64). udev reads /usr/lib/udev/rules.d, dracut reads /usr/lib/dracut/modules.d, and upstream's own rule (rules/71-prefixdevname.rules:9) and dracut module (dracut/71prefixdevname-tools/module-setup.sh, inst /usr/lib/udev/prefixdevname) hardcode /usr/lib/udev/prefixdevname; upstream Makefile:19-25 installs to /usr/lib. Sibling specs use %{_udevrulesdir} (packages/bolt/bolt.spec:73).

    Fix for both:

     %install
    -install -D -m 0755 target/release/prefixdevname %{buildroot}%{_libdir}/udev/prefixdevname
    -install -D -m 0644 rules/71-prefixdevname.rules %{buildroot}%{_libdir}/udev/rules.d/
    -install -D -m 0755 dracut/71prefixdevname/module-setup.sh %{buildroot}%{_libdir}/dracut/modules.d/71%{name}/
    -install -D -m 0755 dracut/71prefixdevname-tools/module-setup.sh %{buildroot}%{_libdir}/dracut/modules.d/71%{name}-tools/
    +install -D -p -m 0755 target/release/prefixdevname %{buildroot}%{_udevdir}/prefixdevname
    +install -D -p -m 0644 rules/71-prefixdevname.rules %{buildroot}%{_udevrulesdir}/71-prefixdevname.rules
    +install -D -p -m 0755 dracut/71prefixdevname/module-setup.sh %{buildroot}%{_prefix}/lib/dracut/modules.d/71%{name}/module-setup.sh
    +install -D -p -m 0755 dracut/71prefixdevname-tools/module-setup.sh %{buildroot}%{_prefix}/lib/dracut/modules.d/71%{name}-tools/module-setup.sh
     
     %files
     %license LICENSE
     %doc README.md
    -%{_libdir}/udev/prefixdevname
    -%{_libdir}/udev/rules.d/71-prefixdevname.rules
    -%dir %{_libdir}/dracut/modules.d/71%{name}
    -%{_libdir}/dracut/modules.d/71%{name}/*
    -%dir %{_libdir}/dracut/modules.d/71%{name}-tools
    -%{_libdir}/dracut/modules.d/71%{name}-tools/*
    +%{_udevdir}/prefixdevname
    +%{_udevrulesdir}/71-prefixdevname.rules
    +%dir %{_prefix}/lib/dracut/modules.d/71%{name}
    +%{_prefix}/lib/dracut/modules.d/71%{name}/module-setup.sh
    +%dir %{_prefix}/lib/dracut/modules.d/71%{name}-tools
    +%{_prefix}/lib/dracut/modules.d/71%{name}-tools/module-setup.sh
  3. New (low) — tools/generated_sources.py:993-1062 adds _prefixdevname_transform/_prefixdevname_generate with no test, while every other generator has one (tests/test_generated_sources.py:518 PydanticCoreVendorTests, tests/test_generated_sources_generate.py:185,219). A PrefixdevnameVendorTests mirroring the pydantic one (fake tag archive + tinycrate, determinism, outside-top-dir rejection) would close it.

intent-alignment (advisory, low) — PR body says "the GitHub tag v0.2.0 archive is locked by sha512", but the lock is now the generated prefixdevname-0.2.0-vendored.tar.xz (config/upstream-sources.json:3086-3090); the tag archive is the generator's pinned input (tools/generated_sources.py:984-986). Update the body to say so.

docs-currency (advisory, low) — tools/generated_sources.py:4-29 module docstring enumerates each generated recipe and its reason; prefixdevname is not added (pydantic_core is also missing, pre-existing).

No findings from: security, style.

Confidence: 1/5 (needs attention) — 2 high findings

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

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@kylerankin 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 added stage/074-adopted-by-hive Contributor PR adopted: author unavailable after red CI; the hive is finishing it (takeover path) and removed stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act labels Oct 30, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

1 of 2 commits on ba165782988d are the hive's, signed off as the hive App, and the rest are @kylerankin's with their own sign-off. A squash would land the hive's commits under @kylerankin's name with the App's sign-off, so this PR merges with a merge commit instead (merge-method/merge): every commit lands as it is, each with its own author's sign-off. Nothing is rewritten and nobody needs to re-sign anything. Maintainers merging by hand: use gh pr merge --merge, not squash.

@hivecommons-hive hivecommons-hive Bot added the merge-method/merge Hive merges this PR with a merge commit (mixed authorship, each commit self-signed); never squash label Oct 30, 2026

@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 hanthor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Blocking

  • CI has never run, so the new generator in tools/generated_sources.py is untested.
  • The branch needs a rebase.

Nit: find Cargo.lock by its exact f"{top}/Cargo.lock" path, as the existing generator does, rather than with endswith.

kylerankin pushed a commit to kylerankin/utah-packages that referenced this pull request Oct 30, 2026
…uefin#819)

* feat: add the prefixdevname tool that shifts Windows-style prefix names

Import the prefixdevname Rust crate from the GitHub tag v0.2.0 archive,
unmodified, and lock that archive sha512 since upstream publishes no
release asset. Register the build in Packit, refresh the source-lock and
the architecture counts, and move prefixdevname from the long-tail
backlog area to [resolved] and regenerate the backlog report. No hosted
build, publication or runtime closure is claimed.

Refs projectbluefin#505

Hive-Run: projectbluefin#505
Hive-Plan: issue-505 implementation step 3 (prefixdevname source family)
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>

* docs: link the prefixdevname closing record to its pull request

Fill in the pr field on the prefixdevname [resolved] record now that the
import PR has a number.

Refs projectbluefin#505

Hive-Run: projectbluefin#505
Hive-Plan: issue-505 implementation step 5 (closing record)
Hive-Spec: factory-build-backlog#closing-a-backlog-gap
Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>
@kylerankin
kylerankin force-pushed the parity-505-long-tail branch from ba16578 to 340d915 Compare October 30, 2026 05:36

@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.

Looks correct to me; I reproduced the generated source lock independently.

What I checked (head fc9262d)

  • Ran python3 tools/generated_sources.py prefixdevname packages/prefixdevname <out> from a clean checkout of this head, on a different host, with network: output prefixdevname-0.2.0-vendored.tar.xz is 4,017,312 bytes with SHA-512 223679b0…c13f1 — byte-identical to the lock in config/upstream-sources.json and packages/prefixdevname/sources. The determinism claim (fixed mtime, zeroed ownership, cleared PAX headers, sorted members — tools/generated_sources.py, _prefixdevname_transform) holds in practice.
  • Fetched https://github.com/msekletar/prefixdevname/archive/refs/tags/v0.2.0.tar.gz and computed SHA-512 myself: matches PREFIXDEVNAME_INPUT_SHA512["0.2.0"], so _prefixdevname_generate really does pin the input tree rather than trusting whatever GitHub serves.
  • Crate bytes are verified before vendoring: the pre-existing _vendored_crate_members (tools/generated_sources.py:714-716) raises on a sha256 mismatch against Cargo.lock, so crates.io cannot substitute content. The new code reuses that path instead of re-implementing it.
  • .hummingbird-upstream.json with "branch": "upstream" and empty commit/tree has precedent (bluefin-artwork-logos, gnome-rounded-blur, libfreeaptx); generate entries with stage likewise (10 existing).
  • .packit.yaml position, [resolved] entry shape and backlog JSON deltas are consistent.

Canary is red for the usual fork reason — "a fork pull request cannot publish the canary image, and no maintainer-run Canary has passed" — not this diff; a maintainer needs to run the fork-Canary workflow against fc9262d59558b57d3e5469f788ca9959a97d5120.

Not checked: I did not compare prefixdevname.spec against Fedora's spec, since the provenance record declares this an upstream-branch recipe rather than a rawhide import.

Merge-order note: #823, #844, #834, #836 also bump the docs/architecture.md package-count table and edit factory-build-backlog.toml/.json; whichever lands after this one will need a count rebase.

Confidence: 5/5 (safe)

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

hanthor and others added 4 commits October 31, 2026 17:03
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>
Regenerate combined 680-recipe architecture and backlog state after projectbluefin#847 landed on main, and remove the prohibited historical DELTA session artifact carrying committed conflict markers.

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>
Preserve prefixdevname recipe, source lock and Rust vendor generator/tests while structuring generated_sources cleanly alongside sibling generators. Regenerate combined 681-recipe 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>
Merge current main (a590886) preserving all PR recipes and source locks, and regenerate combined 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>
@hanthor

hanthor commented Oct 31, 2026

Copy link
Copy Markdown
Member

Merged current main (a590886a) without rewriting branch history (2778b149997e78cd8cf9388ef2dd84553e2f9e37), preserved prefixdevname recipe, source lock, and Rust vendor generator structured cleanly alongside sibling generators, and regenerated combined inventory with just regenerate-inventory. Verified locally with just check.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

@kylerankin 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.

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

@kylerankin 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 review swarm requested changes

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 (4 waiting): fixes are handed out before new work as soon as you have capacity.

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

@kylerankin 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 review swarm requested changes

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 39ccf6d860aa384b372dbde481d335a287826df5 by @hanthor after review, from the in-repository copy canary/pr-819: https://github.com/projectbluefin/utah-packages/actions/workflows/canary.yml?query=branch%3Acanary%2Fpr-819. 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

@kylerankin 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

Copy link
Copy Markdown
Contributor

stage 080-awaiting-merge-admission → 074-adopted-by-hive: conflicting

hanthor and others added 5 commits October 31, 2026 22:45
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>
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>
Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@hanthor
hanthor enabled auto-merge (squash) November 1, 2026 00:12
@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Canary was run on this pull request at d064625565941ffc084b5e56ace4563d36f7167f by @hanthor after review, from the in-repository copy canary/pr-819: https://github.com/projectbluefin/utah-packages/actions/workflows/canary.yml?query=branch%3Acanary%2Fpr-819. 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

@kylerankin 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

@kylerankin 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 review swarm requested changes

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 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: Re-review of the follow-up changes since the last approval. The new code now reads the one Cargo lock file at the top of the upstream release instead of the first file whose name happens to end in Cargo.lock, so a stray nested lock cannot change which third-party crates get bundled; that fix is tested and sound. One leftover: the pull request description still says it refreshes the recipe counts in the architecture document, but that document no longer carries counts and this PR no longer changes it.

What I need from you: Drop the architecture-counts bullet from the PR description.


intent-alignment

  • (low) PR body bullet "Refresh the architecture counts in docs/architecture.md" no longer matches the diff. compare/main...d064625 touches 10 files and none is docs/architecture.md; at this head docs/architecture.md:144 reads "This document quotes no inventory counts". The fc9262d commit that did this was superseded by the main merge. Remove the bullet.

Delta checked: tools/generated_sources.py:1017 (src.getmember(f"{top}/Cargo.lock")) and :1066 (source.getmember(f"prefixdevname-{version}/Cargo.lock")) replace the endswith("Cargo.lock") scan; tests/test_generated_sources.py:222-247 covers the nested-lock case; docs/skills/supply-chain-provenance.md:285-288 documents the rule. 194 tests in the touched test files pass at d064625.

No findings from: correctness, security, style, docs-currency.

Confidence: 3/5 (needs attention) — 1 perspective requested changes

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

@hanthor
hanthor dismissed their stale review November 1, 2026 00:40

Resolved on reviewed head d064625: merged current main without force-push; just check passed (1471 tests, 3002 subtests) and full pre-commit passed; both Cargo.lock consumers now use the exact top-level path with a nested-lock regression. Actual generator CLI reproduced the locked 4,017,312-byte bundle and SHA-512. Maintainer fork proof and automatic PR-check refresh passed in run 41255736409; current-head Canary, Unit tests and Runtime contract are green. Dismissing my stale changes-requested review under the user-authorized #819 landing; normal branch protection and auto-merge remain in force.

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

Labels

author/clanker A contributor's own hive authored this PR under their login dco All commits are DCO signed-off merge-method/merge Hive merges this PR with a merge commit (mixed authorship, each commit self-signed); never squash role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/074-adopted-by-hive Contributor PR adopted: author unavailable after red CI; the hive is finishing it (takeover path)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants