Skip to content

fix(evals): preserve compound disclaimers and gate claims - #181

Merged
vriesd merged 6 commits into
mainfrom
fix/compound-review-disclaimer
Oct 7, 2026
Merged

vriesd merged 6 commits into
mainfrom
fix/compound-review-disclaimer

Conversation

@vriesd

@vriesd vriesd commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Why

Qualification rejected a truthful deferred handoff because it said No independent review or completion is claimed. The same answer exposed a separate gap: a gate result after preceding prose could escape command evidence checks.

What changed

  • Interpret the exact compound disclaimer as completion not claimed, without asserting whether review was performed.
  • Preserve both clauses around the observed Linux gate wrapper. A quote-aware scan keeps ordinary punctuation and Unicode word apostrophes while preserving exact command arguments.
  • Retain the actual answer and cover conflicting exits, unknown commands, result tails, critical preceding claims, and scoped or opaque text.

Scope

Evaluator parsing and focused regression fixtures only. Product package bytes, policy, catalog, case instructions, sampling, and passing requirements stay unchanged.

Tradeoffs

The parser recognizes the observed wrapper while retaining both source clauses. The existing command parser and native evidence checks evaluate the result. It does not discard preceding claims or infer facts from review disclaimers.

Blast Radius

Delivery grading accepts the supported handoff and rejects altered command claims. The stopped campaign remains failed and supplies no qualification credit.

Verification

  • RED reproduction precedes GREEN. The unchanged actual native input passes after the fix, while incorrect exits, unknown commands, contradictory tails, and unsupported completion claims reject.

  • Focused delivery checks passed with 652 tests and zero failures. Typecheck passed. The reported apostrophe and colon cases reject incorrect exit claims, and quoted and unquoted command arguments retain their binding.

  • Diagnostic replay covers 348 attempts from 11 byte-identical original reports. It accepts 346, preserves one genuine disclosure failure, and excludes one host failure.

  • Full push preflight passed on the final head with 2,903 tests passing, 20 existing skips, and zero failures. Independent exact-head, native-evidence, package, and comment reviews passed.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-07T23:05:33.076762Z b21a049 PR opened
ℹ️ 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" or "@codex security review".

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 chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b21a049e86

ℹ️ 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".

Comment thread evals/delivery-presentation.ts Outdated
@vriesd
vriesd merged commit e345030 into main Oct 7, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants