refactor(db): migrate user rule settings

docs/verification/jt-019-schema-ownership.md

@@ -15,6 +15,8 @@ table. It does not attempt to delete the legacy reconciler wholesale.
   and MariaDB/MySQL.
 - Removed the MariaDB startup `CREATE TABLE` block for `SystemEmailSettings` and moved the table to
   the migration-owned set.
+- Added `20260830121000_AdoptUserRuleSettingsSchema` and removed both provider startup-create paths
+  for the independent per-user rule-settings table.
 - Corrected the ownership runbook: new tables now default to migrations; the reconciler is legacy
   compatibility code to retire one dependency group at a time.
 
@@ -32,14 +34,15 @@ migration.
   `SystemEmailSettings` columns.
 - A database stopped immediately before the adoption migration, seeded with a representative SMTP
   settings row, upgrades without changing that row.
+- A representative per-user rules row survives adoption, downgrade, and re-upgrade.
 - Generated MariaDB SQL contains the provider-correct `SystemEmailSettings` DDL.
-- Full backend: 722/722 passed.
+- Full backend: 723/723 passed after both leaf-table transfers.
 - Fresh application startup over a new disposable SQLite database applied
   `20260830120000_AdoptSystemEmailSettingsSchema` and reached the healthy listening state.
 
 ## Remaining JT-019 work
 
-Thirty-four model tables remain startup-created, including the Identity group and several tables
+Thirty-three model tables remain startup-created, including the Identity group and several tables
 with parent dependencies. Transfer them in small dependency-aware migrations with blank, populated,
 retry and MariaDB runtime proof. Column/index repairs must remain until historical upgrade fixtures
 prove each one redundant.