Recover fixes that were pushed after their PRs merged

[JeremySNR]

Release notes

• Fixed: If Cutawan couldn't restart itself after updating a source checkout, trying again now finishes the update instead of reporting "already up to date".
• Fixed: On Windows, a Python or other command launcher (such as one from conda) is no longer mistaken for a broken Codex install.
• Fixed: AI connections that don't support strict JSON output (some local and OpenAI-compatible models) are now told exactly what shape to reply in, and a malformed reply is retried instead of failing.
• Fixed: A size-limited export that still ends up over the limit now says so plainly.

What does this change?

While cleaning up old branches, I compared every branch with its PR. Ten branches had one commit pushed after their PR merged, so it never reached main. Six were already covered by later work or no longer needed. This brings in the other four, plus a winget release fix:

Original commit	From	Fix
7b0af89	fix/dev-update-black-screen (#45)	Retry after a failed restart finishes a built source update instead of re-pulling
646bd18	codex/video-quality-improvements (#59)	Only codex.cmd is treated as a Codex shim on Windows; other .cmd launchers run via a shell. Ported by hand, since the file had changed
03afb8a	cursor/openai-compatible-endpoints-627e (#56)	json_object and plain fallbacks include the schema; invalid JSON moves on to the next format
ef5810b	cursor/size-targeted-export-627e (#55)	Warn when a capped export is still over the limit
a049ea5	cursor/winget-manifest-627e (#57)	The winget job uses the package.json version as its release tag. It still only runs once winget is configured

Cherry-picks keep (cherry picked from commit …) trailers.

How did you test it?

• npm test (582). New tests cover the schema fallback and the restart retry. The retry test fails on the previous code.
• npm run typecheck, npm run lint

🤖 Generated with Claude Code

---

Note

Medium Risk
Touches source-update relaunch, Windows process spawning for local Whisper/Codex, and the structured-output fallback path used across analysis—high user impact but scoped changes with new tests.

Overview
Bundles several fixes that never landed on main after their original PRs merged, plus a small release-workflow tweak.

Source checkout updates now remember when pull/build already finished but restart failed (relaunchPending). A retry goes straight to Restarting… instead of pulling again and hitting “already up to date.”

OpenAI-compatible analysis adds explicit schema text on json_object / plain fallbacks, validates parsed JSON before accepting a response, and retries the next format when the model returns prose or invalid JSON.

On Windows, only codex.cmd is resolved to the Codex JS entry; other .cmd shims (e.g. conda python.cmd) run through cmd.exe with properly quoted arguments via new cmdLine.

Size-targeted exports clarify that overBudget is a quality warning, not a guarantee under the cap; the editor shows a dedicated message when the finished file’s bytes exceed sizeTargetBytes.

The winget release job checks out the repo, reads package.json for the version, and passes release-tag to winget-releaser. CHANGELOG documents the fixes under [Unreleased].

^{Reviewed by Cursor Bugbot for commit 747d72c. Bugbot is set up for automated code reviews on this repo. Configure here.}