feat: add transactional module migration runner
This commit is contained in:
@@ -65,9 +65,12 @@ registration, dependency-ordered startup and reverse shutdown, rollback, and a b
|
||||
template. Optional compiled schema entrypoints now contribute validated, namespaced module-owned
|
||||
Drizzle tables to a deterministic aggregate without connecting to a database. Optional module-owned
|
||||
Drizzle migration directories now produce an atomic dependency-ordered offline inventory with
|
||||
validated metadata, explicit destructive-change declarations, and exact SHA-256 checksums.
|
||||
validated metadata, explicit destructive-change declarations, and exact SHA-256 checksums. Core can
|
||||
now compare that inventory with its fixed PostgreSQL history table, produce a read-only plan, and
|
||||
apply the complete pending batch under a session advisory lock and one transaction. Destructive
|
||||
migrations require an exact externally supplied approval bound to module, identity, and checksum.
|
||||
|
||||
Target architecture, not yet implemented: transactional migration execution and applied history,
|
||||
Better Auth,
|
||||
Target architecture, not yet implemented: production approval-provider composition, live
|
||||
PostgreSQL migration-runner integration coverage, Better Auth,
|
||||
permission enforcement, physical storage-bucket provisioning, Surface SDK, richer public resource
|
||||
and action contracts, API server, dashboard, Builder, and reference feature modules.
|
||||
|
||||
Reference in New Issue
Block a user