odoo-pr-monitoring

odoo-pr-monitoring - the post-PR lifecycle owner (poller)

Role

Post-PR lifecycle owner. The plan's integrate node stops at "PR opened, link reported" (ONE PR per repo per run). monitor runs only when the user asked for the PR to be watched: a CI build runs for hours and every tick costs tokens; without that ask no loop, cron or wakeup reads the PR, and a later "how is the PR" is ONE read. monitor and merge are ordinary plan nodes (monitor depends_on integrate, merge depends_on monitor); this skill runs each time either is dispatched. Each poll tick reads once, classifies, and PARKS: emit a NEEDS_NEXT Continuation Contract naming this skill in next[]; a later /loop tick or /schedule cron re-invocation re-attaches via run-<id>.json. Once the watch classifies green + approved + mergeable, the monitor node reaches DONE; it never performs the merge.

monitor node:  poll (/loop | /schedule)
   -> any CI warning/error/fail -> odoo-debug (D3: root-cause) -> odoo-coding (fix)
        -> proposed re-push is human-gated (X2); max_review_rounds cap; exhaustion -> BLOCKED
   -> green + approved + mergeable -> `monitor` DONE
merge node:    present merge approval gate -> merge (git-ops) -> post-merge cleanup (git-ops)

Make no domain/code decision and run no git/GitHub op yourself: read PR state, merge and clean up via the git-toolkit:git-ops skill, route diagnosis to odoo-debug and fixes to odoo-coding. Every git mutation stays human-gated + worktree-only, including from an unattended cron poll.

Inputs - the PR handle (re-attachable across sessions)

On start, locate the PR by pointer (do NOT re-open or re-derive it):

• PR URL + branches - from the active run-<id>.json, which lives under the Tier-2 ISOLATE dir; resolve it via the resolve-capture-substitute protocol in ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md (captured path shown as <ISOLATE_DIR> below) - <ISOLATE_DIR>/run-<id>.json (the integrate node's produced carries the PR URL, the run-integration branch, the squashed SHA). A fresh session re-attaches by reading run-<id>.json. Surface the PR URL + poll state in the Continuation Contract produced, and write poll-state notes under <ISOLATE_DIR>/pr-monitoring/<id>.md.
• Direct user invocation - "watch PR #N" supplies the PR number/URL directly; no run file required.