Skip to content

fix(compiler): retain exact opaque field labels - #304

Merged
abrichr merged 1 commit into
mainfrom
agent/opaque-select-exact-label-20260728
Jul 28, 2026
Merged

fix(compiler): retain exact opaque field labels#304
abrichr merged 1 commit into
mainfrom
agent/opaque-select-exact-label-20260728

Conversation

@abrichr

@abrichr abrichr commented Jul 28, 2026

Copy link
Copy Markdown
Member

Summary

  • retain one exact, row-aligned field label for opaque select controls
  • require exact OCR uniqueness while preserving legacy fuzzy landmark serialization
  • revalidate the same selected field after focus before any option input

Safety contract

  • duplicate exact labels refuse instead of selecting the first candidate
  • low-confidence duplicate OCR still contributes to ambiguity
  • a moved post-focus target halts before bulk type or Enter
  • legacy sealed bundle digests remain unchanged

Validation

  • 216 affected tests passed
  • full package mypy and strict safety mypy passed
  • Ruff and diff checks passed
  • independent review found no high or medium issue
  • public changes contain only generic mechanisms and synthetic geometry

The retained private OpenEMR recording now compiles its first opaque select with the exact independent field label, without publishing application data or tuning.

@abrichr
abrichr merged commit 67ebec2 into main Jul 28, 2026
17 checks passed
@abrichr
abrichr deleted the agent/opaque-select-exact-label-20260728 branch July 28, 2026 09:11
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