Repository navigation
Bound managed Jev requests and align the individual usage contract - #253
Merged
Merged
Conversation
…dividual-access-20261004-review-fallback
Integrate current main, keep managed fixed reviews independent from BYOK-only planning, validate payload bytes before credential lookup, retain opt-in compact previews, and correct selected-report labels and integration docs. Regenerate immutable source-bound evidence and shipped contracts.
Restore canonical v149 integrity, guard Latest promotion after uploads, and bind fresh immutable offline evidence. Preserve external Ask/UI fixes and qualify offline provider and workspace fixtures.
Use the actual connector-created source commit for the benchmark guide and figure links. Fifty affected evidence and documentation checks pass; the runtime tree is unchanged from the qualified offline repair.
… repair Preserve both public parent histories and external Ask/UI work. Retain consent, purpose, origin and absolute-deadline boundaries; bind fresh immutable source evidence and qualify all offline acceptance gates.
Use the actual published source identity in all eight guide consumers. The qualified offline runtime tree is unchanged; 131 affected evidence and documentation checks pass.
Record the reviewed PR252 squash checkpoint as a second parent. Main has exactly the incorporated cc1f2c0 tree; retain the fully qualified PR253 tree unchanged so the remaining review is scoped to managed transport and its evidence.
Coding-Dev-Tools
changed the base branch from
codex/jev-pro-team-pr-20261003-final
to
main
October 8, 2026 03:18
Coding-Dev-Tools
marked this pull request as ready for review
October 8, 2026 03:18
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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4351c3128f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Correct only the sidecar basename, retaining the original digest, CRLF and historical JSON bytes. The regression preserves the advertised payload identity; 49 affected tests and a real sha256sum check pass.
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.
Change
Restricts managed Jev to fixed, bounded support, contradiction, command and completion workflows. Custom questions and route planning fail locally before client selection or credential access. Per-call consent, classification, credential-bound origin and an absolute request deadline remain required. Questions count individually; explicit opaque request keys identify a lost-reply retry without an automatic client retry.
The transport bounds HTTP 429 body and chunk-framing reads by the same deadline, preserves only allowlisted allowance/protection reasons, and retains control URL path prefixes. This PR incorporates the merged #252 consent, offline-review and deterministic-planner fixes, and is now based on main. Its current immutable offline evidence and guide/figure consumers point to source commit
522def372c45a26d46bc7a05829964ae0240f3a9. The retained v142 client JSON and measurements are unchanged; its checksum sidecar now resolves the correct adjacent filename.Verification
b5ce84a9551387af8e9aa01846e7a2e7e050457f. Exact-head CI, CodeQL, and automated review provide the current acceptance results.sha256sum --checkpassed; the historical digest and CRLF are preserved. No runtime source changed in this final two-file repair.Release boundary
Managed availability remains
not_yet_availablepending separate private Cloud identity, admission/idempotency, rolling-limit and capacity acceptance. The documented per-individual limits are 100 questions/hour, 1,000/five hours and 2,000/24 hours. The public offline fixtures establish deterministic client behavior and artifact integrity; private-service qualification and activation remain separate.