1ae051ec95
The staging E2E suite already grep's for 5 known regression patterns in the A2A response (hermes-agent 401, model_not_found, Encrypted content, Unknown provider, hermes-agent unreachable). The comment block at lines 386-395 lists "Invalid API key" as the signal for the CP #238 boot-event 401 race + stale OPENAI_API_KEY paths, but the explicit grep was never added — meaning a regression in that class would slip through the generic `error|exception` catch-all. Closes the gap with one specific-pattern check that fails loud with the relevant bug references in the message. Verified `bash -n` clean; pre-existing shellcheck SC2015 at line 88 is unrelated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| _extract_token.py | ||
| _lib.sh | ||
| STAGING_SAAS_E2E.md | ||
| test_a2a_e2e.sh | ||
| test_activity_e2e.sh | ||
| test_api.sh | ||
| test_claude_code_e2e.sh | ||
| test_comprehensive_e2e.sh | ||
| test_dev_mode.sh | ||
| test_saas_tenant.sh | ||
| test_staging_full_saas.sh | ||