From 68f02f67488edc402ae9a292c2e0e1bde58f82cc Mon Sep 17 00:00:00 2001
From: davion-knight <298846663+davion-knight@users.noreply.github.com>
Date: Fri, 10 Jul 2026 00:18:58 -0500
Subject: [PATCH] fix(db): renumber the two newer 0134 migrations to resolve
 the 0134 collision

Three PRs landed a migration numbered 0134 (pr_last_backlog_convergence_regated_at,
review_targets_cadence_idx, predicted_gate_calls), so check-migrations fails on main and
blocks the queue. Keep the earliest at 0134 and renumber the two later ones to the next
free numbers (0136, 0137), preserving merge order. Pure renames; no SQL changes.
---
 ...argets_cadence_idx.sql => 0136_review_targets_cadence_idx.sql} | 0
 ...134_predicted_gate_calls.sql => 0137_predicted_gate_calls.sql} | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename migrations/{0134_review_targets_cadence_idx.sql => 0136_review_targets_cadence_idx.sql} (100%)
 rename migrations/{0134_predicted_gate_calls.sql => 0137_predicted_gate_calls.sql} (100%)

diff --git a/migrations/0134_review_targets_cadence_idx.sql b/migrations/0136_review_targets_cadence_idx.sql
similarity index 100%
rename from migrations/0134_review_targets_cadence_idx.sql
rename to migrations/0136_review_targets_cadence_idx.sql
diff --git a/migrations/0134_predicted_gate_calls.sql b/migrations/0137_predicted_gate_calls.sql
similarity index 100%
rename from migrations/0134_predicted_gate_calls.sql
rename to migrations/0137_predicted_gate_calls.sql