nanograph storage migration

A one-shot migration of a legacy nanograph database onto the current NamespaceLineage storage generation. Preserves the current visible graph state, resets storage-era history, and leaves a verifiable backup — with clear rollback steps if anything looks wrong.

• Run nanograph storage migrate --db <db>.nano --target lineage-native
• Keep the current committed graph state; drop old manifest/WAL-era history
• Verify row counts, queries, embeddings, and media before deleting the backup
• For schema changes in a healthy database, use nanograph migrate instead — this skill is storage-only

For new graphs, nanograph 1.2.x defaults to NamespaceLineage. That storage generation is Lance 4 namespace-backed, uses lineage-native CDC for inserts and updates, keeps delete tombstones in __graph_deletes, and stores committed graph state in Lance-backed internal tables such as __graph_snapshot and __graph_tx.

When to use this

Use this skill when any of these are true:

• the CLI refuses to open a database normally and prints nanograph storage migrate --db ... --target lineage-native
• the database still uses the old manifest or WAL-era storage layout
• the project wants the current default storage generation for new work