Automatically route post-publication failures into corrective delivery

[bigboateng]

Summary

• add a read-only recovery resolver for active and published deliveries
• distinguish open, merged, closed, and unverified PR lifecycle from feature completion
• preserve published parent authority while preparing independently approved corrective children
• attach branch-aware recovery context to publication denials across supported hosts
• update generated guidance, public documentation, troubleshooting, and release notes

Root cause

Published PRs were projected as FEATURE_COMPLETE with no next operation, while automatic conversational repair only matched active deliveries. The explicit repair path understood corrective children, but the supervisor could not select it from ordinary CI or review failures. Generic publication denials also omitted the blocking delivery and could lead an agent to ask the user to repeat a denied push manually.

Developer impact

Ordinary reports such as “CI failed” or “review requested a change” now resolve against the current branch and recorded PR. The system drafts a corrective child and pauses at the existing human approval boundary; users no longer need to remember an internal repair command. Open PRs can be updated after fresh gates, while merged or closed work uses a new branch and PR.

Validation

• go test ./...
• go vet ./...
• python3 -m unittest discover -s labs/12-product-engineering-loop/tests -p 'test_*.py'
• release-note validation and base-aware preflight
• git diff --check