loopx-pr-program

# LoopX PR Program Manage a delivery program as durable LoopX state instead of rebuilding a queue from chat memory. Keep source acquisition provider-local, normalize observations into one public contract, and write back only material transitions. ## Route The Request Use this workflow when the user asks to manage, prioritize, reconcile, document, or monitor several pull requests or merge requests. Route a deep review of each selected PR to `loopx-pr-review`. Route approval, comments, reruns, branch retargeting, closing, or merging to the normal provider-specific workflow and require the corresponding authority. Treat document maintenance and monitor creation as writes. A request to update the roadmap or keep monitoring the program authorizes those scoped writes; an ordinary status question remains read-only. ## Start From LoopX State Start or join the project goal before material work. Represent the program with one advancement todo for the current reconciliation and one `continuous_monitor` todo for recurring observation. Do not create one monitor todo per change request. Use a stable monitor identity: ```text task_class=continuous_monitor action_kind=pr_program_reconcile target_key=pr-program-<stable-program-id> cadence=<user cadence or 30m> ``` Preserve `claimed_by`, `last_checked_at`, `next_due_at`, `result_hash`, `consecutive_no_change`, and `material_change`. Quiet monitor polls keep liveness but do not count as delivery progress, rewrite roadmap documents, or ...