[Mike Krüger (mkrueger)]

Fix the Azure pipeline failure and preserve valid terminal JSON output on narrow consoles.

The normal CI failure was caused by long JSON strings being wrapped by the Spectre.Console renderer at the agent's console width. The resulting inserted carriage return made the test's JSON output invalid. For JSON lines that exceed the console width, the shell now writes the already-formatted JSON directly to stdout instead of routing it through the renderer that inserts line breaks. Short output remains syntax-highlighted.

The import dry-run output test uses a stable console width, and a new regression renders a 100-character string at 40 columns and parses the resulting stdout as JSON.

Validation: the full test suite passes locally (4886 passed, 0 failed, 131 skipped).

[Copilot]

🟢 Approval recommended

The isolated test-only change follows established patterns, preserves console cleanup, and has no identified blocking issues.

No open issues 🎉

What changed in this PR

Stabilizes the import dry-run output test by removing its dependence on the build agent’s console width.

Changes:

• Pins the captured console width to 200 to prevent wrapping inside JSON strings, matching existing console-capture tests.

File	Description
CosmosDBShell.Tests/​CommandTests/​ImportCommandTests.cs	Sets a fixed console width for dry-run output validation.

_{Review effort: Balanced}

[github-code-quality]

Code coverage overview

Languages: C#

C# / code-coverage/dotnet

main 4ff7843	dev/mkrueger/fix-dry... 1b585d4	+/-
72%	72%	0%

ℹ️ Calculations represent line coverage. Results may change as calculations are updated.

---

_{Updated October 26, 2026 16:00 UTC}

[Copilot]

🟢 Approval recommended

The focused rendering change addresses the wrapping failure with a matching regression test and no identified blocking issues.

No open issues 🎉

_{Review effort: Balanced}