[DevMando]

During startup, connection status becomes available before model validation and MCP initialization complete. A render in that gap could start the chat input loop early. Wait for completed initialization, apply prompt state changes together on the renderer dispatcher, and prevent a closed agent from starting input after the startup delay.

Prepare CLI v0.16.1 with the package version, release notes, changelog, and a release checklist. Allow the component stability script to run focused startup repetitions. RazorConsole remains at 0.6.0; Desktop code/versioning and local launch settings are excluded.

Validation completed on Windows:

• Release-mode full suite: 1,247 passing tests on each of .NET 8 and .NET 10.
• Startup lifecycle: 25 fresh-process runs per framework, three tests per run, all passing. The early-input regression fails with the previous gate.
• Full component suite: three fresh-process runs per framework, 234 tests per run, all passing.
• Local v0.16.1 package inspected for both runtimes, installed from an isolated local-only source, and its installed executable passed --doctor.
• git diff --check passed.

The user retested startup and could no longer reproduce the corruption. The exact repeated-border screen has not been reproduced automatically, so this PR fixes the confirmed race without claiming all terminal corruption is resolved.

CI validation: CLI tests run passed all four Windows/Linux × .NET 8/.NET 10 jobs, including full suites and repeated component tests.

Release checks still required: the documented interactive launch/resize/focus checks, review, and merge. No tag, GitHub release, merge, or NuGet publication is performed by this PR.