[docs] Document aspire doctor check timeouts

[aspire-repo-bot]

Documents changes from microsoft/aspire#18969

@JamesNK

Targeting release/13.5 based on the source PR milestone 13.5.

Why

aspire doctor could previously hang at Checking Aspire environment... indefinitely if an environment check or installation discovery blocked.

What changed

Updated src/frontend/src/content/docs/reference/cli/commands/aspire-doctor.mdx with a note explaining the 30-second per-check timeout, the two-minute aggregate timeout, and the separate 30-second installation-discovery timeout. The note also explains that the aspire doctor result includes a warning when a timeout occurs.

No new pages were created; this is an update to the existing aspire doctor command reference page.

Generated by PR Documentation Check · auto · 58.8 AIC · ⌖ 7.15 AIC · ⊞ 19.6K · ◷

[aspire-repo-bot]

Frontend HTML artifact ready

The latest frontend build uploaded the frontend-dist artifact for PR #1472. Use the VS Code button below to open this PR with GitHub Artifacts Explorer and browse the built HTML locally.

This comment updates automatically when a new frontend build artifact is uploaded.

[Copilot]

Pull request overview

Updates the aspire doctor command reference to document newly introduced timeouts and how they surface in table and JSON output, aligning aspire.dev docs with the behavior added in microsoft/aspire#18969.

Changes:

• Added a note describing per-check, aggregate, and installation-discovery timeouts plus process-tree cancellation behavior.
• Added sample table output for individual-check and aggregate timeout warnings.
• Added JSON output example/notes for timeout metadata (checkType, timeoutSeconds).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Adam Ratzman (adamint)]

I checked the timeout values, cancellation behavior, warning output, and JSON metadata against the CLI implementation. This looks good.

[James Newton-King (JamesNK)]

Reviewed the updated timeout note. The per-check, aggregate, and installation-discovery limits are concise and unambiguous, and the warning behavior is stated clearly.