Implement leave handling in /feedback (posta.room/v1 + text fallback) #5

New issue

Open

opened 2026-05-13 18:45:13 +02:00 by arne · 0 comments

arne commented

2026-05-13 18:45:13 +02:00

Owner

What to build

Wire up the leave semantics in posta-web's room logic.

Inbound dispatch grows two new cases:

Inbound	Effect
`posta.room/v1` `action="leave"`	Remove sender from `subscribers`. Do not archive as content. Do not fan out. Return `204`.
`posta.text/v1` body trimmed-lowered == `"leave"`	Same effect. Compat fallback for clients that only speak `posta.text/v1` today.

Idempotent — a leave from a non-subscriber is a no-op (still `204`).

Everything else stays per posta/web#4 (any other text body archives, subscribes, and fans out; any other kind archives but doesn't fan out).

Acceptance criteria

A `posta.room/v1` action="leave" from a current subscriber removes them and returns `204`
A `posta.text/v1` body "leave" (with surrounding whitespace, mixed case) has the same effect
Leave messages are not archived as content (do not appear in the HTML archive) and not fanned out
Leave from a non-subscriber returns `204` and changes no state
After leaving, a follow-up `posta.text/v1` from the same sender re-adds them per the implicit-subscribe rule
Tests cover both the `posta.room/v1` form and the text-body fallback

Blocked by

posta/spec#3 (needs `action="leave"` defined in the spec)
posta/web#4 (needs subscribers + fan-out)

## What to build Wire up the leave semantics in posta-web's room logic. Inbound dispatch grows two new cases: | Inbound | Effect | |---|---| | \`posta.room/v1\` \`action=\"leave\"\` | Remove sender from \`subscribers\`. Do not archive as content. Do not fan out. Return \`204\`. | | \`posta.text/v1\` body trimmed-lowered == \`\"leave\"\` | Same effect. Compat fallback for clients that only speak \`posta.text/v1\` today. | Idempotent — a leave from a non-subscriber is a no-op (still \`204\`). Everything else stays per posta/web#4 (any other text body archives, subscribes, and fans out; any other kind archives but doesn't fan out). ## Acceptance criteria - [ ] A \`posta.room/v1\` action=\"leave\" from a current subscriber removes them and returns \`204\` - [ ] A \`posta.text/v1\` body \"leave\" (with surrounding whitespace, mixed case) has the same effect - [ ] Leave messages are not archived as content (do not appear in the HTML archive) and not fanned out - [ ] Leave from a non-subscriber returns \`204\` and changes no state - [ ] After leaving, a follow-up \`posta.text/v1\` from the same sender re-adds them per the implicit-subscribe rule - [ ] Tests cover both the \`posta.room/v1\` form and the text-body fallback ## Blocked by - posta/spec#3 (needs \`action=\"leave\"\` defined in the spec) - posta/web#4 (needs subscribers + fan-out)

arne referenced this issue from a commit

2026-05-13 21:54:55 +02:00

feedback: room broadcasts — implicit subscribe + fan-out outbox (#4)

arne referenced this issue from a commit

2026-05-13 22:00:59 +02:00

feedback: leave handling — posta.room/v1 action=leave + text-body fallback (#5)

arne referenced this issue from a commit

2026-05-13 23:13:56 +02:00

feedback: room broadcasts — implicit subscribe + fan-out outbox (#4)

arne referenced this issue from a commit

2026-05-13 23:13:56 +02:00

feedback: leave handling — posta.room/v1 action=leave + text-body fallback (#5)