Repository navigation
feat: ready-to-use Codex adapter and two real defect workflows - #11
Merged
Merged
Conversation
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.
New users previously needed a custom JSON wrapper for a vendor CLI and had to assemble real defect acceptance manually. This adds a pinned Codex 0.163.0 adapter/profile generator and
case-init/case-checkworkflows for two independent Python defects.The adapter requires an explicit model, read-only proposals, strict completed JSONL events, separate acceptance credentials and durable invocation/time reservations. It supports npm native-package layouts and nested working directories. The cases pin boltons/more-itertools source and fix commits, reproduce target assertions, accept the reference change, reject an intentional regression, rerun recovery and export portable positive/negative evidence. Protocol/reference controls are labelled separately from live AI results.
Validation of tree
238e62dc39ec74441842ab71ac1d844c7d388066:17b370e997bfe8f966d61ffd3352324ba838a7e7remains in history.Roadmap: live model validation with credentials and an explicit spending allowance; certified Node/GenericCommand evidence; at least three independent new-user walkthroughs; maintainer license choice, support/upgrade notes and final stable-release acceptance. No paid model request was made. See docs/PRODUCT_PLAN.md and docs/ACCEPTANCE_MATRIX.md.
Post-merge verification: main commit
bf77f7f0d0f80e7d9013fd64ad84c6c09366797dhas the identical tested tree. All 11 main-branch CI jobs passed in run 39117791709.