lsm / HyperNeo / 31564692270

79%

Build Type

push

github

Committed by web-flow

Commit Message

feat(delivery): expose message delivery state in the UI [#862]

* feat(delivery): expose send_status delivery lifecycle in chat + Space feeds [#862]

Add a shared MessageDeliveryStatus type (queued/processing/retrying/delivered/
failed) with a sendStatusToDeliveryStatus mapper, and surface it through the
messages.bySession and spaceTaskMessages LiveQuery feeds:

- Widen user-row visibility so deferred/enqueued/submitted rows appear (the
  daemon's own reads keep the consumed/failed filter, so prompt context and
  rewind are unaffected). This also gives a natural optimistic-like echo: the
  persisted enqueued row appears within ms of send via the reactive-DB flush,
  no web-side optimistic insert needed.
- Map send_status + the active message_delivery job retry_count to the badge
  state, so queued/processing/retrying/failed are distinguishable without
  inferring from system/init.
- Render the badge on SDKUserMessage (delivered hides it to avoid noise) and
  expand the existing Space thread deliveryState from delivered/failed to the
  full lifecycle. DeliveryStateBadge is generalized to cover both status unions.

Phase 4 of message-delivery reliability (task #862 items 2, 3, 5).

* test(delivery): cover delivery-status mapping, retry signal, and reactive no-duplicate [#862]

- live-query-messages: assert the widened feed surfaces every user-message
  state (queued/processing/delivered/failed) and that an active message_delivery
  job with retry_count > 0 marks the row 'retrying'.
- live-query-delivery-status: end-to-end through Database -> ReactiveDatabase ->
  LiveQueryEngine, a send_status transition emits an UPDATED delta on the same
  row id (never a duplicate ADD), and a post-reconnect snapshot reconciles to
  the latest send_status.
- SDKUserMessage: badge renders for queued/processing/failed and is hidden for
  delivered (avoid noise).

Phase 4 of message-delivery reliability (task #862 items 4, 8).

* docs(delivery): phase-4 — delivery state i... (continued)

Coverage Stats

20758 of 58599 branches covered (35.42%)

Branch coverage included in aggregate %.

31 of 38 new or added lines in 10 files covered. (81.58%)

1 existing line in 1 file now uncovered.

30867 of 69197 relevant lines covered (44.61%)

277.98 hits per line