Implement `/health` Endpoint for Server Health Checks

[kappsegla]

Implement /health Endpoint for Server Health Checks

Summary

Create a lightweight GET /health endpoint that returns a simple response indicating whether the server is running and able to handle requests.

Why This Is Needed

• Allows deployment platforms and load balancers to verify server availability
• Useful for uptime monitoring and automated health checks
• Provides a simple diagnostic tool during development
• Helps avoid false positives when the server is unresponsive or stuck

Requirements

• Add a new route: GET /health
• The endpoint should:
  • Return HTTP 200 OK when the server is operational
  • Respond with a small JSON object, for example:

    { "status": "ok" }

  • Or just a simple OK
  • Not require authentication
  • Execute quickly without performing heavy operations

Acceptance Criteria

• /health returns HTTP 200
• Response body contains a JSON object with a status field
• Endpoint is reachable when the server is running
• Endpoint is documented in README or API documentation

Optional Enhancements (Future Work)

• Include uptime or timestamp
• Include version/build metadata
• Add /ready and /live endpoints for more advanced orchestration
• Add checks for dependencies (database, cache, etc.)