Repository navigation
fix: retain sequential pool roll history and image bindings - #272
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
tangletools
approved these changes
Oct 23, 2026
tangletools
left a comment
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved PR — 7b3509c2
Blanket team auto-approval is intentional. This is not a code review.
No automated review runs on this PR. This approval rests on the rule above alone.
tangletools · auto-approval · reason: blanket_auto_approve · 2026-10-23T01:37:32Z
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
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.
A completed pool roll currently rejects the next immutable artifact. The existing authenticated owner now starts a new transaction only from the completed candidate's exact ID after its slot is drained and idle, appends the previous receipt to history, and retains original adoption identities and stopped predecessors. Missing local images leave the completed journal unchanged. Status reports each current slot's immutable image binding, including mixed-image pools, for the existing security-report consumer.
Exact API-only head7b3509c2bdc68e608b309ac8187ada95f3193f9d has a maintenance module and real Docker/HTTP fixture byte-identical to qualified936748602e3ca28535b39441cc5cb11776cd95d9 (empty Git diff for both files). That Beelink2 frozen-install/typecheck/integration gate passed209s (beelink2-a2bb99ec5e50c9cddefb6c8842500c8b): real active work survives drain, unrelated slots serve, two successive artifacts preserve credential volumes/environment/resources, missing images leave the journal unchanged, stale intents refuse, and a real owner restart reconciles the latest candidate. Independent source review passed; this isolated change contains only the owner, its integration fixture and API documentation. No image dependency changes or claims of reduced live vulnerability counts.
Run ID: run_4b1d54cfdf2c05412b39044bf98511e1