Add built-in agent acceptance test and bounded local Hermes bridge #219

Goal

Make the MacBook OpenBot pilot usable in two verified steps:

1. Prove a shipped built-in OpenBot agent can complete a safe local test run.
2. Connect selected local Hermes agents to OpenBot through a bounded, explicit AG-UI adapter.

This is local pilot work only. Do not change ARIA/OpenClaw production, Teams production, customer data, or the existing OpenBot computer volumes.

Scope

Built-in agent acceptance test

• Add a deterministic test for the shipped General Assistant (or the smallest built-in agent path that exercises the real runtime contract).
• Cover the authenticated AG-UI request/response path and a safe smoke prompt with no corporate or customer data.
• Assert useful text is returned, structured content is rendered safely, and no secret/token/payload disclosure occurs.
• Keep the test runnable offline or against local services with an explicit smoke mode.

Local Hermes bridge

• Add a small, documented adapter that speaks AG-UI to OpenBot and invokes only an explicitly configured local Hermes profile/interface.
• Do not pass raw Hermes sessions, auth.json, .env, credential stores, home-directory mounts, Docker sockets, or unrestricted shell/computer access into OpenBot.
• Bind the bridge to loopback or the private Compose network only; fail closed when the allowlist, endpoint, or auth boundary is missing.
• Permit text-in/text-out first. No Hermes tools, MCP credentials, files, browser control, production systems, or customer data in this pilot.
• Use bounded request size, timeout, and concurrency limits; redact secrets and structured payloads from logs.
• Register the bridge-backed agents as OpenBot remote-ag-ui agents without storing their tokens in agent rows.
• Make the Hermes profile allowlist and display metadata deployment configuration, not user/request controlled.
• Add a health/readiness check that proves the configured Hermes interface is available without issuing a real business action.
• Document how to add/remove a local Hermes profile and how to run the smoke test.

Acceptance criteria

• Focused unit/integration tests pass for built-in-agent execution, bridge routing, allowlist enforcement, timeout/error handling, and redaction.
• A local smoke run proves the built-in OpenBot agent responds.
• A local smoke run proves at least one explicitly allowed Hermes profile responds through the bridge, or reports a concrete external blocker without weakening isolation.
• OpenBot UI/API remains loopback-only for this pilot and existing CA/TLS validation remains enabled.
• No secrets or raw Hermes session data are committed, logged, or returned.
• Evidence is posted here before merge.