sprint_closelisted

# sprint_close — route the terminal boundary Use as a closeout router, not as a second operating workflow. The Reviewer owns conformance and final-report judgment; the Planner executes Reviewer control decisions; clean conformance closes atomically; the FnB owns explicit fallback and follow-up disposition. Use the simplest path supported by current durable state. Treat authority, lifecycle preconditions, durable writes, and typed handoffs as hard boundaries; use judgment within them. Repeat a read only when later activity could have changed it or the next command requires live revalidation. ## Route the entry - **Selected conformance Reviewer receives `sprint.delivery_terminal`.** Confirm the notification's owner shell and generation match the current Sprint. Load `sprint_rev` and follow **Delivery-terminal closeout**. Inspect the Sprint inbox once, compile bounded evidence, and choose between in-Sprint re-entry, abort, or the atomic clean `record-conformance` path. Any other Reviewer records no conformance. The Planner does not initiate this pass. - **Planner receives a Sprint-scoped Reviewer decision.** Load `sprint_pln` and follow **Reviewer decision actions**. Inspect and handle the durable inbox message once, then execute the exact requested transition without re-adjudicating it. - **Planner receives an engine-wide completion or cleanup receipt.** Load `sprint_pln` and follow **Conclude or abort**. Inspect the self-contained receipt and terminal S