CLI: make doctor pretty output human-readable

[Timi16]

Overview

The doctor command prints raw JSON values in pretty mode, which is hard to scan.

Background

Diagnostics is already present in the repository, but the current implementation leaves a concrete gap for users or maintainers. Relevant files: src/cli/commands.rs, docs/troubleshooting-index.md.

Specifications

• Render named sections with clear status lines.
• Show binary, config, history, plugins, protocol, remote, and VS Code checks.
• Keep JSON mode unchanged.
• Use warnings for failed checks.

Acceptance Criteria

• Behavior is covered by focused tests or documented manual verification.
• Errors are handled gracefully with actionable suggestions.
• Help text or docs are updated when the user-facing behavior changes.

[Jacques-codes]

@Jacques-codes has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hiii, Good Morning Ser I love your product and I would love to solve this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jacques-codes to this issue.

[Sam-Rytech]

@Sam-Rytech has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi maintainer

I'd like to take up this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sam-Rytech to this issue.

[mich-sys]

@mich-sys has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

hi team,
kindly assign this to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mich-sys to this issue.

[Amarjeet325]

@Amarjeet325 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi Maintainers 👋,

I’m interested in working on this issue and would like to be assigned.

I have experience contributing to open-source projects and implementing backend and full-stack features. I’ve successfully delivered contributions across multiple repositories and am comfortable following project standards, writing tests, and maintaining code quality.

I’ve gone through the issue description and understand the requirements. If assigned, I’ll start working on it immediately and submit a clean, well-documented PR for review.

Thank you for your time and consideration.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Amarjeet325 to this issue.

[eln4199]

@eln4199 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

i would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @eln4199 to this issue.

[drips-wave]

Congratulations, @eln4199! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @eln4199: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @eln4199 as part of the Stellar Wave Program's 5th Wave 🥳

😎 @eln4199: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.