Allow confirmed changes to in-progress route stops - #171
Merged
Conversation
Require an explicit warning acknowledgement before adding or removing stops from an in-progress child route while keeping route reversal, cross-route moves, and terminal routes locked. Constraint: Shopify source data remains read-only; only CLEVER route membership changes are allowed. Rejected: Reverting active routes to READY | It would conflict with live tracking and execution history. Confidence: high Scope-risk: moderate Directive: Keep the confirmation gate for all future in-progress membership mutations. Tested: npm test; npm run build; npm run typecheck; git diff --check Not-tested: Live embedded Shopify interaction before deployment
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
1 participant
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