Skip to content

corpus: harvest realized-outcome verifier cases - #2843

Merged
stranske merged 1 commit into
mainfrom
verifier-corpus-harvest/auto
Jul 27, 2026
Merged

corpus: harvest realized-outcome verifier cases#2843
stranske merged 1 commit into
mainfrom
verifier-corpus-harvest/auto

Conversation

@stranske

@stranske stranske commented Jul 27, 2026

Copy link
Copy Markdown
Owner

Automated corpus growth (#2819 move 2).

High-confidence cases derived from realized PR outcomes — see the run
summary for the promoted case list. Ambiguous cases were routed to the
auto-expiring staging file, not here.

Expected verdicts here come from what the world already adjudicated by
merging or reverting each PR. The semantic NON_PASS categories
(stale-verifier-claim, review-thread-debt, missing-acceptance-criterion)
remain owner-sourced and are never machine-added.

Summary by CodeRabbit

  • Tests
    • Expanded the staging evaluation set with four additional verification cases.
    • Added a broader collection of harvested cases to the pilot evaluation corpus.
    • Updated evaluation metadata to reflect the latest corpus revision and collection dates.
    • All newly added staging cases are expected to pass, improving coverage for clean-pass verification scenarios.

@stranske stranske added automation Automation and workflow automation model-selection labels Jul 27, 2026
@cursor

cursor Bot commented Jul 27, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@stranske
stranske enabled auto-merge (squash) July 27, 2026 06:48
@stranske
stranske temporarily deployed to agent-standard July 27, 2026 06:48 — with GitHub Actions Inactive
@agents-workflows-bot

Copy link
Copy Markdown
Contributor

Workflow source needed

PR #2843 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely.

Please do one of:

  • Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
  • Check one Workflow Source option in the PR body.
  • Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
  • Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.

@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The verifier corpus staging configuration gains four harvested cases. The pilot configuration receives a +harvest21 version, multiline case formatting, and additional harvested workflow cases with provenance and harvest dates.

Changes

Verifier corpus data

Layer / File(s) Summary
Populate staging corpus
config/model_eval_corpus_staging.json
Replaces the empty cases array with four harvested records containing identifiers, repository and PR references, expected verdicts, categories, provenance, and harvest dates.
Expand pilot corpus
config/model_eval_pilot.json
Updates corpus_version, reformats existing cases, and adds harvested workflows-* cases with provenance and harvested_at fields.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: harvesting realized-outcome verifier cases into the corpus.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch verifier-corpus-harvest/auto

Comment @coderabbitai help to get the list of available commands.

@stranske-keepalive

stranske-keepalive Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Automated Status Summary

Head SHA: 0cb0a97
Latest Runs: ⏳ pending — Gate
Required contexts: Gate / gate, Health 45 Agents Guard / guard
Required: core tests (3.12): ⏳ pending, core tests (3.13): ⏳ pending, docker smoke: ⏳ pending, gate: ⏳ pending

Workflow / Job Result Logs
(no jobs reported) ⏳ pending

Coverage Overview

  • Coverage history entries: 0

Updated automatically; will refresh on subsequent CI/Docker completions.


Keepalive checklist

Scope

No scope information available

Tasks

  • No tasks defined

Acceptance criteria

  • No acceptance criteria defined

@stranske
stranske temporarily deployed to agent-standard July 27, 2026 06:48 — with GitHub Actions Inactive
@stranske
stranske temporarily deployed to agent-standard July 27, 2026 06:48 — with GitHub Actions Inactive
@stranske
stranske merged commit eaab0fe into main Jul 27, 2026
81 of 92 checks passed
@stranske
stranske deleted the verifier-corpus-harvest/auto branch July 27, 2026 06:50

@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: ed96593ec1

ℹ️ 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 on lines +347 to +348
"expected_verdict": "PASS",
"category": "clean-pass",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Remove the mislabeled clean-pass case

PR #2528 did not remain a clean, durably complete PASS: its merge commit d096fa2 was followed only two hours later by the direct child commit 7648a7e, titled Follow up #2528: upload LangSmith fleet artifact under registry name. Because the pilot evaluates only the original PR diff, a verifier that correctly detects that missing work will return NON_PASS and be charged a false fail; with the current 47 expected-PASS cases, that single error produces a Wilson upper bound of about 0.111, exceeding the policy's 0.10 false-fail gate. Exclude this case or adjudicate it as NON_PASS rather than promoting it as clean-pass.

Useful? React with 👍 / 👎.

@coderabbitai coderabbitai 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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@config/model_eval_pilot.json`:
- Around line 217-405: Update the model evaluation configuration’s purpose text
to distinguish the frozen 30-case paired pilot from the additional harvested
cases, and revise the evaluation corpus handling so repeated PASS-only
harvesting does not dilute the NON_PASS signal used to compare model candidates.
Preserve the owner-sourced NON_PASS semantics while making the
frozen-versus-augmented case sets explicit.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 022d56a5-824a-43cd-a099-4a4bb2ef10e8

📥 Commits

Reviewing files that changed from the base of the PR and between fdd8007 and ed96593.

📒 Files selected for processing (2)
  • config/model_eval_corpus_staging.json
  • config/model_eval_pilot.json

Comment on lines +217 to +405
{
"case_id": "workflows-2545",
"repo": "stranske/Workflows",
"pr": 2545,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2544",
"repo": "stranske/Workflows",
"pr": 2544,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2543",
"repo": "stranske/Workflows",
"pr": 2543,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2540",
"repo": "stranske/Workflows",
"pr": 2540,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2539",
"repo": "stranske/Workflows",
"pr": 2539,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2538",
"repo": "stranske/Workflows",
"pr": 2538,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2537",
"repo": "stranske/Workflows",
"pr": 2537,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2536",
"repo": "stranske/Workflows",
"pr": 2536,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2535",
"repo": "stranske/Workflows",
"pr": 2535,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2534",
"repo": "stranske/Workflows",
"pr": 2534,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2533",
"repo": "stranske/Workflows",
"pr": 2533,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2532",
"repo": "stranske/Workflows",
"pr": 2532,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2531",
"repo": "stranske/Workflows",
"pr": 2531,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2530",
"repo": "stranske/Workflows",
"pr": 2530,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2528",
"repo": "stranske/Workflows",
"pr": 2528,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2527",
"repo": "stranske/Workflows",
"pr": 2527,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2524",
"repo": "stranske/Workflows",
"pr": 2524,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2523",
"repo": "stranske/Workflows",
"pr": 2523,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2522",
"repo": "stranske/Workflows",
"pr": 2522,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2520",
"repo": "stranske/Workflows",
"pr": 2520,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
},
{
"case_id": "workflows-2519",
"repo": "stranske/Workflows",
"pr": 2519,
"expected_verdict": "PASS",
"category": "clean-pass",
"provenance": "harvested",
"harvested_at": "2026-07-27"
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🗄️ Data Integrity & Integration | 🔵 Trivial

Growing PASS-only harvest may dilute NON_PASS signal; "purpose" text is now stale.

All 21 newly harvested cases are PASS/clean-pass (by design, since NON_PASS semantics stay owner-sourced). This is expected, but it shifts the pilot's NON_PASS ratio from 4/30 (~13%) toward 4/51 (~8%) as harvesting continues each round, which could weaken the pilot's power to discriminate model candidates on NON_PASS detection over time. Separately, purpose (Line 4) still describes this as a "Paired 30-case pilot" even though the corpus now totals 51 cases — worth updating or clarifying that harvested cases augment, but aren't part of, the frozen 30-case paired set.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@config/model_eval_pilot.json` around lines 217 - 405, Update the model
evaluation configuration’s purpose text to distinguish the frozen 30-case paired
pilot from the additional harvested cases, and revise the evaluation corpus
handling so repeated PASS-only harvesting does not dilute the NON_PASS signal
used to compare model candidates. Preserve the owner-sourced NON_PASS semantics
while making the frozen-versus-augmented case sets explicit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation Automation and workflow automation model-selection

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant