fix(db-migration): keep timestamp order

src/application/ports/opaque_ports.rs

@@ -2,7 +2,7 @@
 //!
 //! The registration record (encrypted "envelope" blob) and its
 //! metadata live in three columns on `auth.users` — introduced by the
-//! Phase 0 migration (`20260926000000_auth_opaque.sql`). This trait
+//! Phase 0 migration (`20260930000002_auth_opaque.sql`). This trait
 //! wraps the row-level access so:
 //!
 //!   * the OPAQUE handlers (Phase 1+) depend on a small, mockable

src/infrastructure/repositories/pg/opaque_pg_repository.rs

@@ -1,7 +1,7 @@
 //! PostgreSQL repository for OPAQUE aPAKE envelopes.
 //!
 //! Backs [`OpaqueRepositoryPort`] against the three OPAQUE columns on
-//! `auth.users` introduced by migration `20260926000000_auth_opaque.sql`:
+//! `auth.users` introduced by migration `20260930000002_auth_opaque.sql`:
 //!
 //!   * `opaque_envelope BYTEA` — the serialised registration blob,
 //!   * `opaque_ciphersuite_version SMALLINT` — the bound suite version,