Align video catalogue limits and OCR coverage with native evidence - #15
Merged
Merged
Conversation
DrDrewCain
changed the base branch from
feature/video-frame-understanding
to
main
September 13, 2026 02:36
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.
Valid native video evidence could fail to display when a frame had over 10,000 OCR regions or supplementary Unicode characters in labels, metadata or filenames. The parser also accepted nonwhitespace recognized text that no OCR region accounted for.
Match the native 20,000 cumulative region allowance and Unicode character limits, and require region spans to account for all nonwhitespace text. Source identities, exact clocks and aggregate text/region limits remain checked.
Builds on Web PR14. Validation: 452 tests pass; strict TypeScript and production build pass. Independent native-comparison probes accept 20,000 cumulative regions and a 50,001-emoji OCR label, reject 20,001 regions, and refuse uncovered text. Five persistent regressions reproduced the failures before correction. Existing bundle-size advisory remains.