chore: regenerate the column-widening migration on top of the current head

migrations/versions/3b1965ea9cea_widen_money_and_timestamp_columns_to_64_.py

@@ -1,8 +1,8 @@
 """widen money and timestamp columns to 64-bit
 
-Revision ID: d3c8b21f7a04
+Revision ID: 3b1965ea9cea
 Revises: a73d19b6c204
-Create Date: 2026-09-29 00:00:00.000000
+Create Date: 2026-09-30 23:13:38.295444
 
 Balances are millisatoshis and every clock column is a unix timestamp, so both
 are 64-bit quantities. SQLite stores all INTEGER values as 64-bit, which is why
@@ -23,7 +23,8 @@ from __future__ import annotations
 import sqlalchemy as sa
 from alembic import op
 
-revision = "d3c8b21f7a04"
+# revision identifiers, used by Alembic.
+revision = "3b1965ea9cea"
 down_revision = "a73d19b6c204"
 branch_labels = None
 depends_on = None

tests/unit/test_postgres_schema_compat.py

@@ -28,7 +28,7 @@ MIGRATION = (
     ROOT
     / "migrations"
     / "versions"
-    / "d3c8b21f7a04_widen_money_and_timestamp_columns.py"
+    / "3b1965ea9cea_widen_money_and_timestamp_columns_to_64_.py"
 )
 
 # Built once here because SQLAlchemy's dialect constructors are untyped.