fix(deploy): pin prod Prism to public Lium template v9

[echobt]

Summary

• Persist PRISM_POD_TEMPLATE_ID=f2f5e84c-… (public prism-recipe-v9) in prod compose so the next digest deploy does not wipe the live hotfix.

Test plan

• Already set on prod master; prism-challenge healthy
• Next remote-deploy.sh --env prod --role master --build-from registry keeps the pin

Summary by CodeRabbit

• Chores
  • Updated production deployment configuration to use the designated public pod template.
  • Avoids requiring private template creation credentials during startup.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 66b33dac-42c0-4ab9-bc9e-d6066b72eb5e

📥 Commits

Reviewing files that changed from the base of the PR and between 374ef2b and 54e668f.

📒 Files selected for processing (1)

• deploy/compose/env-prod.yml

---

📝 Walkthrough

Walkthrough

The production Compose configuration sets PRISM_POD_TEMPLATE_ID for prism-challenge to a public v9 pod template UUID.

Changes

Production Prism template selection

Layer / File(s)	Summary
Configure the production pod template deploy/compose/env-prod.yml	The prism-challenge service now uses the pinned public v9 pod template through PRISM_POD_TEMPLATE_ID.

Estimated code review effort: 1 (Trivial) | ~2 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/prism-prod-pin-public-v9

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}