Before you start
Architecture knowledge; deployment-specific access is required for any headless exercise.
01Understand the browser path
The application bridge invokes a compiled WebAssembly runtime and services asynchronous requests through workers. The repository documents a Rust execution core. External models and integrations can still require network access.
02Separate local execution from privacy claims
Browser-local orchestration does not mean offline AI, no authentication, or no data leaving the device. Inspect each provider, file and API path when evaluating deployment.
03Qualify headless availability
The product materials describe supported headless configurations, but a runnable headless CLI was not available for verification in this academy build. No installation command, webhook recipe or parity claim is presented as tested here.
04Define a deployment acceptance test
For your actual runner, verify credentials, input delivery, output persistence, human-decision handling, recovery and side effects. Confirm supported node variants and operating responsibilities before assuming a browser workflow will run unchanged.
If the result is wrong
Do not infer generally available headless parity from a conceptual architecture diagram.