METHOD described the retired dispatch-time risk floor #149
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
external-review
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence-archived#149
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Source: strict re-review C-09 (reviewed against v3.2.0)
Verdict: FIXED in v3.3.0 - closing
Claim as reviewed
METHOD still describes a retired dispatch-time risk/stakes floor, so current docs describe a mechanism current code removed.
At HEAD
f354864(v3.3.0)True when reviewed. Closed by v3.3.0, whose changelog names it: "
METHOD.mdandINTERNALS.mdstill described the dispatch-time risk floor and its per-surface waivers, both retired in v2.7.0".Current text is a retirement notice, not a description:
METHOD.md:420-422- "Detection sets no floor. What a plan declares raises no level: thestakesyou set is the whole of it. The dispatch-time detector ... were both cut in v2.7.0".cadence-core/bin/route.mjs:62-76agrees.Note
The review targeted commit
81bdb5d4fcon the v3.2.0 tree, one milestone behind HEAD.