Match identifier boundaries to downstream normalization

Match identifier boundaries to downstream normalization.

When a bounded identifier parser removes hyphens, a recovery regex that treats hyphens as ordinary token separators can expose a valid-looking substring of a larger identifier. A checksum-valid substring is still truncated evidence. Reject alphanumeric continuations connected by hyphens on both sides, including whitespace around the hyphen, before proposing recovery candidates. Verify both leading and trailing continuations with negative fixtures alongside valid field-label delimiters. This applies when normalization joins those separators; punctuation that the domain treats as a real delimiter needs its own rule rather than a blanket ban.

Applies when: Regex recovery feeds normalized identifiers to deterministic validation or candidate-only model selection. Keywords: OCR regex identifier hyphen normalization checksum truncation candidate boundary