P0: harden FAT TCS / protection-27 smart finding - #146
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This was referenced Aug 13, 2026
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.
P0 scope
This PR hardens FAT signal finding only. It intentionally does not include the multi-IED or fascia/toolbar UX work.
Verified baseline
58d4b4b.VI3p1_27Undervoltage1/PTRC1.Opreferences, plus a legacy field row where 27-1 degraded to generic.Op.generalwhile 27-2 retained its full reference.Changes
27Undervoltage/PTUVIEC identities — no fuzzy text similarity;$ST$spelling, 59/67 sibling collision protection, weak 27-1 + strong 27-2 sibling elimination, ambiguity blocking, and prepared-reference live binding.Safety intent
The matcher remains conservative: exact/canonical references win, TCS exact-leaf behavior remains intact, and protection-27 fallback cannot select when evidence still leaves more than one candidate.
Please gate merge on the existing ARSAS build/test workflows.