Finish reverting per-repository table

[intentionally-left-nil]

This finishes the cleanup of the never-deployed per-repo code

Summary

Verification

The table is empty on production, so there is nothing to save

• [ ]

Visual Changes

Before	After

Reviewer Notes

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Executive Summary

The PR cleanly finishes reverting the never-deployed per-repository customization feature: the repository_customizations table, RepositoryReviewMode enum, and related tests/types are removed, and no remaining application code references them.

Files Reviewed (6 files)

• packages/db/src/migrations/0255_drop_repository_customizations.sql
• packages/db/src/migrations/meta/0255_snapshot.json
• packages/db/src/migrations/meta/_journal.json
• packages/db/src/schema-types.ts
• packages/db/src/schema.test.ts
• packages/db/src/schema.ts

Verification Notes

• No non-migration references to repository_customizations, RepositoryReviewMode, or bot_mention_model_slug remain in apps/, services/, or packages/db/src, so the DROP TABLE ... CASCADE cannot break running application code.
• The pr_review_mode occurrences that remain live under platform_integrations.metadata (JSON key), not the dropped table column.
• enumCheck, unique, and withPlatformAccessTokenTestData helpers are still used elsewhere, so no unused-import/lint fallout.
• The SCHEMA_CHECK_ENUMS registry entry and its test expectation were removed consistently in schema.ts and schema.test.ts.
• Snapshot diff between 0254 and 0255 is exactly the removal of public.repository_customizations plus the expected id/prevId chain update; no schema drift.

---

_{Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0}

_{Review guidance: REVIEW.md from base branch main}