health

/health — BDC Health

Run the executable health checker. Do not judge BDC health from memory.

/health is the only user-facing BDC health entrypoint. It runs local deterministic checks by default.

Default

If builder invokes /health with no argument, run:

bash ${BDC_HOME:-$HOME/.bdc}/scripts/hook-health-check.sh

Report:

• whether the command passed
• hook install status
• missing script or projection warnings
• whether the result is local quick health or local baseline evidence

Arguments

Argument	Action
--quick	Run hook-health-check.sh. Local only, no remote spend and no paid model calls.
--baseline	Run local deterministic checks when the source repo is available, otherwise run hook-health-check.sh. Local only, no remote spend and no paid model calls.

Rules

• Do not turn a quick-health pass into a full baseline claim. Instead say whether the current result is local quick health or local baseline evidence. Because: quick health and baseline checks answer different questions.
• Do not hide baseline warnings. Instead quote the warning line and explain the operational meaning in one sentence.

Verification

• /health --quick must run hook-health-check.sh.
• /health --baseline must run local-only baseline checks when the source repo is available.

Red Flags

• A response judges BDC health from memory.
• A quick-health pass is described as release-grade green.
• External validation is treated as a user-facing skill.

Common Rationalizations

Rationalization	Response
"The last release gate was green, so current health is green."	Do not collapse the facts. Run the current health command and report fresh evidence.
"Just run every possible check to be sure."	Do not from a vague health request. /health --quick is the default no-spend gate; use /health --baseline only when a broader local check is requested.