Cockpit + CDP + Edge + OWA stack

The collision

OWA logic duplicated in cockpit connectors, wrong browser (Chrome vs Edge), CDP port collisions with A11y Studio, or M365 sync attempted without Edge/Playwright path.

How to choose

1) New OWA/Teams read behavior? → extend lcdl task + contract; cockpit bridge wires run_task only. 2) Session lease / attach owner? → cdp (FORGE_CDP_MANAGER_URL, typically :18770). 3) Operator browser? → Edge with CDP; COCKPIT_EDGE_FOCUS_EDGE for focus emulation per lcdl docs. 4) EML on disk / manifest upgrades? → cockpit eml_paths + cockpit_data_manifest (not lcdl layout). 5) Start cockpit? → Electron via start-cockpit.sh COCKPIT_PORT=9775 — not browser unless asked.

Using several at once

lcdl: playwright atoms. cdp: leases. cockpit: SQLite, UI, manifest. OWA/EML: mail path. fa-acc-leo may share cdp manager — coordinate surface ids. Fleet memory via fccmem optional pulse path.

Terms covered

• cockpit
• fccw
• cdp
• lcdl
• OWA
• EML
• fa-acc-leo
• fccmem

Examples from chat / plan.md

Outlook search-day stall → outlook-mail-preflight via cdp manager with COCKPIT_SYNC_RUN_ID bound session_id.

User: "start cockpit" → ./scripts/start-cockpit.sh background Electron; M365 sync remains Edge unless CDP remote attach configured.

Bridge page cockpit-cdp-edge — read when multiple abbreviations appear in one sentence.