- extend `_a0_connector` computer-use metadata handling to retain
`backend_id`, `backend_family`, `features`, and `support_reason` from the
CLI hello payload
- update `computer_use_remote` to prefer inline `png_base64` screenshots for
capture and auto-refresh flows, while keeping filesystem-path fallback for
migration/debug cases
- include backend information in status formatting so remote computer-use
sessions are easier to inspect across Wayland and Windows backends
- align the builtin Agent Zero plugin with the new multi-backend computer-use
transport used by `a0` 1.5
- replaced heavy CU instructions with a SKILL.md
## Summary
- include `exec_config` in `_a0_connector` `connector_hello`
- source execution timeouts and prompt/dialog patterns from `_code_execution` config
- make the connector advertise execution policy explicitly to the CLI
## Why
The CLI should not depend on a local Agent Zero Core checkout just to run `code_execution_remote`. On Windows this broke remote execution even when the connector was active, because the CLI could not see the container's internal Core tree. The backend already owns the execution policy, so it should send that contract directly.
## What changed
- add `_a0_connector.helpers.exec_config.build_exec_config()`
- read `_code_execution` settings/defaults through plugin config resolution
- return `exec_config` from `_a0_connector.api.ws_connector` during `connector_hello`
## Impact
- removes an implicit host-side Core dependency from the connector flow
- lets the CLI keep only platform-specific shell / TTY behavior locally
- aligns Linux and Windows behavior behind the same handshake contract
