Fix source-aware artifact detection and add benchmark tracks#1
Draft
kiriakostsourekas-wq wants to merge 4 commits into
Draft
Fix source-aware artifact detection and add benchmark tracks#1kiriakostsourekas-wq wants to merge 4 commits into
kiriakostsourekas-wq wants to merge 4 commits into
Conversation
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.
What changed
.bib,.bbl, and embeddedthebibliographystructure before artifact scanning.Root cause
The browser previously routed
.bibcontent through the ordinary text scanner, so legitimate titles containing phrases such as “As an AI Language Model” were treated as manuscript prose. Chat rules also recognized ASCII contractions but missed typographic apostrophes copied from common editors and chat interfaces.Benchmarking
This adds two deliberately separate tracks under
benchmark/:The checked-in Track A data is a regression/smoke seed. It is intentionally marked
releaseReady: falseuntil the full licensed and independently adjudicated corpus is supplied. Track A and Track B must not be combined into one leaderboard.No model, API, or runtime dependency was added to the browser product.
User impact
.bbland embedded bibliography titles receive the same protection.Validation
node --test tests/*.test.mjs— 260 passedpython3 -m unittest benchmark.tests.test_track_b -v— 9 passed--releasecorrectly fails because the publishable corpus requirements are not yet met.