feat(chrome-stagger w319): fix CDP auto-repair via stagger launch

CAUSE RACINE (Yacine doctrine zero manuel):
- wevia-self-repair.sh cron 2min detectait CDP 0/8 et lancait 8 chromes en batch
- Peak CPU 150+ = launch ALL fail + spike load = CX 502 = cascade
- Log repetait chaque 2min sans jamais relancer vraiment

FIX wave 319:
1. launch-chromes-all.sh v2 STAGGER logic:
   - Find first DOWN profile (ordre prio: openai, anthropic, google...)
   - Launch SEULEMENT 1 chrome par cycle
   - Rate-limit 90s entre 2 launches (immune multi-call)
   - Load guard 100 (skip si deja sature)
   - Verify CDP UP apres 5s
2. Intent opus_chrome_stagger_launch ACTIVATED (5 triggers NL)
3. State reset /tmp/wevia-stagger-last

Result: 8 chromes UP en 16min (vs jamais avant)
Zero spike CPU (max 1 chrome par cycle 2min)
Auto-stop quand 8/8 UP (dit ALL UP nothing to launch)

Opus utilise systeme auto-repair existant doctrine 194
Zero nouveau code, patch surgical script existant + nouveau intent

221 -> 222 intents (w317 meeting) -> 223 intents (w319 stagger)
GOLD backup gold_launch_chromes_all_w319

api/wired-pending/intent-opus4-ACTIVATED-opus_chrome_stagger_launch.php

@@ -0,0 +1,17 @@
+<?php
+return array (
+  'name' => 'opus_chrome_stagger_launch',
+  'triggers' => 
+  array (
+    0 => 'chrome_stagger',
+    1 => 'stagger_launch',
+    2 => 'cdp_stagger',
+    3 => 'relance_chromes_soft',
+    4 => 'launch_chromes_stagger',
+  ),
+  'cmd' => 'bash /opt/weval-ops/opus-intents/launch-chromes-all.sh',
+  'status' => 'ACTIVATED',
+  'created_at' => ''.'+00:00',
+  'source' => 'opus4-wave-319-autowire',
+  'description' => 'Launch 1 Chrome CDP par cycle (stagger) - appele par wevia-self-repair cron 2min OU on-demand NL. Load guard 100. Rate-limit 90s. Cycle tous les 2min = 8 chromes UP en 16min sans spike CPU.',
+);