feat: e2e full infrastructure stack (TLS + Valkey + NATS + S3)

[tgarciai]

Summary

E2E test validating all infrastructure transports working together in a single test run.

Layer	What it proves
TLS	All 9 HTTPS requests verified against CA
Valkey sessions	Session created and persisted
Valkey invocations	2 invocations retrievable by ID after execution
S3/MinIO	4 artifacts stored and retrievable via /invocations/{id}/artifacts
NATS + Outbox	6 domain events: session.created, 2× invocation.started, 2× invocation.completed, session.closed
Telemetry	Valkey backend active (runtime logs confirm)

Cluster evidence

Step 1: Subscribing to NATS workspace.events.>
OK Subscribed to workspace.events.>
Step 2: Creating session (Valkey-backed)
OK Session: session-0ab8511f2834ac68 (persisted in Valkey)
Step 3: Invoking fs.write_file (Valkey invocation store)
OK fs.write_file → inv-aa86fa2de58eedd4 (persisted in Valkey)
Step 4: Invoking fs.read_file (verify content round-trip)
OK fs.read_file → inv-9dce4f657d63dc43 (content match: True)
Step 5: GET /invocations/{id} (Valkey persistence proof)
OK   inv-aa86fa2de58e... → succeeded (from Valkey)
OK   inv-9dce4f657d63... → succeeded (from Valkey)
Step 6: GET /invocations/{id}/artifacts (S3 persistence)
OK   inv-aa86fa2de58e.../artifacts → 200 (2 artifacts)
OK   inv-9dce4f657d63.../artifacts → 200 (2 artifacts)
Step 7: Closing session
OK Session closed: 200
Step 8: Waiting for NATS events (outbox relay poll)
Step 9: Verifying NATS domain events
OK NATS events: 6 — session.created=yes, invocation.started=yes, invocation.completed=yes, session.closed=yes
OK Full Infra Stack PASSED

Test plan

• Ran on live cluster with TLS + Valkey + NATS + outbox + S3
• Pod Completed, job succeeded
• No sensitive data

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud