Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(codegen): write generated files atomically to survive interrupted generation

Generate() unlinked the exec + model outputs at the very start, before any schema load or render, so any interruption or failure during generation (OOM on the validation compile, a timeout, SIGKILL, or a failing schema mutator) left the output ABSENT — invisible to go build until the next regen. Reported as #2345 ('deleted the older model/generated.go file, did not create a new one') and #3505 ('it seems to delete the generated files'), both closed without addressing the delete-before-write.

Replace the upfront unlink + truncate-write with an atomic write: render to a temp file in the same directory, then os.Rename into place on success. os.Rename is atomic on the same filesystem, so a reader/build never observes a half-written file, and a mid-generation failure leaves the pre-existing file intact instead of absent. The upfront unlink is removed because the rename replaces the file atomically (no prior delete needed).

Add TestGenerateAtomicWritePreservesOutputOnFailure: a pre-existing generated file survives a mid-generation failure (fails on the old unlink-first code, passes with the fix).