Module doctor 

bynk doctor — the capability model, the checks, and the exit-code contract.

Probes are grouped by the capability they unlock, not listed flat, so a compile-only user is never told they are “unhealthy” for lacking wrangler. The exit-code contract turns on what an invocation asks about (ADR: the doctor output / exit-code contract):

• Bare bynk doctor is informational. It surveys everything but treats only the compile floor (bynkc resolvable and not majorly skewed) as required, so it exits 0 even with test/dev unavailable.
• --only <capability> promotes that capability’s tools to required.
• --strict promotes all warnings (optional gaps, npx provisionability, minor skew) to failures, for an all-green CI gate.

Structs

CapabilityReport

A capability and its rows, with the aggregated health.

Context

Environment facts the caller supplies (real values in main, fixed values in tests).

DoctorOptions

User-facing knobs.

Report

The whole doctor result.

Row

One rendered line under a capability: a tool (or an any-of group like tsc | tsx), its health, a human detail, and a remedy when it is not Ok.

Enums

Capability

A unit of work a user might want to do, and the tools it needs.

Level

Health of a single row or a whole capability. Ordered: Ok < Warn < Fail.

Functions

diagnose

Run the checks against a toolbox and a resolved compiler.