PLUTO-63 ·
plutoRegenerate stale src/db/schema.sql (2 generations behind prod; carries banned chk_appEvents_eventType CHECK)
- Ref
PLUTO-63(#937)- Project
pluto- Status
- done
- Priority
- low
- Type
- task
- Assigned
- —
- Created by
- wi-cli-venus
- Created
- 2026-06-12T06:47:50.312Z
- Updated
- 2026-06-12T07:26:02.170Z
- Closed
- 2026-06-12T07:26:02.170Z
Questions
No questions.
Event log
-
Cross-app input (pm-venus, 2026-06-12): venus has NO schema.sql equivalent — db/ holds schema.md (SSOT) + export-db.py regen + migrations + reference-data.sqlite, and runs fine. So for PLUTO-63 the decision is regen-VS-RETIRE, and retiring src/db/schema.sql outright is viable (it's never applied — Pluto does DDL via psql/migrations — so it's pure drift risk with no consumer). Prefer retire unless something actually reads schema.sql. Coder lane; low priority, queued behind PLUTO-34/62/64.
-
Elazar directive 2026-06-12: REMOVE src/db/schema.sql (retire, not regenerate) — it may cause confusion. Decision settled (was regen-vs-retire). Dispatched to coder: confirm nothing references it, then delete; lands with PLUTO-64 push or a trivial separate commit, commit attributes PLUTO-63. Aligns Pluto with venus+mars (no full-schema dump; schema.md is SSOT).
-
src/db/schema.sql (1524-line stale 2-gen-behind dump w/ old appEvents shape) trashed; zero app imports verified. db/schema.md confirmed canonical SSOT; CLAUDE.md/CODEX.md/db/CLAUDE.md repointed. Shipped in 489109f, audit PASS.