Drive an implementation through the paired-session coordinator: independent PLAN review, EXEC implementation/review, adversarial gate, then finish, quality polish, docs and security up to operator acceptance. Trigger in exactly three cases: (1) the user explicitly asks for paired-session or names this explicit coordinator entry; (2) the review-loop entry hands off because .review-loop/config.md sets `entry: paired-session`; (3) the review-loop entry hands off because that key is absent (the default entry). Do not trigger on a bare review-loop request in any other case (key invalid, `legacy`, or /review-loop:legacy).
