Separate readiness and liveness probe semantics

[Akatenvictor]

Problem / Context

A single /health endpoint conflates "process is alive" with "process is ready to serve traffic," which matters for k8s-style deployments.

Proposed approach

Add distinct /health/live and /health/ready endpoints with the semantics each is meant to have.

Acceptance criteria

• Liveness reflects process aliveness only
• Readiness reflects dependency availability
• Documented for deploy-platform configuration

[drips-wave]

@Akatenvictor This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets

[drips-wave]

@Akatenvictor This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets

[drips-wave]

@Akatenvictor This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets