[shrsv]

Inlines the trivial healthcheck boolean directly rather than calling through Healthy(), ahead of a bigger health-check rework.

[livereviewbot]

LiveReview automated review

Scanned 1 changed file (+4/-1).

🟡 Warning — Maintainability (main.go:14): the health check logic is now duplicated between main.go and internal.Healthy() — the two will drift the moment either one gains real dependency checks. Consider calling internal.Healthy() instead of inlining the boolean.

[livereviewbot]

Auto-approve policy evaluation

Stage	Result
Eligibility	✅ pass
LLM classification (refactor-only, confidence 9)	✅ pass
Findings	1x warning / maintainability
Risk score vs. threshold	✅ pass -- a single warning in a low-weight category doesn't move the score past cutoff

Verdict: AUTO-APPROVED. Contrast with the critical-severity scenarios above: maintainability is a real finding worth leaving as feedback (and it is, in the review comment), but at warning severity it isn't treated as a blocking risk signal on its own. Auto-approve still posts the finding -- it just doesn't hold the PR for it.

[livereviewbot]

Auto-approve policy verdict: APPROVED. One warning/maintainability finding is noted but doesn't block -- low-weight category, non-critical severity.