pr-delivery-loop

# PR Delivery Loop This file contains the operating rules. [Rationale and examples](references/rationale.md) are optional reading for understanding a failure or the reasons behind a rule; do not load them routinely. They introduce no additional delivery gates. ## Ownership and distribution - The current user-started session is the **orchestrator**. A delegated lane's orchestrator is its dispatching session/callback target. Authority is **user > orchestrator > this standard**. Never delegate final review, orchestration, or merge approval to a newly spawned agent. - The orchestrator decides clear, reversible, contract-preserving scope changes. Ask the user only for a major trade-off, irreversible risk, or genuinely ambiguous direction. A lane reports cross-scope gaps instead of editing peers. - Avibe's `.agents/skills/pr-delivery-loop/` is canonical; the project-level entry links to it. After canonical review passes, sync the **whole maintained package**, including references, byte-for-byte to each repository mirror. Inspect companion guidance and preserve unrelated files and edits. - `background-watch-hook` owns managed waits, waiter scripts, cursor mechanics, retry/settle/filter behavior, and delivery acknowledgement. Load that skill before a managed wait. If unavailable, report the environment blocker; do not vendor or reimplement it in a repository. This skill owns delivery policy. ## 1. Scope, contracts, and implementation - Continue an assigned ...