Repository navigation
chore(pins): move to governance generation Q (5ef12472) - #12
Merged
Merged
Conversation
Move every project-governance pin surface of this repository from generation P (1c8b37c8) to generation Q (5ef12472), as planned by project-governance tools/fleet/bump-generation.ts: reusable workflow `uses:`, `tooling_ref:`, governance checkout refs and the card `pinned:`, where present. Q composes schemas-and-contracts at a82d7b54 and project-governance at d94081cc. Owner-arbitration: 2026-10-10 — fleet migration to generation Q arbitrated in chat. Claude-Session: https://claude.ai/code/session_01F18JyLzoGrRpt7efAr4E92 Signed-off-by: Constantin <74049135+constantin-jais@users.noreply.github.com>
Generation Q composes project-governance at d94081cc, whose check-bun-manifests requires every lifecycle script to start with `bun run check:bun:runtime && ` (Bun-floor bypass fix, governance #66). packages/ui `prepublishOnly` started with `bun run check`, so `bun run build` refused the manifest and the composition stopped before any check ran: Bun manifests: package.json: prepublishOnly must enforce the Bun floor first: start with `bun run check:bun:runtime && ` and chain only with `&&` Owner-arbitration: 2026-10-10 — fleet migration to generation Q arbitrated in chat. Claude-Session: https://claude.ai/code/session_01F18JyLzoGrRpt7efAr4E92 Signed-off-by: Constantin <74049135+constantin-jais@users.noreply.github.com>
…endency Generation Q's check-bun-manifests reads tracked nested manifests and only treats paths under distribution/templates/ as standalone templates. Here bun-app and starter are workspace members (workspace:* dependencies) of packages/starter, so the gate held them to the governance form and failed with "check:bun must be one of ... ../node_modules/@libre-ai/governance/...". Point their check:bun at the same runtime floor the other packages use. Signed-off-by: Constantin Jais <74049135+constantin-jais@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Move every
project-governancepin surface of this repository from generation P (1c8b37c80beb41f640982768ec27304a911e0b8e) to generation Q (5ef12472d043f3ed1799ca09cff89c27ff024d79), declared inproject-governance/ecosystem/fleet-pins.v1.yaml.Q composes
schemas-and-contractsata82d7b54andproject-governanceatd94081cc(.github/composition/manifest.jsonat Q).execution-continuity-evaluatoris already on Q (e29f507).Evidence
bun tools/fleet/bump-generation.ts --to 5ef12472… --public-only(dry run,project-governanceat93ca8e4), which plans this repository asbump; after the edit,git grep 1c8b37c8returns no surface.composition / validateruns the composition at Q's refs.Owner-arbitration: 2026-10-10 — fleet migration to generation Q arbitrated in chat.
https://claude.ai/code/session_01F18JyLzoGrRpt7efAr4E92