Browser Automation Orchestrator

The single entry skill for browser and UI automation work. It places the task on the surface × session-model map — what are you driving (the web/DOM layer vs the native OS UI layer) and how long does the driver live (one-shot vs persistent) — and delegates to one of the specialist spokes. The cross-cutting model every spoke shares — the two automation surfaces, the session lifecycle, the selector/targeting strategy, and the debug-first evidence rule — lives in browser-automation-core; read it before choosing an engine or claiming a UI "works".

Cluster map (spoke → role)