Conversation
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
E2E Evals: ✅ PASS1/1 tests passed | $.87 total cost | reconcile exit: 0
Fail-closed reconciliationSliced lane: diff-selected gate census via scripts/test-paid-shards.ts (planner → 6 executors → fail-closed report) |
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
garrytan
added a commit
that referenced
this pull request
Sep 11, 2026
PR #2852 now claims v1.85.0.0. Align the release metadata and rename migration so upgrades from that version still receive it. Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Co-Authored-By: OpenAI Codex <noreply@openai.com>
Normalize BSD wc output, compare Windows paths by filesystem identity, preserve portable snapshot race coverage, and narrow POSIX-only Windows fixtures. Co-Authored-By: OpenAI Codex <noreply@openai.com>
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.
Why (in your own words)
Today
/csocan describe security risks, but it cannot reliably prove that a vulnerability is reachable, that a proposed repair fixes the same assertion, or that the finding stays closed against current source. This release adds a fail-closed local evidence pipeline: capture the real source safely, distinguish supported findings from hypotheses and coverage gaps, reproduce candidates only in qualified containment, issue replayable repair bundles, and recheck closure from a fresh snapshot.Live evidence
I ran the compiled helper against a local vulnerable Node fixture containing a query parameter concatenated into SQL:
This is the intended daily-mode behavior: a complete static assessment can support a finding without falsely claiming runtime reproduction or repair.
Scope
@garrytanPR-liveness exemption.Liveness proof (required for external contributors)
Authenticated PR author is
@garrytan, verified withgh api user --jq .login. The repository-owner exemption applies; no screenshot is required.Checklist
GSTACK PRtyped live into a real surface) or PR author is @garrytan (owner exemption)Summary
Verified audits and repair lifecycle
--doctor,--resume,--replay, and--recheckwhile preserving bounded daily static audits and existing scope/diff flags.VERIFIEDclaims.Contained execution and environment support
Qualification and release safety
self_reported; the strongertestedlabel stays reserved for a future target-independent completion witness.@garrytan; external contributors retain the liveGSTACK PRrequirement.Test Coverage
bun run build: passed.bun run skill:check: all generated host variants fresh; 54 Codex skills present.Platform-specific Docker, macOS, and Windows scenarios are explicit skips locally and mandatory in their dedicated CI jobs.
Pre-Landing Review
No P0-P2 issues found. Independent native, security, cross-platform, and release reviews covered exact head
b2ad371e. The added-line credential scan found 0 high-severity findings; 74 PII/internal advisories were reviewed as public test inputs and version-like fixture values.Design Review
No production frontend changed; design review was skipped.
Eval Results
The free evaluation-contract suite validates 40 vulnerable/fixed pairs across Node, Bun, Python, and Rails, three-repetition accounting, precision/recall gates, held-out repair assertions, and no false repair certification. Paid matched-model runs were not executed in this workspace and remain a promotion prerequisite.
Plan Completion
Implementation tasks T1-T6 are present: contracts, trusted execution primitives, Node repair workflow, Bun/Python/Rails preparation, scanner adapters, and distribution/release qualification. Catalog publication and release-metric claims remain gated on protected CI and paid evaluation evidence.
Verification Results
bun test test/cso-*.test.ts: PASS (582 tests, 22 expected skips)cso-runtime-releaseandcso-scanner-release: configured with required@garrytanreview and branch policy.TODOS
No TODO items were completed in this PR.
Test plan
bun test test/cso-*.test.ts: 582 passed, 22 expected skips, 0 failedxvfb-run -a bun run test:free: 10,000 tests across 596 files; one timeout passed the required serial retry; final exit 0bun run build: compiled helpers and regenerated all host skill variantsbun run skill:check: generated files fresh and host skill manifests completeGenerated with OpenAI Codex.