guide: audit-loop ownership + PM-notify-on-4-triggers + drop FINISHED banner + 5min/10min rename

Elazar 2026-07-13: PM should not receive per-round coder<->audit updates (blocked/corrected/re-sent/re-passed) - only final state or a real escalation. NEW GUIDE RULE (append, ~rule 34): 'AUDIT-LOOP OWNERSHIP: the coder owns the coder<->audit fix/re-audit loop. Do NOT send the PM per-round updates (audit blocked / corrected / re-sent / re-passed). Notify the PM ONLY when: (1) audit PASSes and the work is ready to close; (2) audit surfaces a SCOPE-CHANGING issue needing a PM decision; (3) work is BLOCKED and PM action is required; (4) the planned solution, risk, release, or acceptance criteria MATERIALLY change. The closing PM update carries only: work item, high-level outcome, validation status, release/version, remaining risk. Do NOT send separate clear-to-close / FINISHED-banner messages - DONE + audit PASS + live version imply closure.' ALSO: guide rule 23 human-facing rename '300s (default)'->'5 min', '600s'->'10 min' (keep the env-var names). Rides the same head+bounce as VENUS-225 to save a cold-start announce (Elazar flagged bounce-announce spam). coder implements guide text, audit reviews, PM bounces.