Repository navigation
Integrate Codex packaging, rehearsal guidance, and model snapshot pin - #7
Merged
Merged
Conversation
The unversioned `qwen-flash` alias silently re-points as Alibaba ships new flash generations, so the kit's documented fast lane was a moving target. Pin the default to `qwen-flash-2025-07-28`, the behaviour-equivalent dated snapshot (live-probed against dashscope-intl compatible-mode: 200 OK, echoes back the snapshot id — note it is NOT listed by GET /models, so a catalog grep is a false negative; only an inference probe confirms it). Also updates the surfaces that state the default — README env table + fast-lane prose, .env.example, the architecture diagram (md + generated html) and the routing unit test — so the public lane mapping matches the code. 39/39 tests pass. `dist/` is gitignored here, so there is no compiled output to commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…aderless Public MCP remains 8 tools. formation.checkout is gated, not missing. X-Corpus-Rehearsal belongs on a private Grok Bot connector only. No canary claimed.
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
+55
to
+56
| tag = ref.removeprefix("refs/tags/") | ||
| if tag.startswith("corpus-openai-v") and tag != f"corpus-openai-v{version}": |
There was a problem hiding this comment.
The version check runs only when the supplied ref already starts with corpus-openai-v. A differently named future tag such as v0.2.0 therefore bypasses the documented naming and version rule while still producing a normal versioned archive and release.json. Detect tag refs independently of their spelling and reject release tags that do not exactly match the manifest version, while continuing to permit HEAD for CI builds.
Prompt To Fix With AI
This is a comment left during a code review.
Path: scripts/package-openai-plugin.py
Line: 55-56
Comment:
**Release Tags Bypass Validation**
The version check runs only when the supplied ref already starts with `corpus-openai-v`. A differently named future tag such as `v0.2.0` therefore bypasses the documented naming and version rule while still producing a normal versioned archive and `release.json`. Detect tag refs independently of their spelling and reject release tags that do not exactly match the manifest version, while continuing to permit `HEAD` for CI builds.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
| - uses: actions/setup-python@v5 | ||
| with: | ||
| python-version: '3.12' | ||
| - run: python3 scripts/package-openai-plugin.py HEAD |
There was a problem hiding this comment.
CI builds the archive only once and checks ZIP integrity, so it does not verify the newly documented guarantee that repeated builds of the same ref are byte-identical. A change that reintroduces timestamps, unstable ordering, or compression variance could pass unnoticed. Build the same ref into separate output directories and compare the resulting archive bytes or checksums before the unzip check.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/ci.yml
Line: 26
Comment:
**Reproducibility Is Not Tested**
CI builds the archive only once and checks ZIP integrity, so it does not verify the newly documented guarantee that repeated builds of the same ref are byte-identical. A change that reintroduces timestamps, unstable ordering, or compression variance could pass unnoticed. Build the same ref into separate output directories and compare the resulting archive bytes or checksums before the unzip check.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
teakesdev
changed the title
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.
Adds the OpenAI Codex marketplace/package and reproducible archive builder, including CI packaging checks. Incorporates private rehearsal-header guidance while correcting the old claim that public checkout is disabled; the public ten-tool contract remains intact. Pins the autopilot fast-lane default to the documented equivalent qwen-flash-2025-07-28 snapshot, preserving environment overrides.
Validation: 39 autopilot and 6 bridge tests passed; workspace typechecks and builds passed; generated skill drift and plugin manifest checks passed; npm package dry run passed; repeated OpenAI archive builds were byte-identical and unzip integrity passed. GitHub CI passed on the combined code at 52d8397; the final commit only records this validation. No tag, publication, production deployment, flag change, or paid request.