Repository navigation
Harden guardrail routing and imported pricing - #8
Merged
Merged
Conversation
Require an explicit route for branching guardrails and flag invalid routing in analysis. Ask for confirmation before importing editable catalog or per-node prices; preserve locally saved overrides. Core tests: 34 passed locally. Browser tests pending; do not merge until validation is complete. Signed-off-by: Jordi Garcia Castillon <gcjordi@hotmail.com>
Signed-off-by: Jordi Garcia Castillon <gcjordi@hotmail.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.
Summary
Validation
Scope
The change is confined to the analyzer, importer, model validation, simulator, local storage validation, and regression tests. No schema version or external dependency changes.