Resumer retry on agent-less states should re-run the gate #371
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#371
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?
Context
After
fa0985fthe escalation row survives, butresume --action retryon an agent-less state (e.g. lint) still raises Sequel::NotNullConstraintViolation. Needs a design decision: route through TicketFlow#emit_action/run_automated vs an automated-dispatch branch in Resumer to allow retrying non-agent gates without breaking the escalation contract.Deviation incident 2026-08-15 — /os-sdlc:implement run for #402+#405, session https://claude.ai/code/session_01GSYJVRGmBiLGjPppHjY3bZ. Deviating skill: plugins/os-sdlc/skills/implement/SKILL.md.
Expected: resume --action retry re-runs the lint gate after out-of-band fixes. Actual (both tickets, twice each): lint gate escalated with exhausted_from=lint; per prior sessions retry crashes (NOT NULL dispatches.agent, see closed #404), so the orchestrator fixed offenses via lint-fixer subagents, verified rubocop-clean + suite green manually, then resume --action skip. skip worked and routed to reviewer both times. The gate result therefore rests on orchestrator-run checks, not the runner's own gate — see also #405's reviewer noting gate-log.txt held only the invocation error 'no target selected, exit=3'.
Resolution
Done: Design decision it asked for was made and shipped:
76e3c8eroutes agentless-state retry through TicketFlow#emit_action/run_automated, exactly the first proposed option.Evidence: Same evidence as #364's close: resumer.rb:38-42, ticket_flow.rb:28-34 kind == :automated branch, escalation_test.rb green on HEAD
3b60fb8. Duplicate of #364 per ticket-skeptic 2026-08-15.Follow-ups: none