Preserve CLI status messages without interactive spinners

[James Newton-King (JamesNK)]

Description

Console logging and debug mode should not use Spectre.Console's interactive status renderer because spinner frames can interleave with diagnostic logs. They should still show status updates as stable, subtle messages so users retain progress context.

This follow-up to #19214 and the review feedback on #19256:

• Centralizes interactive status eligibility in ShouldShowInteractiveStatus, including the atomic nested-status guard.
• Restores debug-mode spinner suppression across synchronous, asynchronous, and dynamic status methods.
• Keeps status messages visible when console logging is enabled while suppressing spinner rendering.
• Makes the doctor regression recording resilient to stale files and validates debug logging explicitly.

User-facing usage

Running doctor with console debug logging keeps readable status messages without interactive spinner frames:

aspire doctor --log-level debug

Screenshots / Recordings

This PR includes UI changes. Please add screenshots or screen recordings so reviewers can evaluate the visual changes without running locally.

• For before/after comparisons, place them side-by-side or label them clearly.
• For interactive changes (animations, transitions, new flows), prefer a short screen recording (GIF or video).
• If you cannot capture visuals now, note what scenario to test and mark this section as TODO.

TODO: Run aspire doctor --log-level debug in an interactive terminal and confirm status messages remain visible without spinner glyphs. Local archive creation was blocked by unrelated existing Dashboard package path-length errors (NU5123).

Validation

• ConsoleInteractionServiceTests and SpectreConsoleLoggerProviderTests: 119 passed.
• Aspire.Cli.EndToEnd.Tests project build passed.
• git diff --check passed.

Fixes # (issue)

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 19272

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 19272"

[Copilot]

Pull request overview

Preserves CLI status messages while suppressing interactive spinners during debug or console logging.

Changes:

• Centralizes spinner eligibility and nested-status guarding.
• Displays stable status updates in fallback modes.
• Expands unit and doctor end-to-end regression coverage.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
src/Aspire.Cli/Interaction/ConsoleInteractionService.cs	Centralizes interactive-status selection.
tests/Aspire.Cli.Tests/Interaction/ConsoleInteractionServiceTests.cs	Tests fallback status behavior.
tests/Aspire.Cli.Tests/Interaction/SpectreConsoleLoggerProviderTests.cs	Verifies trace filtering.
tests/Aspire.Cli.EndToEnd.Tests/DoctorCommandTests.cs	Validates debug output without spinner glyphs.

[James Newton-King (JamesNK)]

One blocking output regression found: console logging now duplicates status messages because the fallback both logs and renders them directly. Focused CLI unit tests pass, but the current combined-output assertions do not detect the duplication.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

Suppressed comments (1)

tests/Aspire.Cli.Tests/Interaction/SpectreConsoleLoggerProviderTests.cs:36

• This expectation conflicts with the CLI contract: RootCommandStrings.DebugLevelArgumentDescription advertises Trace as a console log level, and Program.CreateLoggerFactory configures the Aspire.Cli filter to the requested level. Because SpectreConsoleLogger.IsEnabled currently rejects Trace, --log-level trace silently omits all trace messages; asserting false locks in that bug. Permit trace for Aspire CLI categories and expect true here.

        Assert.False(aspireLogger.IsEnabled(LogLevel.Trace));

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

[github-actions]

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

[github-actions]

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

[Mitch Denny (mitchdenny)]

Approving this direction. We'll want to fix the double printing of status messages when console logging is enabled, where the status can be emitted through both the logger and the fallback display path.

[github-actions]

🔍 CI Failure Analysis: Transient Infrastructure Failure

The CI build failed due to transient infrastructure issues.

Failed jobs:

• Tests / Hosting.Oracle / Hosting.Oracle (ubuntu-latest) — The 'Checkout code' step failed with git exit code 128 due to 'server certificate verification failed' when accessing github.com. This is a runner-side SSL/network issue unrelated to any PR change; the checkout step runs before any PR code is compiled or tested. (transient-infra)

If a rerun was not already requested automatically, visit the workflow run page to rerun the failed jobs manually.