feat: v1→v2 config schema migration for seid v6.5 write mode rename

[bdchatham]

Summary

Fixes #24. Unblocks all nightly chaos experiment validators currently crash-looping with invalid state-commit.sc-write-mode "cosmos_only".

What changed

types.go — v2 WriteMode constants matching sei-chain v6.5:

• WriteModeMemiavlOnly = "memiavl_only" (new default)
• Full FlatKV migration ladder: migrate_evm, evm_migrated, migrate_all_but_bank, all_migrated_but_bank, migrate_bank, flatkv_only, test_only_dual_write
• Old constants kept as // Deprecated: for migration use; removed from IsValid()

defaults.go — WriteMode: WriteModeCosmosOnly → WriteModeMemiavlOnly in both StateCommit and StateStore

config.go — CurrentVersion: 1 → 2

migrate.go — v1→v2 migration: maps cosmos_only→memiavl_only, dual_write→migrate_evm, split_write→evm_migrated in both WriteMode fields. Adds SeidVersionForSchema map so each schema version is traceable to its seid version boundary:

v1 → seid < v6.5
v2 → seid ≥ v6.5

Note on ReadMode

ReadMode (sc-read-mode) was removed from sei-chain's StateCommitConfig in v6.5. The field is kept in sei-config for backward compat and will be silently ignored by seid. A follow-on migration can remove it when sei-config drops pre-v6.5 support.

🤖 Generated with Claude Code

[cursor]

PR Summary

Medium Risk
Changes default and migrated storage write routing modes used at node startup; incorrect migration mapping could misconfigure SeiDB/FlatKV behavior across deploys.

Overview
Bumps the sei-config schema to v2 so configs align with seid ≥ v6.5 FlatKV write modes, fixing nodes that still emit or carry deprecated cosmos_only and fail validation at startup.

Write modes are redefined: new v2 constants (memiavl_only, full migration ladder through flatkv_only, test_only_dual_write) replace the old set in IsValid(); v1 names remain only as deprecated symbols for migration. Fresh defaults for state_commit and state_store write_mode switch from cosmos_only to memiavl_only.

A v1→v2 migration renames legacy values in both storage write fields (cosmos_only→memiavl_only, dual_write→migrate_evm, split_write→evm_migrated), bumps version, and is covered by registry round-trip and rename tests. Validation now warns if test_only_dual_write is set on state commit.

^{Reviewed by Cursor Bugbot for commit 8dc28b5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8dc28b5. Configure here.}