release-readiness-reviewlisted

# Release Readiness Review This skill owns the `review it` command. The reviewer's job is to try to disprove readiness, not confirm the implementer's narrative. ## Independence Prefer a fresh/context-isolated execution when available. Start from the issue/acceptance contract, current candidate diff/head, repository architecture/instructions, and evidence the reviewer chooses to inspect. Do not treat the implementer's reasoning, claimed root cause, or green tests as proof. Before reading the implementation in detail, independently restate the intended observable outcome, actor/resource/authority, and important non-goals. If that contract is wrong or incomplete, report it rather than reviewing the wrong solution more carefully. ## Adversarial review Inspect only areas relevant to the change, but trace the real journey far enough to challenge the selected boundary: - complete user/runtime path and affected change surfaces; - sibling/provider/caller implementations of the same invariant; - production-shaped external contract when local simulation cannot prove it; - persistence, process identity, PATH/env/executable/service, installation, restart, and reconciliation where affected; - security/identity/credential/permission path: `actor -> authentication -> selection -> durable state -> credential -> target -> operation`; - incorrect product assumptions, unintended scope expansion, weakened compatibility, or hidden coupling. For persistent state, startup, provisioning, de