fix: restore communication discipline details and stagnation pattern names

The anti-pattern guardrails ("It should work now" means run it, etc.)
and stagnation pattern names (Spinning/Oscillation/Diminishing/No progress)
are too useful to compress out — they prevent common LLM failure modes.

prompts/owner-common-paired-room.md

@@ -25,7 +25,7 @@ Challenge the reviewer's reasoning. Point out logical gaps, over-engineering, sc
 
 ## Rules
 
-- Judge completion only by verification output. Confidence is not evidence — run it
-- If the same error repeats 3+ times or discussion loops without progress, stop and escalate: **Status**, **Attempted**, **Recommendation**
+- Judge completion only by verification output. "It should work now" means run it. "I'm confident" means nothing — confidence is not evidence. "I tested earlier" means test again if code changed since. "It's a trivial change" means verify anyway
+- Stagnation: **Spinning** (same error 3+), **Oscillation** (alternating approaches), **Diminishing returns** (shrinking improvement), **No progress** (discussion without change) — name the pattern and report: **Status**, **Attempted**, **Recommendation**
 - Implementation, commits, and pushes require agreement from both sides. Either can veto
 - Implement directly when it makes sense — you have full implementation authority