clawbot 6e1f499048 Document that migrations are supported and none are added before 1.0 (closes #68) ...

The docs now say vaultik supports migrations. The numbered files in `internal/database/schema/` are migrations: `schema_migrations` records which have run, and opening a database applies any that have not. None are added before 1.0 because nothing is installed anywhere yet, so a schema change edits `001.sql` directly. After 1.0 each change is a new numbered file, and an existing local database is migrated when vaultik is updated.

`docs/DATAMODEL.md` owns the explanation. The README caveat and roadmap entry and `AGENTS.md` policy 13 link to it. This replaces the wording from #146, which said there was no upgrade path.

Disclosure: `CLAUDE.md` line 33, the owner's file, changes from "do not need to support migrations" to "do not add migrations before 1.0".

Model: opus-5-5

2026-09-28 20:21:38 +02:00

..

DATAMODEL.md

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

2026-09-28 20:21:38 +02:00

REPOSTRUCTURE.md

Mark a snapshot complete only after its metadata export succeeds (closes #177)

2026-09-22 20:00:41 +02:00