fix(migrations): recreate the secrets migration with a fresh revision id

The add-secrets migration was amended in place across the review rounds
(notably the nsec_state column), so its revision id no longer maps to a
single schema step and any DB that ran an intermediate form would not
re-migrate. Recreate it under a fresh id (fc4fa29630d2) chained onto the
current head so the migration is one clean, unambiguous step.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

migrations/versions/fc4fa29630d2_add_secrets_table.py

@@ -1,8 +1,8 @@
 """add secrets table
 
-Revision ID: c6f8d2e4a1b3
+Revision ID: fc4fa29630d2
 Revises: d7e8f9a0b1c2
-Create Date: 2026-07-07 00:00:00.000000
+Create Date: 2026-07-23 00:00:00.000000
 
 Creates the node-level singleton secret store (issue #553). Schema only; moving
 any legacy plaintext into the encrypted/hashed columns happens at bootstrap,
@@ -16,7 +16,7 @@ import sqlalchemy as sa
 import sqlmodel
 from alembic import op
 
-revision = "c6f8d2e4a1b3"
+revision = "fc4fa29630d2"
 down_revision = "d7e8f9a0b1c2"
 branch_labels = None
 depends_on = None