os-sdlc recover 1/7: Dispatch#void! + voided status #392

Closed
opened 2026-08-15 10:44:21 +00:00 by jared · 1 comment
Owner

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).

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).
Author
Owner

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 clean

Follow-ups: Pending-only guard for void! is being decided in #396

## 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 clean **Follow-ups:** Pending-only guard for void! is being decided in #396
jared closed this issue 2026-08-15 10:52:03 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jared/cc-os#392
No description provided.