Extend OCR-helpers ledger row for PR #384's marker-detection change - #394
Merged
Conversation
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Description
Conventions-compliance pass over today's (2026-07-23) shipped work
against
docs/upstreaming/extractable-primitives.md's own criteria.local_ocr.py'sparse_legal_line(_PROXY_MARKER_RE, copyright-yearregex) is a pure text-in/struct-out classifier with zero fork-only
imports, widened today by PR #384 to catch maker-brand-glued proxy
markers ("JestaProxy"). It wasn't listed in the existing "OCR
crop/preprocessing helpers" row's function set even though it qualifies
by the same standard as every other function already in that row —
added it, plus a Detail-notes sentence explaining why it's included
(mirroring how
validate_against_candidates/find_matching_candidatesare explained as excluded there).
Everything else audited this pass (
pilot_run_lifecycle.py,local_layout_class_cast.py,retract_stage_d_by_run_id.py, the #380reparse/lexicon changes) is verified accurate or genuinely
non-qualifying — no further ledger edits.
modern_artist_credit.py(#390) is judged but not rowed since it's unmerged (file doesn't exist
on
masteryet — the ledger's own "read directly from the repo onmaster" ground truth).
scripts/ops/crash_drill.shand a"sequence-independence test pattern" PR referenced in this pass's brief
don't exist as any PR (open/closed/merged) or committed file anywhere
in the repo as of this audit — nothing to check in against. PR #352's
button-divergence documentation requirement (owner's "if we diverge
from upstream, document it" rule) is already satisfied — verified
present at
docs/upstreaming/readiness-audit.md§10 with matching// diverges from upstream:comments at each cited call site.Docs-only, no code changes.
Checklist
pre-commitand installed the hooks withpre-commit installbefore creating any commits.python3 .github/scripts/docs_lint.py --strict(clean) and the link-rewrite-parity/readme-parity fixture test scripts (all passing, unaffected by this change).