[docs-scanner] Deprecated self-diagnose tool section lacks guidance on alternatives

[docker-agent]

File: content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md

Issue

The "Self-diagnose tool" section contains only a deprecation notice with no additional information:

Self-diagnose tool

[!IMPORTANT]

This tool has been deprecated.

This stub section doesn't tell users:

• What to use instead of the self-diagnose tool
• When it was deprecated
• Whether it's been removed or just discouraged
• Which of the other diagnostic methods on the page replaces its functionality

Why this matters

Users who previously relied on the self-diagnose tool or who find references to it elsewhere need clear guidance on what to do instead. A deprecation notice without migration guidance leaves users without a path forward.

Suggested fix

Either:

1. Remove this section entirely if the tool is fully replaced by the "Diagnose" section above it, or
2. Add a sentence directing users to the appropriate alternative, such as: "Use the diagnostic methods described in the Diagnose section above instead."

If the self-diagnose tool was a specific CLI command or UI feature, mention what specifically was deprecated and what replaces it.

---

Found by nightly documentation quality scanner

[nielskaspers]

Rechecked main in content/manuals/desktop/troubleshoot-and-support/troubleshoot/_index.md after the PR discussion.

The replacement path is already documented earlier on the same page under ## Diagnose:

• Diagnose from the app
• Diagnose from an error message
• Diagnose from the terminal
• the inline pointer to docker desktop diagnose

So the smallest docs-only fix here is either:

1. delete the ### Self-diagnose tool stub entirely, or
2. replace it with one sentence that points readers to the existing replacement path.

Suggested wording if the section stays:

The former self-diagnose tool has been replaced by the Diagnose workflows above. To gather diagnostics from the terminal, use the docker desktop diagnose command.

That keeps the guidance architecture-neutral, stays within the same file, and avoids introducing a broader page rewrite just to close the gap the scanner found.