fix(db): renumber prism_eval_v3 migration to 0019

[echobt]

Summary

• PR feat(prism): AutoModel recipe 2.0 + miner-funded Lium BYOK #120 introduced 0017_prism_eval_v3.sql while 0017_raw_weight_tip_supersede.sql (PR feat(weights): tip-track /v1/weights/latest via leaf supersede + reseal #121) was already applied on staging/prod as version 17.
• sqlx then treated prism_eval as modified v17 → gateway/design/prism crash-loop on migrate.
• Renumber prism_eval to 0019_* so tip-supersede stays v17; staging/prod can apply 0018+0019 cleanly.

Test plan

• CI green on this PR
• Staging master deploy: services healthy (no migration checksum error)
• Confirm _sqlx_migrations has 17=tip supersede, then 18+19 applied
• Unblocks prod tag for design auto-enqueue (6fff1575 + this fix)

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

💤 Files selected but had no reviewable changes (1)

• crates/db/migrations/0019_prism_eval_v3.sql

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4d44cb0a-0edb-4bf7-8242-c4b848c3561b

📥 Commits

Reviewing files that changed from the base of the PR and between e7e89b0 and d92c40a.

📒 Files selected for processing (1)

• crates/db/migrations/0019_prism_eval_v3.sql

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}