os-sdlc recover 3/7: consistency check before re-emit #394
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#394
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. Depends on 2/7. Verify pending dispatch agent/brief matches what the ticket's current state would dispatch (dispatch rows carry no originating state). Mismatch -> refuse with report, never emit.
Resolution
Done: Added dispatch-state consistency check: RecoveryStatus now resolves via shared WedgeTarget; DispatchConsistency compares table.agent_for(current state) to pending row's agent; mismatch yields recovery_refused/dispatch_state_mismatch naming expected vs pending agent; consistent dispatch_summary carries consistent: true
Evidence: Commit
eb061e9; tests/runner/recovery_status_test.rb mismatch tests; full suite 898 runs 0 failures; rubocop cleanFollow-ups: Re-emit (#395) relies on dispatch != nil && consistent as its trust signal