Document first release baseline

2026-07-29 19:23:07 +02:00
parent 9ea081179d
commit fac6c9350f
1 changed files with 19 additions and 0 deletions
@@ -8,6 +8,25 @@ requirements and intended sequencing, not proof of implementation.
 - Collect the remaining editor interaction issues before changing additional
  behavior.
 ## First Release Baseline
 Complete this immediately before the first supported release, once the schema
 and initial feature set are frozen:
 - Decide explicitly whether pre-release databases, portable JSON exports,
  logical snapshots and persisted command histories remain supported.
 - Create one clean baseline migration that builds the complete release schema
  on an empty database.
 - Replace the active development migration chain and Drizzle metadata only if
  no released installation depends on it.
 - Remove upgrade-only database, snapshot and command compatibility code only
  for formats that are explicitly declared unsupported.
 - Preserve the pre-release migration history in Git history or a release tag.
 - Verify installation, migrations, application startup and core workflows
  against a completely empty database.
 - Mark the resulting compatibility boundary with the first release tag.
 - Treat every migration published after that release as immutable.
 ## Project History
 - [x] Every listed logical snapshot, including automatic snapshots, must be