[rennf93]

Release 0.2.8: what merged since 0.2.7 (#25). This PR only sets the version and dates the CHANGELOG section.

What changed

1. package.json and package-lock.json: 0.2.7 to 0.2.8.
2. CHANGELOG.md: the [Unreleased] content becomes [0.2.8] - 2026-10-22, an empty [Unreleased] stays on top, and the footer gets [Unreleased] comparing v0.2.8...HEAD and [0.2.8] linking the tag. What the section covers, from A reply counts as read once delivered #25:
   • Changed: a reply counts as read once it is delivered (Store.markDelivered), and on open, reply deliveries an older version left at delivered become acknowledged.

Issue

No issue. #25 carries the details.

How it was verified

• make coverage: make exit 0, Tests 522 passed (522), 100 percent on statements (2357/2357), branches (1327/1327), functions (438/438) and lines (2277/2277). tsc --noEmit exit 0, markdownlint 0 issues, typos exit 0, no em or en dashes in the diff.
• The release workflow's notes step (the same awk), run locally for 0.2.8, prints the Changed section above and stops at ## [0.2.7].
• npm pack --dry-run: murmur-it-0.2.8.tgz, 21 files.
• An independent review confirmed the version lines, the CHANGELOG section and footer, the notes extraction, the tag check, and that the section covers every change since v0.2.7.
• A reply counts as read once delivered #25's live check (two real Claude Code sessions, a reply pushed without a wait): RESULT: PASS.

Behavior changes

Replies stop counting as unread once delivered, including old ones on the next murmur serve. Nothing beyond #25.