-
Notifications
You must be signed in to change notification settings - Fork 0
[dashboard DDX-21] S11: DB Migrations & Drift #552
Copy link
Copy link
Open
Labels
area:databasepackages/database and adapterspackages/database and adaptersarea:fresh-uiarea:pluginsplugins/* and plugin-core packagesplugins/* and plugin-core packagesepic:dev-dashboardDev Dashboard epic (Spine-1 headline, ships as a plugin)Dev Dashboard epic (Spine-1 headline, ships as a plugin)priority:p2MediumMediumstatus:triageIncoming; not yet triagedIncoming; not yet triagedtype:featwave:v1
Milestone
Description
Metadata
Metadata
Assignees
Labels
area:databasepackages/database and adapterspackages/database and adaptersarea:fresh-uiarea:pluginsplugins/* and plugin-core packagesplugins/* and plugin-core packagesepic:dev-dashboardDev Dashboard epic (Spine-1 headline, ships as a plugin)Dev Dashboard epic (Spine-1 headline, ships as a plugin)priority:p2MediumMediumstatus:triageIncoming; not yet triagedIncoming; not yet triagedtype:featwave:v1
DDX-21 / S11: DB Migrations & Drift
Summary
"Which migrations are pending vs applied, and has the schema drifted" — a panel over the existing
db statususe-case exposed via/_netscript/db/status.DX thesis
Aspire shows the DB resource is up; it never shows migration state or schema drift.
Scope
data-table(applied/pending); driftalert; introspect diff as CodeBlock.netscript db ...), confirm-gated — the db cells of the P2 management loop.db statustoday).Non-goals
WithUrlout-link). No query console.Acceptance criteria
Dependencies
/_netscript/db/statusread API (#423). Wave: beta.6 if the read API is trivial; else fast-follow. Note the db-init Prisma 7.x transient flake (re-run clears).