fix(cache): read an ISO 8601 instant in an alert as one placeholder
Merged
21
17d ago+17+17+01234567890123456789-1-1-0123456789
What and why
- An alert like
Saved at 2026-10-24T15:41:27.955Zfailed its replay end check when the time differed.VOLATILE_TEXTtook only2026-10-24T15as an id and left the rest, so most pairs of saves compared unequal. - A new pattern matches the whole instant (seconds, fraction and offset optional), so
alertShapereads it as one placeholder as the docs say.
Issue
Fixes #1358
Verified
Ran it locally: yes
pnpm checkpasses, e2e unit tests pass (3174).- The new test fails on main and passes with the change.
Checklist
- Changeset added (
pnpm changeset) for any change to a published package, or the change is testbed, docs, or CI only. - Breaking change: not applicable.
- Docs updated in the same PR: no change needed,
docs/cache.mdxalready says volatile text in an alert reads as a placeholder. - Contract change: not applicable.
- Engine contract change: not applicable.