fix: harden generated output and database releases

[smiggleworth]

Summary

• preserve live generated output when the pre-swap backup rename fails
• make the missing-ORM error name the exact public install command
• add a registry-only database generate/validate smoke test
• run that public-artifact smoke test after every CLI publish

Linked issues

Closes #87
Closes #90

Acceptance audit

• Every acceptance criterion in Published database command depends on unavailable @askrjs/orm package #87 is checked with evidence.
• Every acceptance criterion in writeGenerated deletes live output directory with no backup when the pre-write backup rename fails #90 is checked with evidence.
• Both issues include and satisfy a permanent class-level guardrail.

TDD evidence

• Red data-loss commit: f20eba6
• Green data-loss commit: db98e10
• Red public-command test commit: 9e77bb8
• Green public-command and release-guardrail commit: 82886d7

Verification

• Exact stale-backup regression red, then green
• Complete generator suite: 23 passed
• Missing-ORM exact install instruction red, then green
• Clean registry-only CLI 0.0.23 + ORM 0.0.1 database generate/validate smoke test
• Full local package gate: lint, typecheck, 248 coverage tests, changelog, build, docs, publint, and package inspection
• Packed-template and minimum-peer integration tests
• Exact-head hosted CI run 31897889867 on Ubuntu, macOS, and Windows, plus audit, benchmark, templates, and peer floor
• Squash merge e5c66a27517911ff3ddc367bd11b139656f71378
• Release workflow 31898038085, including OIDC publish
• Annotated v0.0.24 tag dereferences to the squash merge
• @askrjs/cli@0.0.24 is public and latest on npm
• Clean registry-only 0.0.24 + ORM 0.0.1 post-publish database smoke test

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.