v1.4.1: two internally-inconsistent contracts, closed by subtraction #71
No reviewers
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence#71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "cadence/v1.4.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Patch cycle. Two small contract defects, both fixed by deleting rather than wiring.
cad-executorrequired a terminal success-criteria check whose output the same contract gave nowhere to put, and whichexecute.mdnever consumed.goal_checkalready redoes it one step later with the full phase diff in view. Deleted. The per-task predict-then-verify at process step 2 is untouched.conventions.mdclaimed "every skill and workflow follows" while being@-included by exactly one skill and named in prose by 18 others. Header now states its real reach. Including it everywhere was the rejected alternative: it spends resident context in every session on rules most invocations never need.Plus the version bump and CHANGELOG entry.
Verification: 727 tests pass,
tsc -p tsconfig.ci.jsonclean,self-verifyreturnsok:truewith no problems.Closes #65
Closes #67