monitorlisted

Discover the canonical task first, then run one bounded reconciliation sweep: ```console <PLUGIN_ROOT>/scripts/python <PLUGIN_ROOT>/scripts/run_task.py list <PLUGIN_ROOT>/scripts/python <PLUGIN_ROOT>/scripts/run_task.py run pr-lifecycle-reconcile . --report ``` Read the JSON report as follows: - `pull_requests` is every local branch with a PR/MR, including branches with no checkout; - `checkout` is `primary`, `managed`, `external`, or `null`; - `changes` records newly discovered PRs/MRs and authoritative state transitions; - `actions` records completed or deferred lifecycle reactions and their reason; - a false `updated` field or repo-level `error` means that source was not refreshed, so do not infer absence or authorize cleanup from stale data. Never pass `--loop` from a skill or Scheduled task. Looping is only the Claude native-monitor adapter; task discovery, one-shot behavior, report shape, and reconciliation policy are shared. Codex plugins cannot register a Scheduled task during installation. The plugin's Codex SessionStart and PostToolUse hooks therefore provide a throttled, non-blocking, repo-level opportunistic trigger for this same one-shot task. Treat it as an active-use fallback, not a durable timer: it cannot run while Codex has no lifecycle events. When the user asks to monitor continuously under Codex, use the native Scheduled-task capability instead of a daemon. Create or update a project-scoped task with the requested cadence; when none is given, use