akka-reliabilitylisted

## User Input You **MUST** consider the user input before proceeding (if not empty). If the input contains the word **"remove"**, execute the **Remove Workflow**. Otherwise, execute the **Attach Workflow**. ## Required MCP Capabilities This command requires the following MCP tools. If any are unavailable, stop and tell the user to update the Akka CLI and restart Claude Code. - **Local development**: `akka_local_start`, `akka_local_run_service`, `akka_local_cluster_status`, `akka_local_status` - **Service introspection**: `akka_backoffice_list_components`, `akka_backoffice_discovery` ## Purpose This command sets up resilience testing for an Akka service. It discovers the service's endpoints at runtime via backoffice MCP tools and writes a `.akka/reliability.yml` config file. The daemon (port 9889) reads this config and serves a self-contained testing dashboard — no code is generated in the user's project. Two modes: - **Attach** (default): ensure cluster is running, discover endpoints, write config, report dashboard URL - **Remove**: delete `.akka/reliability.yml` (and any legacy artifacts) The dashboard is served by the daemon at `http://localhost:9889/resilience/` and provides: - Single-shot READ/WRITE operations against the service - Burst load testing with configurable duration, interval, and read ratio - Real-time latency chart and transaction log via SSE - Cluster node management (stop/start nodes 2–3 to test failover) --- ## Attach Workflow ### Step 0 — E