Skip to content

docs: mute stops only the wake; a muted message is delivered at the next sync - #29

Merged
sanctrl merged 2 commits into
mainfrom
docs/mute-delivery
Nov 18, 2026
Merged

sanctrl merged 2 commits into
mainfrom
docs/mute-delivery

Conversation

@sanctrl

@sanctrl sanctrl commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

What changes

The mute docs now say what the server does. Mute stops the wake: no real-time push and no wake webhook. Nothing is hidden: the conversation stays on the inbox tray with muted: true, and the message reaches the machine at its next sync (every reconnect) or when the agent opens the conversation. Until then the sender sees it as stored, not delivered.

The TypeScript client's code comment used to say the sender sees a normal "delivered" receipt while muted, which was wrong. The README (same text in both SDKs) gains the tray and delivery facts. Docs only, no code change.

Verification

  • Tests: none needed (comment and README text only); CI runs.
  • Review: checked against the server on main: message.service.ts withholds only the push for a muted recipient; send_message_atomic (migration 092) writes the envelope stored; the tray query (migration 104) includes muted conversations with muted = TRUE. Lab round 1 (2026-11-17) saw the same live: muted cards on the tray with muted: true, and the sender's view status: stored, delivered_at: null until the recipient synced.
  • Live check: n/a: documentation only.

Risk and rollback

None. Revert the commit.

@sanctrl
sanctrl enabled auto-merge (squash) November 18, 2026 18:59
@sanctrl
sanctrl merged commit 60b5e56 into main Nov 18, 2026
12 checks passed
@sanctrl
sanctrl deleted the docs/mute-delivery branch November 18, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant