fix(e2e): clarify EIC diagnose SG guidance #1664
Reference in New Issue
Block a user
Delete Branch "fix/e2e-eic-diagnostic-sg"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
MOLECULE_EIC_ENDPOINT_SG_ID.Why
The live staging EIC endpoint SG is resolved from AWS/Railway config. A stale hard-coded SG in the failure text sent investigation toward a deleted security group even after CP was correctly wiring the live endpoint SG.
SOP
terminal-reachableand Files API EIC write HTTP 200 after Railway env fix; later A2A 503 was expected because the manual probe intentionally omitted LLM credentials.EIC_ENDPOINT_SG_IDname while CP uses canonicalMOLECULE_EIC_ENDPOINT_SG_ID; the repo diagnostic also hard-coded a deleted SG.Verification
bash -n tests/e2e/test_staging_full_saas.shshellcheck -x tests/e2e/test_staging_full_saas.shgit diff --checkterminal-reachableand Files API EIC write HTTP 200; teardown verified no EC2 leak.Approved for CI/E2E diagnostic cleanup. Scope is a stale failure message only; live EIC path was verified separately.
Approved for CI/E2E diagnostic cleanup. Scope is a stale failure message only; live EIC path was verified separately.
/sop-ack 1 2 3 4 5 6 7
/sop-ack comprehensive-testing local-postgres-e2e staging-smoke root-cause five-axis-review no-backwards-compat memory-consulted
/sop-ack comprehensive-testing local-postgres-e2e staging-smoke root-cause five-axis-review no-backwards-compat memory-consulted
/sop-ack local-postgres-e2e staging-smoke root-cause five-axis-review no-backwards-compat memory-consulted
/sop-ack 3 4 5 6 7
/sop-ack 4
/sop-ack 5
/sop-ack 6
/sop-ack 7