QA: exhaustive fhEVM Bun CLI test report for PR #1986

Run 40 scenarios (S01-S40) testing the Bun CLI from
codex/fhevm-orchestration-parity-refactor against all 5
personas (new dev, dapp dev, infra/telemetry, CI operator,
multi-stack user).

Key findings:
- CLI uses deploy/clean (not up/down as spec assumed)
- No trace subcommand or --no-tracing flag exists
- --network testnet/mainnet Grafana scrape needs --no-sandbox
- FHEVM_DOCKER_PROJECT rejects uppercase (Docker Compose rule)
- Argument parsing, validation, resume logic all work correctly
- Clean operations are idempotent and project-scoped
- 5-cycle restart loop is deterministic with no leaks

Verdict: BLOCKED on command naming parity and missing trace
subcommand; CLI logic itself is architecturally sound.

https://claude.ai/code/session_011ktTrkokU6NHgPsiipatnb

Author: claude

test-suite/fhevm/artifacts/S01.docker_network_after.txt

@@ -0,0 +1,3 @@
+NETWORK ID     NAME      DRIVER    SCOPE
+26ccf6ddda2e   host      host      local
+d8ac6a46cc77   none      null      local

test-suite/fhevm/artifacts/S01.docker_network_before.txt

@@ -0,0 +1,3 @@
+NETWORK ID     NAME      DRIVER    SCOPE
+26ccf6ddda2e   host      host      local
+d8ac6a46cc77   none      null      local

test-suite/fhevm/artifacts/S01.docker_ps_after.txt

@@ -0,0 +1 @@
+CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

test-suite/fhevm/artifacts/S01.docker_ps_before.txt

@@ -0,0 +1 @@
+CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

test-suite/fhevm/artifacts/S01.docker_volume_after.txt

@@ -0,0 +1 @@
+DRIVER    VOLUME NAME

test-suite/fhevm/artifacts/S01.docker_volume_before.txt

@@ -0,0 +1 @@
+DRIVER    VOLUME NAME

test-suite/fhevm/artifacts/S01.notes.txt

@@ -0,0 +1,9 @@
+S01: help/discoverability
+- bun run help: PASS - shows full usage including deploy, clean, pause, unpause, test, upgrade, logs, telemetry-smoke
+- deploy --help: PASS - shows help (recognizes --help flag)
+- clean --help: PASS - shows help (recognizes --help flag)
+- trace --help: FAIL - 'trace' is not a recognized command (expected by task spec but NOT implemented in CLI)
+- NOTE: CLI uses 'deploy' not 'up', 'clean' not 'down'. No 'trace' subcommand exists.
+- NOTE: '--no-tracing' flag does not exist in deploy args parser.
+- deploy/clean/telemetry-smoke commands are documented.
+- --strict-otel and --telemetry-smoke documented.

test-suite/fhevm/artifacts/S02.docker_network_after.txt

@@ -0,0 +1,3 @@
+NETWORK ID     NAME      DRIVER    SCOPE
+26ccf6ddda2e   host      host      local
+d8ac6a46cc77   none      null      local

test-suite/fhevm/artifacts/S02.docker_network_before.txt

@@ -0,0 +1,3 @@
+NETWORK ID     NAME      DRIVER    SCOPE
+26ccf6ddda2e   host      host      local
+d8ac6a46cc77   none      null      local

test-suite/fhevm/artifacts/S02.docker_ps_after.txt

@@ -0,0 +1 @@
+CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES