fix: generate Prisma client during release

[jonathanhaaswriter]

What changed

• generate the Prisma client before release validation typechecks
• enforce the release validation order in repository guardrails
• record the failed pre-publication v0.1.0 attempt and prepare immutable v0.1.1 image references
• make release verification examples version-variable driven

Validation

• actionlint .github/workflows/release.yml
• npm run db:generate
• npm run db:validate
• npm run typecheck
• npm run guardrails:migration (47 passing)
• docker compose --env-file .env.production.example -f deploy/compose/compose.production.yml config --quiet
• git diff --check

Release receipt

Release run 32444997354 stopped at TypeScript validation because @prisma/client had not been generated. Its image job was skipped, so it published no v0.1.0 image. After this PR merges, v0.1.1 is the forward release target.