v4.4.0 - Code-Owner Fallback for Failed Babysits
Why This Matters
When a default babysitter run fails, oh-my-pr can now make a bounded second attempt as the PR code owner instead of leaving the workflow stuck. This gives operators a better chance of getting review feedback handled, verified, committed, and pushed without manual intervention.
Detailed Changes
- PR #156 adds a 30-minute code-owner fallback for failed babysitter runs outside recovery or forced-prompt mode.
- The fallback prepares an isolated app-owned worktree and runs the resolved coding agent there with current PR context.
- The fallback agent can inspect GitHub review threads, PR comments, and failing checks, then reply, resolve handled conversations, commit changes, and push back to the PR branch.
- Run records now capture clear code-owner fallback phases and metadata for preparing, running, completed, and failed states.
- Documentation now explains the fallback behavior and how agent selection applies to these recovery runs.