e2elisted

# AgentsMesh E2E Run the smallest real end-to-end test that proves the requested behavior, then expand coverage in proportion to the change. ## Invariants - Use the current worktree's generated `deploy/dev/.env`; never assume fixed ports or container names. - A UI requirement must be verified by a browser or app UI test. Do not replace it with a raw API request. - Start the development stack only when the selected suite needs it. Record whether this workflow started the stack before deciding whether to clean it. - Authentication uses Connect-RPC. Never restore the removed REST login route; read `references/connect-rpc.md` when testing auth or proxy routing. - Do not claim a suite passed unless its command completed successfully. - Preserve test artifacts and relevant service logs when a failure occurs. ## Workflow 1. Inspect the requested behavior and changed files. 2. Select the suite from `references/test-matrix.md`. Read the selected target's BUILD file, config, and nearby tests before running it. 3. Reuse a healthy existing stack. Otherwise start `//deploy/dev:up` for Web flows or `//deploy/dev:backend_only` when frontends are not required. 4. Load `deploy/dev/.env` with automatic export enabled so Bazel can forward the worktree-specific values: ```bash set -a source deploy/dev/.env set +a ``` 5. Run the narrowest relevant spec or test filter first. If it passes, run the owning target when the blast radius warrants it. 6. For UI b