updated_ts carried two meanings. In _decay_* it is the settlement anchor --
"these values are settled up to this moment" -- and a previous round taught it
to hold still when less than one step of time has passed, so short gaps could
accumulate. In _update_* it was treated as "last written at" and set
unconditionally, outside every event branch. The main chat path calls
_update_* on every private message, so the anchor was reset faster than one
step could ever elapse and the decay branch never ran. Measured over an hour
of 30-second messages, all four Izard dimensions and the Plutchik values had
not moved a single step.
The two dimension sets also share one anchor, so nudging joy or trust froze
anger, sadness and fear along with them -- an hour of affectionate conversation
still ended with anger pinned at its peak.
Removed both unconditional writes and gave the anchor back to _decay_*.
Conditioning them on "did an event fire" would be wrong too: the apology and
comfort branches lower emotion, which is even less reason to restart the decay
clock. Nothing else reads the field -- only the two decay functions do, the
panel summary and frontend ignore it, and the hurt-aftermath gates use three
separate timestamps.
Companion suite 235 passed; the four new tests fail on the pre-fix code.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>