Opus fddc0a1226 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
2026-04-24 17:55:21 +02:00
2026-04-22 02:50:02 +02:00
2026-04-22 03:50:03 +02:00
2026-04-22 05:00:04 +02:00
2026-04-22 02:30:04 +02:00
2026-04-23 22:15:04 +02:00
2026-04-24 05:00:12 +02:00
2026-04-24 03:05:04 +02:00
2026-04-24 03:00:11 +02:00
2026-04-24 02:30:07 +02:00
2026-04-24 03:00:11 +02:00
2026-04-23 04:55:04 +02:00
2026-04-22 17:15:03 +02:00
2026-04-22 10:50:03 +02:00
Description
No description provided
4.5 GiB
Languages
HTML 57.3%
PHP 28.5%
JavaScript 6.2%
Shell 5.4%
Python 2.1%
Other 0.5%