refactor(session-projection): compare per-step views instead of storing a dedup baseline
Review suggestion (imccyu): the drive holds both the previous and next state, so the identity gate can compute view(previous) and view(next) in the driving step
Review suggestion (imccyu): the drive holds both the previous and next state, so the identity gate can compute view(previous) and view(next) in the driving step and compare them directly. The stored lastView cell field and its stamp-on-every-change rule are deleted; with no dedup memory, nothing can go stale across listener generations by construction, and a rebuilt cell no longer pushes an unchan
- Date
- 2026-08-31
- Version
- master@9069a8b
- commit
- 9069a8b
Review suggestion (imccyu): the drive holds both the previous and next state, so the identity gate can compute view(previous) and view(next) in the driving step and compare them directly. The stored lastView cell field and its stamp-on-every-change rule are deleted; with no dedup memory, nothing can go stale across listener generations by construction, and a rebuilt cell no longer pushes an unchan