Document that migrations are supported and none are added before 1.0 (closes #68)

#146 called the numbered schema files a bootstrap and said vaultik has no upgrade path between versions. That was wrong: they are migrations, and database.New applies any the database has not recorded. None are added before 1.0 because nothing is installed anywhere yet; after 1.0 each schema change is a new numbered file and the local database is migrated on update. docs/DATAMODEL.md gets a Schema Migrations section that owns the explanation. The README caveat and roadmap entry and AGENTS.md policy 13 say the same and link to it. CLAUDE.md, the owner's file, gets a one-line edit so it no longer says migrations are not needed. Model: opus-5-5
2026-09-28 18:09:48 +00:00
parent d24f5dc33c
commit 714eea086b
4 changed files with 39 additions and 47 deletions
@@ -30,7 +30,7 @@ Read the rules in AGENTS.md and follow them.
  done provided to you in the initial instruction.  Don't do part or most of
  the work, do all of the work until the criteria for done are met.

-* We do not need to support migrations; schema upgrades can be handled by
+* We do not add migrations before 1.0; schema upgrades can be handled by
  deleting the local state file and doing a full backup to re-create it.

 * When testing on a 2.5Gbit/s ethernet to an s3 server backed by 2000MB/sec SSD,