Repository navigation
fix: make installed adapter selection authoritative - #299
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. |
This was referenced Nov 2, 2026
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.
Qualification blocker — adapter-selection prerequisite
PR #299 was created and merged by account Dimkox on 2026-11-02 at 13:17:25/35 UTC (16:17 Moscow), before this coordinator completed independent reviews and full local qualification. Its head is
e430ec0622b2b1164d4cc75816f1c73d2c9973ff; merge3310ab7f3d1898e8fbb929b889b80e584dbd23c9has the identical treee87e81e05ae045c06079ba64ac02e6772b673f7c.Independent code review found a blocking AC-007 defect. Generation ignores a valid
AGBP_SYNC.jsonkeep declaration. Real lifecycle checks reproduced overwrite after a canonical change, deletion after canonical removal, and creation of a declared-kept absent path. Security review independently confirmed the missing check. Both reviews are FAIL. Passing author tests and the 115-test committed observation do not override this defect.The repair will make generation honor the existing bounded keep contract before creation, replacement or retirement, validate declared digests, and avoid claiming ownership of preserved custom content. The three lifecycle cases and stale-digest behavior need regressions. Fresh code/security/release reviews, full native PR verification and exact-head CI will follow the repair.
#234 and GZDEV-38 remain open. Shared namespace relocation, adapter removal and native-hook deactivation remain outside this prerequisite. This is not a production-readiness or completion claim.
Problem
Installed adapters were inferred independently by installation, generation, setup and update. An empty choice could become a default adapter. Existing folders could expand the choice. Generic generation and updates lacked one shared record of which files they could replace.
Change
.getzilla/managed-components.jsonfor complete adapter selection and file ownership. Preserve explicit[]. Reject invalid state and require explicit legacy adoption.Scope
Prerequisite for #234; related to #166 and Jira GZDEV-38. These issues remain open. This change does not complete shared namespace relocation, adapter removal or native-hook deactivation. Empty selection does not disable retained shared Grok hooks. The advisory guard does not provide OS isolation; an I/O failure can leave partial files.