fix(health): rebuild readiness hardening on current main

[seonghobae]

Controlled current-main replacement for #70

PR #70 contains a valuable /healthz hardening line but has accumulated a long conflicted history. Fresh comparison against protected main 3e029d8d38032eaffa60bd95026b7a05839691fa shows that since #70's merge base, protected main changed only one of #70's 19 paths (CHANGELOG.md). The remaining health implementation/tests/docs are path-disjoint from intervening protected work.

This replacement starts from that exact protected head and follows a new RED → GREEN cycle rather than transferring old evidence.

Current RED

Head 3cdf922e5bf963e88290aaeebf7b8de5438d3998 adds one focused regression proving PostgreSQL readiness values must be exact booleans and malformed truthy strings such as "false" must not become a healthy local/public result. Protected main currently truth-coerces database values with bool(is_ready) and does not expose the required bounded public-report boundary, so production code is intentionally unchanged at this head.

After exact RED is observed, the smallest root-cause repair will be composed on this same branch. The broader #70 result will only be replayed where current-main path identity proves it safe; CHANGELOG.md will be composed deliberately from current protected content.

No #70 checks, reviews, approvals, or stale-base evidence transfer. No force-push, destructive rebase, gate weakening, central dependency workaround, or release action is used.

Merge boundary

Keep Draft until the current-main replacement reaches GREEN, full exact-head CI/security/coverage/review evidence is terminal-success, review threads are resolved, and live rules are satisfied on an unchanged head. Close #70 as superseded only after unique-work preservation is proven on this replacement.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6f696659-b066-4d49-a97d-48fd41c28e57

📥 Commits

Reviewing files that changed from the base of the PR and between 6c88490 and a57fe22.

📒 Files selected for processing (2)

• pg_llm_batch/health.py
• tests/test_health_database_boolean_boundary.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}