Consider cmd.exe maximization on Windows startup

Context

The Rich live UI renders substantially better when the Windows console window is maximized.

For operators launching the app in a native cmd.exe or PowerShell console, it may be worth attempting a best-effort maximize step during startup.

Proposal

Consider adding a Windows-only startup helper that attempts to maximize the console window before the Rich live UI starts.

Constraints

• This should be best-effort only.
• It should not block startup if the call fails.
• It will likely work only for a real Windows console window.
• It may not work in SSH sessions, VS Code integrated terminals, Windows Terminal tabs, or other embedded/remote terminal environments.

Desired behavior

• On supported native Windows console launches, maximize the window automatically so the live UI has enough width.
• On unsupported terminals, do nothing and continue normally.

Notes

This is primarily an operator-experience improvement, not a correctness fix.

Start by locating the application startup path and the point where the Rich live UI begins. Research a Windows-only, best-effort console-window maximization approach, then verify that supported native consoles maximize while failures and unsupported terminals continue startup normally.