fix(db): renumber colliding migration 0181 to 0182

[JSONbored]

Problem

db:migrations:check is currently failing on main:

check-migrations: duplicate migration number 0181: "0181_alert_dedup_claims.sql", "0181_decision_replay_inputs.sql".
Two PRs grabbed the same number — renumber the newest to the next free number (0182).

Two PRs merged 18 minutes apart and both picked migration number 0181:

• 0181_alert_dedup_claims.sql — fix(db): give the anomaly-alert dedup claims their own alert_dedup_claims table #8985, merged 2026-07-26T15:51:09Z
• 0181_decision_replay_inputs.sql — feat(orb): deterministic decision replay — re-derive any gate decision from its recorded inputs #9014, merged 2026-07-26T16:09:23Z (later)

This blocks CI for every subsequent PR against main.

Fix

Renumber the later-merged file to the next free number, 0182. Verified no code or test references either migration by filename or number (only test/unit/alerts.test.ts references 0181_alert_dedup_claims.sql, which keeps its number).

check-migrations: 186 migrations OK — contiguous 0001..0182 (5 grandfathered duplicates: 0015, 0017, 0074, 0090, 0156), no new duplicates. Next free: 0183

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
22047	1	22046	21

View the top 1 failed test(s) by shortest run time

test/unit/reputation-wiring.test.ts > shouldSkipAiForReputation (helper) > submission-cadence signal (#4514) > FLAG-ON: true for a machine-paced submitter even though every submission itself looks fine (quality-neutral)

Stack Traces | 0.169s run time

AssertionError: expected false to be true // Object.is equality

- Expected
+ Received

- true
+ false

 ❯ test/unit/reputation-wiring.test.ts:299:105

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}