os-sdlc recover 1/7: Dispatch#void! + voided status #392
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#392
Loading…
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?
Child of #332. Add VOIDED alongside PENDING/RETURNED in lib/os_sdlc/runner/dispatch.rb with a void! method. Tests assert voided rows no longer match pending_for and that status is explicit (no schema constraint enforces statuses).
Resolution
Done: Added VOIDED status constant and void! class method to lib/os_sdlc/runner/dispatch.rb, mirroring mark_returned; voided rows no longer match pending_for
Evidence: Commit
7ee87df; new tests/runner/dispatch_test.rb; full suite 884 runs 0 failures; rubocop cleanFollow-ups: Pending-only guard for void! is being decided in #396