From e497ecc77342ee60e2aa8789a55aae20cea8d460 Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Thu, 9 Jul 2026 18:41:11 -0700
Subject: [PATCH 1/2] fix(db): resolve migration number collision at 0131

Two already-merged PRs (#4544 impact-map query cache, #4545 screenshot-table
gate matrix) both claimed migrations/0131, so db:migrations:check fails on
main. Renumber the more-recently-merged file to 0133 (the next free slot,
since 0132 is claimed by an in-flight PR) to restore a contiguous sequence.
---
 ...impact_map_query_cache.sql => 0133_impact_map_query_cache.sql} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename migrations/{0131_impact_map_query_cache.sql => 0133_impact_map_query_cache.sql} (100%)

diff --git a/migrations/0131_impact_map_query_cache.sql b/migrations/0133_impact_map_query_cache.sql
similarity index 100%
rename from migrations/0131_impact_map_query_cache.sql
rename to migrations/0133_impact_map_query_cache.sql

From 8b2015f1e57164f32b02e16600f7f1d38df9def2 Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Thu, 9 Jul 2026 18:43:35 -0700
Subject: [PATCH 2/2] fix(db): renumber collision fix to 0132, not 0133

The prior commit skipped straight to 0133, leaving a gap at 0132 -- CI
correctly caught it (db:migrations:check enforces a contiguous sequence with
no skipped numbers). 0132 is the actual next-free number in this branch
considered on its own.
---
 ...impact_map_query_cache.sql => 0132_impact_map_query_cache.sql} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename migrations/{0133_impact_map_query_cache.sql => 0132_impact_map_query_cache.sql} (100%)

diff --git a/migrations/0133_impact_map_query_cache.sql b/migrations/0132_impact_map_query_cache.sql
similarity index 100%
rename from migrations/0133_impact_map_query_cache.sql
rename to migrations/0132_impact_map_query_cache.sql