WA-VERIFY-025: Add docker services health-check script (ES/Mongo/Redis)

[kitcommerce]

Summary

Local test runs require Docker services (Elasticsearch, MongoDB, Redis). We routinely lose time when one service is missing or unhealthy.

Objective

Add a lightweight health-check script that confirms required docker-compose services are running and reachable before tests.

Acceptance Criteria

• Add script/docker_services_health (name flexible) that:
  • Checks docker ps for the expected service containers (mongo/redis/elasticsearch)
  • Prints a short PASS/FAIL summary
  • Includes a hint to start services (e.g. docker compose up -d <services>) and references required env vars if relevant
  • Exits non-zero when any required service is missing
• Script is safe to run from repo root

Verification Plan

• Stop one container → script should FAIL and name the missing service
• Start all containers → script should PASS

Client Impact

None (developer tooling).

[kitcommerce]

Dispatcher: picking this up now. Spawning an implementer to add a safe docker-services health check script from repo root. PR will target and include a Client impact section.

[kitcommerce]

(fix) Prior comment accidentally executed shell backticks on my side; intended text: PR will target the next branch.

[kitcommerce]

Opened PR: #863

[kitcommerce]

Changes requested

CI is failing fast across most jobs on PR #863. Also, this PR currently includes both the docker services health-check and the CI system prerequisites script/workflow changes, but those belong to separate issues.

Requested fixes

1. Scope PR Add docker services health-check script #863 to issue WA-VERIFY-025: Add docker services health-check script (ES/Mongo/Redis) #860 only

   • Keep: script/docker_services_health
   • Remove from PR Add docker services health-check script #863: script/system_prereqs and .github/workflows/ci.yml changes
   • Rationale: issue WA-CI-010: Script system prerequisites for tests + reuse in CI workflow #859 already has PR WA-CI-010: Script CI system prerequisites #864 for system prerequisites/CI wiring; we should avoid duplicate/conflicting changes.

2. Re-run CI and confirm it no longer fails during the prerequisites step.

Once PR #863 is scoped correctly and CI is green, we can re-enter review (labels will be reset to status:ready-for-review).