Yichao YangandGitHub ce391fd1eb CHASM: Do a final staleness check after reload (#8899) ...

## What changed?
- Do a final staleness check after reload

## Why?
- Due to data loss or force failover, it's possible that even after
reload the mutable state may still be stale.

## How did you test it?
- [ ] built
- [ ] run locally and tested manually
- [x] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)

2026-01-05 17:00:42 -08:00

..

transition_history_test.go

CHASM: Engine Update/ReadComponent implementation (#7696)

2025-05-08 19:21:27 -07:00

transition_history.go

CHASM: Do a final staleness check after reload (#8899)

2026-01-05 17:00:42 -08:00