[ovidius72]

Why

Room sends already support durable: true internally, but the public SendRoomMessageOptions type omits it. Passing it through MeshStore or CommsStore therefore fails TypeScript checking.

Changes

• Add durable to the shared SendRoomMessageOptions and export that type from the package entry point.
• Use the shared options type directly in the room sender, removing the redundant internal type.
• Describe what the option does in the API comment, including FileStore ignoring it because messages are already persisted.
• Give durable room sends their own README section. State explicitly that room notices are only stored locally: nothing currently announces or fetches them, and automatic offline catch-up still needs policy and bridge wiring.
• Add public-API integration cases for omitted, false and true values, including verification of the recorded signed notice.

Verification

• All 1,885 tests across 212 files pass, along with lint and TypeScript checking.
• The new public-API cases pass; the existing default send behaviour is preserved.

[Mearman]

The change itself is right: durable reaches RoomMessaging.sendRoomMessage through MeshStore, and the test discriminates on all three values. The inline comments are small fixes to the doc comment, the leftover alias and the README wording. Since this adds public API, feat(core) fits better than fix(core), and squashing the three commits into one would help, since the third undoes the second.

[Mearman]

All three comments are addressed in ddf5114 and CI is green. Thanks.

[github-actions]

🎉 This PR is included in version 8.15.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• v8.15.0
• GitHub release

Your semantic-release bot 📦🚀