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
{{ message }}
Repository navigation
Validate fork migration history gaps during startup #141
Normal startup only calls runForkMigrations() when the newest recorded fork migration is below the head. A history with a gap below the head (for example fork IDs 1–15 and 17 with 16 missing) can therefore start without running forkHistoryProblems, silently leaving the missing migration unapplied. Release preflight still catches the state, but ordinary startup should reject it as it did before.
Run the read-only fork-history integrity check unconditionally, including when no migration is pending, without taking an unnecessary write lock.
Acceptance:
A gapped fork migration history fails startup before applying later migrations.
A current, gap-free history remains read-only when there is no pending migration.
Activity