Adam Moussa
d12880ed09
The resume-followup notifier mislabeled build/verify-stage tasks. Two cases, both surfaced live while smoke-testing the #60 builder fix: 1. AWAITING CI (in-progress): the VERIFY node suspends via interrupt() for the async CI-wait. Its interrupt payload is not question-shaped, so pending_question() returns None and the notifier treated the still-suspended task as a settled PARK -> posted '⚠️ PARKED ... the plan could not be auto-approved ... re-assign' for a task that had actually approved the plan, built a diff, and dispatched it to CI. Now detect the suspend (graph interrupted + dispatched run_id + a built diff) and post an honest 'diff built and dispatched to CI (run X); awaiting verification' notice. 2. SETTLED build/verify PARK: phase inference keyed off review_verdicts and reported 'review' for a task that reached verify; the copy hardcoded 'the plan could not be auto-approved'. Now a built diff (candidate_diff/diff_hash) makes the inferred phase 'verify' and the copy reflect a verification/CI-gate failure, surfacing the CI conclusion via _summarize_build_blocker. Plan/review escalation parks (no candidate_diff) are unchanged. - coordinator.py: _post_resume_followups awaiting-CI branch + build-aware phase inference + build-aware PARKED copy; add _summarize_build_blocker. - tests: built-park reports verify + CI conclusion (not auto-approve copy); awaiting-CI suspend reports in-progress, not parked. |
||
|---|---|---|
| .. | ||
| db | ||
| nodes | ||
| transport | ||
| __init__.py | ||
| api.py | ||
| billing.py | ||
| ci_fetcher.py | ||
| ci_gate.py | ||
| ci_watcher.py | ||
| coordinator.py | ||
| dashboard.py | ||
| deadline_timer.py | ||
| decisions.py | ||
| dispatcher.py | ||
| draft_pr_monitor.py | ||
| graph.py | ||
| invoker.py | ||
| invoker_multi.py | ||
| ledger.py | ||
| operator_cli.py | ||
| recovery.py | ||
| responder.py | ||
| resume_worker.py | ||
| state_store.py | ||
| status_page.py | ||
| task_model.py | ||
| topology.py | ||