Sync Needs-you dismissals and chat read state across devices

This commit is contained in:
2026-10-31 12:47:25 +00:00
parent f4b3ef17cc
commit d1aa36163a
12 changed files with 1164 additions and 14 deletions
+5 -1
View File
@@ -316,7 +316,11 @@ Existing protocol commands: `ping`, `list_pipelines`, `get_pipeline`,
optional `kind` and `limit`) and returns a `search_results` response whose ranked
`results` each carry a stable `target` the client can open plus the typed payload
and matched field. `list_runs` also returns all-history `usage`
aggregates. See `internal/protocol/message.go` for JSON envelopes. Mutating RPCs
aggregates. `attention_acks` reads and `ack_attention` adds to the operator's
shared in-app acknowledgements (dismissed Needs-you entries and chat read
watermarks; see [ntfy.md](ntfy.md#clearing-notifications-across-devices)); other
connections receive an `attention_acks_changed` push. See
`internal/protocol/message.go` for JSON envelopes. Mutating RPCs
have real effects; they are not previews. TUI-only animation, scrolling, and
transient client logs are presentation, not separate server capabilities.
+16
View File
@@ -182,6 +182,22 @@ changes any subset; both reply with type `notification_settings` carrying all
three keys. Unknown keys and non-boolean values are refused with an `error`
reply and nothing is written.
## Clearing notifications across devices
The app's in-app attention state is shared through the server: dismissing an
entry or using **Clear all** in the Needs-you sheet, and opening a chat (which
clears its **New** badge), clears it on every connected browser and phone at
once, and on a disconnected device when it next connects. The protocol is
`{"type":"attention_acks"}` (read the whole set) and
`{"type":"ack_attention","attention_acks":{"dismissed":["42:Failed"],"chat_seen":{"ses_x":1730000000000}}}`
(add to it). Both reply `attention_acks`, and every other connection receives an
`attention_acks_changed` frame with the change. Acknowledgements for deleted runs
or sessions, or older than 30 days, are pruned.
This does **not** reach notifications the ntfy app has already shown on a phone:
once ntfy delivered a message, the server cannot retract it, so those must still
be swiped away in the ntfy app (or the Android notification shade).
## Explicit delivery stage (optional)
The preceding stage must output three nonempty UTF-8 strings: `title`, `summary`,