follow writ#19: n/a is a finding, compare loses a broken law, NOT VALID declined - #13
Merged
Merged
Conversation
…w, NOT VALID declined Assertions and READMEs that recorded the old behaviour now record the new: - agent-guardrails: the cheat that deletes `out` makes check exit 1 (was 0); - compare reports a law declared in both and broken in the new model as LOST with its route (rename-a-column's "the verb that does NOT catch it", drop, add-required, expense-approval, entitlement-problems, git-compare's one-capture); the migration READMEs no longer say compare is the wrong gate; - add-a-foreign-key: writ sql declines NOT VALID (exit 1 under --strict) and VALIDATE CONSTRAINT, each with its reason. Needs writ with branch writ-gaps; 306 checks against it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Follows writ-lang/writ#19. Merge after it. Stacked on #12 (base
db-migration-problems-2).The assertions and READMEs that recorded writ's old behaviour now record the new:
agent-guardrails: the cheat that deletes the
outarrow now makeswrit checkexit 1 (it was 0). The README says this scenario is how that was found.comparereports a law declared in both models and broken in the new one asLOST, with its route. Affected:two-for-large);one-capture.The migration READMEs now say both gates catch it, rather than "compare is the wrong gate".
add-a-foreign-key:
writ sqldeclinesNOT VALID(exit 1 under--strict) andVALIDATE CONSTRAINT, each with its reason../run-tests.sh allagainst writ atwrit-gaps: 306 checks, 0 failed. Against the released 0.3.0 it fails those seven assertions, which is the point.🤖 Generated with Claude Code