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
bug(native): stale full-row game updates can restore an obsolete save path #19
A metadata-only Store.UpdateGame call can write an older full Game snapshot and overwrite a more recent, topology-admitted save_path change. Existing UpdateGame SQL updates all mutable fields including save_path, sync_ignore, branch and snapshot/lineage metadata, regardless of which fields the caller intended to change.
Independent synthetic RED witness
Using disposable SQLite/store fixtures against upstream dev-public@a0f6032b8ba36da25e3e0e5e90c5ace9ba0c1fc7:
Read a Game at path /old as a metadata editor.
Update its path to /new.
Commit the stale metadata edit using Store.UpdateGame.
Observed: the path returns to /old without native topology admission.
No production save or user filesystem was used.
Narrow acceptance contract
Metadata-only updates must not write topology or other unrelated protected fields from stale records; enforce at SQL write time (handler re-read alone is insufficient).
Intentional save-path changes must use exclusive native topology admission and an expected-old-state comparison, returning a typed conflict when stale.
Activity