Skip to content

fix(verify): raise the collection floor to the post-merge reality (345 -> 353) - #15

Merged
stranske merged 1 commit into
mainfrom
claude/floor-after-research-merge
Aug 22, 2026
Merged

fix(verify): raise the collection floor to the post-merge reality (345 -> 353)#15
stranske merged 1 commit into
mainfrom
claude/floor-after-research-merge

Conversation

@stranske

Copy link
Copy Markdown
Owner

The floor committed in #12 was measured on a branch cut before #13 (research panels, rounds, domain studies) merged, so main's recorded floor sat 8 tests below what main actually collects (345 vs 353).

A floor below reality fails in the permissive direction: those 8 tests could have stopped being collected and the check would still have passed — exactly the hole .verify-floor.json exists to close, since a silent drop in tests-collected reads identically to tests passing.

Measure the floor on the merge result, not on the branch. Ceilings unchanged (24/7/2).

python3 verify.py: 353 passed, 0 failed, 0/24 skipped, 81 selftests, 5/5 gates green — run from both the canonical tree and the exec mirror.

🤖 Generated with Claude Code

…5 -> 353)

The floor committed in #12 was measured on a branch cut before #13 (research panels, rounds, domain
studies) merged, so main's recorded floor sat 8 tests BELOW what main actually collects.

A floor below reality fails in the permissive direction: those 8 tests could have stopped being
collected and the check would still have passed, which is exactly the hole .verify-floor.json exists
to close — a silent drop in tests-collected reads identically to tests passing.

Measure the floor on the merge result, not on the branch. Ceilings unchanged (24/7/2).

verify.py: 353 passed, 0 failed, 0/24 skipped, 81 selftests, 5/5 gates.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 41 minutes

Limit details: You’ve used the included review currently available. Your 66 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 13871f3a-a526-4b24-a13d-c536f4a12874

📥 Commits

Reviewing files that changed from the base of the PR and between 17a6d26 and 98aa985.

📒 Files selected for processing (1)
  • .verify-floor.json

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

@stranske
stranske merged commit cdc9367 into main Aug 22, 2026
2 checks passed
@stranske
stranske deleted the claude/floor-after-research-merge branch August 22, 2026 16:49
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.

1 participant