You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kiwi could open unclassified Base-v1 and Vector-v1 layouts through live RocksDB creation paths, leaving missing Column Families, partial manifest writes, and interrupted directory switches ambiguous after a restart.
This decision adds a durable Root-manifest migration journal, strict source-profile classification, shadow-copy verification, per-instance atomic promotion, production-open confirmation, and a verified pre-admission rollback path. Resume validation now accepts only the one-step filesystem progress that can occur between a durable rename and its journal update.
Constraint: Rollback is available only before RollbackWindowClosed; after admission, startup validates the live v2 topology without requiring the intentionally stale backup to remain byte-identical.
Rejected: Upgrade a live RocksDB instance in place | A crash between Column Family creation, manifest persistence, and multi-instance switching cannot prove which copy is authoritative.
Confidence: high
Scope-risk: broad
Directive: Keep create_missing_column_families disabled outside fresh, manifest-authorized instance creation.
Tested: WSL 32-test migration and fault-injection matrix; WSL Storage and Server Clippy with -D warnings; Windows Storage checks with and without test-fault-injection; Windows Server check; cargo fmt --check; git diff --check.
Not-tested: Snapshot restore and mixed-version cluster behavior remain Task 3 and later; exact historical executable compatibility remains Task 7.
Related: #421
Co-authored-by: OmX <omx@oh-my-codex.dev>
Signed-off-by: Xin.Zh <alexstocks@foxmail.com>
0 commit comments