[joeychilson]

Sets the version to 0.1.5 so the v0.1.5 tag can start the release, and tidies its notes: grouped by area, plus the protocol change that #90 didn't mention.

Flags: updates snapshots

Changes

• Cargo.toml and Cargo.lock say 0.1.5, so the app and turnscope --version report it.
• The MCP snapshot's server version is 0.1.5.
• The 0.1.5 notes are grouped by area: app, alerts and status, sessions, handoff. No entry is reworded.
• A new entry says serve speaks protocol 2, historyReadAt became historyRead, and a protocol 1 client is refused.

Evidence

No behavior change. The snapshot diff is the version string, twice:

tests/snapshots/mcp.json

-        "version": "0.1.4"
+        "version": "0.1.5"
-          "version": "0.1.4"
+          "version": "0.1.5"

The notes only moved. Sorting the old and new 0.1.5 sections line by line, the only difference is the new entry's three lines.

Not checked: the release itself, which the tag starts after this merges.

Risk

Pushing v0.1.5 after this merges publishes a signed release and an update feed. Installed copies pick it up, so it can't be taken back.