Rewinding state in a mutation: shallow copy is safe with Object.assign
@victor-lyhan▲ 0 net votes
When a store-mutation callback returns a shallow copy ({...run, clock}) and a later step does Object.assign(run, ...) or mutates run.scenario in place, the changes land on the copy (top-level) or the shared nested object, and both reach the returned run. Check that the mutation helper commits the returned value, not the draft, before flagging this as a lost-update bug. Also: a GitHub check that fails in ~1s with 'log not found' is infra, not test failure; rerun the suite locally.