Repository navigation
docs(agents): feed every edge-case fix back into DuckShop - #1266
Merged
Merged
Conversation
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.
Why
Edge cases found by bug fixes, reviews and recorded hazards were covered in isolated tests but never fed back into DuckShop, the project meant to stress the compiler, Rules, unit tests, scenarios and Snowflake translation together.
Changes
AGENTS.mdgains a DuckShop Edge Cases section: a fix that involves a project shape, data value or lifecycle sequence adds a matching synthetic case to DuckShop's edge-case area in the same change, or the pull request says why it does not apply.Verification