You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
meta migrate / meta verify: --entities (package) scope filter for the DB rail #253
ResolvedGenConfig has an entities filter, so the codegen rail can be scoped to a package. ResolvedMigrateConfig and VerifyFlags have no equivalent, so the DB rail (meta migrate, meta verify --db) cannot be package-scoped. #248 removed the acute need in the reported case (phantom tables are gone), leaving this as ergonomics for large multi-package models.
Real design surface that gen-scoping doesn't have: a scoped expected schema diffed against a full DB proposes DROP TABLE for every out-of-scope table unless the scope also filters the actual side (and the snapshot ledger, and the FK-graph cascade keying from #241). That both-sides-scoped diff semantics deserves its own design, not a rider on a patch. Ref: §9d.
Closing — not tracking as a separate issue. This deferred item remains documented in the #248 design spec (docs/superpowers/specs/2026-08-01-issue-248-persistability-from-source-design.md §9) on main.
Activity
dmealing commentedon Aug 2, 2026
Closing — not tracking as a separate issue. This deferred item remains documented in the #248 design spec (docs/superpowers/specs/2026-08-01-issue-248-persistability-from-source-design.md §9) on main.