Resuming a session no longer re-reacts to artifact comments it already handled, and auto-react can be paused.
What's wrong with this entry?
Automatic reactions to comments on artifacts can now report a third status, "paused", alongside "stopped" and "armed", and each session keeps a running record of what it has already reacted to. That record is saved with the session and restored when you resume, so resuming no longer re-reacts to comments handled before.
- The per-session record is stored as
artifactAutoReactLedger, cleared when session state is stripped, and handed back on resume asresumedArtifactAutoReactLedger. - A matching
artifactAutoReactLedgerscollection is saved and restored everywhere session state is serialised, next to the existing artifact comment monitors. - Stopping or resuming now also clears two other pieces of leftover state: swept orphan slugs and a pending resume disclosure.
- The notice shown when auto-react arms is now decided by whether the last outcome was degraded, rather than by whether the user had previously disarmed it.
- The session file writer also gained a materialisation event and a field used to repair a truncated tail on the session file.
artifactAutoReactLedger, artifactAutoReactLedgers
Strings lifted out of the shipped bundle, so the claim above can be checked against them.