Split planning.mjs by effect domain #166
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#166
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: deep dive, broader design B4; general scan recommendation 9
Verdict: DISPUTE - preference, closing
Claim as reviewed
planning.mjsowns state, UAT, audits, overlaps, leases, detection, tracing, renumbering, capture and milestone pruning. Module size increases coupling and makes security properties harder to audit; split into domain modules behind the current CLI facade.At HEAD
f354864(v3.3.0)The size is accurate -
cadence-core/bin/planning.mjsis 3,705 lines at HEAD.Note
No defect in this batch is caused by the file's size, and none of the fixes needs the split to land. A 3,700-line move touching every seam is new review surface bought with no failing behaviour to point at.
Closed as a preference. Reopen with a specific defect the layout caused, and it becomes plannable.