EnvReplay: Catch the Deployment Failure CI Missed

A passing CI run does not always mean a service will work after deployment. CI may test an application at its root path while the deployed service runs behind a path prefix. Developers then face a 404 that their existing tests never exercised. EnvReplay gives developers a repeatable way to investigate that gap. Its single, concrete scenario is a health check: CI successfully serves /api/health, but deployment exposes the application under /service, where /service/api/health initially returns 404. A developer can run the replay, see the failing request and its environment context, inspect the path mismatch, and run the check again after the repair. IBM Bob is part of the repository investigation and development workflow. The project also provides executable replay checks and recorded evidence so judges can inspect what Bob contributed and independently verify the failure and result. The product experience presents the sequence clearly: CI passes, deployment fails, the cause becomes visible, and the repaired route passes the deployment check. EnvReplay is designed for developers, QA engineers, and teams troubleshooting differences between CI and deployed environments. Its value is a reproducible explanation and a checkable repair for a failure that a green CI badge missed.