expo-doctor currently outputs human-readable text only. There's no Node API and no --json flag, which makes it difficult to consume programmatically in CI scripts without parsing the raw output with fragile string matching.

Scripts that want to act on expo-doctor results have to parse ✔/✖ characters from the verbose CLI output and hard-code check names that must match exactly — both of which break silently when the output format or check names change.

We currently are running expo-doctor in our CI environment, and we want to fail on anything except dependencies being out of date, so we have to have custom logic in place to parse the output, etc.