[rennf93]

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

What changed

1. package.json and package-lock.json: 0.2.6 to 0.2.7.
2. CHANGELOG.md: the [Unreleased] content becomes [0.2.7] - 2026-10-21, an empty [Unreleased] stays on top, and the footer gets [Unreleased] comparing v0.2.7...HEAD and [0.2.7] linking the tag. What the section covers, all from Agent-side fixes: wait replies read as acknowledged, 110 s default wait, footer without the shell route, thread listing #23:
   • Added: murmur_thread without threadId lists the newest threads.
   • Changed: the default wait is 110 s (under Claude Code's 120 s auto-background threshold), and the per-message footer drops the shell route for sessions with murmur tools.
   • Fixed: replies handed over in a wait end acknowledged, so they no longer count as unread.

Issue

No issue. #23 carries the details.

How it was verified

• make coverage: make exit 0, Tests 518 passed (518), 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.7, prints the Added, Changed and Fixed sections above and stops at ## [0.2.6].
• npm pack --dry-run: murmur-it-0.2.7.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.6.
• Agent-side fixes: wait replies read as acknowledged, 110 s default wait, footer without the shell route, thread listing #23's live check (two real Claude Code sessions on that branch): RESULT: PASS.

Behavior changes

Listed in the section above; nothing beyond #23.