Skip to content

fix: isolate report cohorts and hash scored inputs - #3

Open
rudycelekli wants to merge 1 commit into
firecrawl:mainfrom
rudycelekli:fix/report-run-cohorts
Open

rudycelekli wants to merge 1 commit into
firecrawl:mainfrom
rudycelekli:fix/report-run-cohorts

Conversation

@rudycelekli

Copy link
Copy Markdown

The public reporter silently pools every historical engine/track directory. An old successful smoke run and a newer unsuccessful run therefore yield recall 0.500 instead of the current run's 0.000, mixing experiments and changing bootstrap inputs.

Select the newest run directory per literal engine/track label, retaining repeated passes within it. Do not revive stale successes when the latest directory is empty. Record selected paths, row counts and SHA-256 digests from the exact bytes scored in the JSON output. Document selection and install the wrapper's existing numpy dependency in offline CI so these new tests run there.

Four synthetic reporter regressions: 3 fail on exact upstream, 1 passes. Full Python 3.11 suite: 136 passed. Base-to-head diff check passes; independently reviewed and rerun. No provider calls or published tables changed. This preserves the existing bootstrap assumptions; it does not certify full cohort coverage or compatibility across independently selected tracks.

AI-assisted contribution; code and regression evidence reviewed before submission.

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