fix(db): renumber colliding migration 0156 to 0157

[JSONbored]

Summary

• PR feat(review): add an opt-in draft-PR close policy to stop bot-review farming #6454 (draft-pr-close-policy) and PR fix(review): correlate screenshot-table presence-mode evidence to the PR head SHA #6467 (screenshot-table-gate-head-sha-correlation) both claimed migration number 0156, merging 23 minutes apart — neither rebased against the other's freshly-landed migration first.
• db:migrations:check (part of validate-code / test:ci) now fails on main for every open and future PR: duplicate migration number 0156.
• Renumbered the later-merged migration (#6467's 0156_pull_request_screenshot_table_presence_satisfied.sql) to 0157, matching the checker's own suggested resolution. No other file references the old filename/number.

Test plan

• npm run db:migrations:check — passes (contiguous 0001..0157, next free 0158)
• npm run db:schema-drift:check — passes (no drift from the rename)

[superagent-security]

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

[codecov]

❌ 4 Tests Failed:

Tests completed	Failed	Passed	Skipped
17533	4	17529	13

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

test/integration/api.test.ts > api routes > serves installation repair diagnostics and refreshes installation health

Stack Traces | 0.884s run time

AssertionError: expected { …(11) } to match object { installation: { …(3) }, …(3) }
(8 matching properties omitted from actual)

- Expected
+ Received

@@ -17,8 +17,8 @@
      "path": ".../777/repair/refresh",
    },
    "requiredPermissions": {
      "issues": "write",
      "metadata": "read",
-     "pull_requests": "read",
+     "pull_requests": "write",
    },
  }

 ❯ test/integration/api.test.ts:2195:24

test/unit/backfill.test.ts > GitHub backfill > marks comment, label, and check repair impacts disabled by repo settings

Stack Traces | 0.898s run time

AssertionError: expected { metadata: 'read', …(3) } to not have property "contents"

- Expected:
undefined

+ Received:
"write"

 ❯ test/unit/backfill.test.ts:1203:44

View the full list of 2 ❄️ flaky test(s)

test/unit/backfill.test.ts > GitHub backfill > repair diagnostics require contents:write for merge autonomy (#audit-install-health display)

Flake rate in main: 23.33% (Passed 23 times, Failed 7 times)

Stack Traces | 0.635s run time

AssertionError: expected 'write' to be 'read' // Object.is equality

Expected: "read"
Received: "write"

 ❯ test/unit/backfill.test.ts:1267:54

test/unit/queue-5.test.ts > queue processors > REGRESSION (#slop-commit-messages): the live slop gate fetches the PR's own commit messages, so low_quality_commit_message can actually fire

Flake rate in main: 16.67% (Passed 5 times, Failed 1 times)

Stack Traces | 0.633s run time

AssertionError: expected null to be 15 // Object.is equality

- Expected:
15

+ Received:
null

 ❯ test/unit/queue-5.test.ts:2708:31

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