meta(parity): track datawatch-app mobile client feature parity

[dmz006]

Purpose

Umbrella tracking issue for keeping dmz006/datawatch-app
(the official mobile client) at feature parity with the datawatch server's PWA/web UI.

Per ADR-0005 in datawatch-app: the mobile app is a 1:1 client-side mirror of the
server's interactive surface. Any new PWA feature in this repo needs an equivalent
in the mobile app, and vice versa.

How to use this issue

When you add or change a PWA feature in this repo (datawatch server):

1. Note the feature in a comment below with a short description.
2. File a linked feature issue in dmz006/datawatch-app using the
   parity issue template
   referencing this issue.
3. The mobile client repo treats the linked issue as a tracked deliverable for
   the next appropriate sprint.

When the mobile client needs a new PWA-side capability:

1. File it in this repo with the mobile-parity label (to be added).
2. Cross-reference here.

Mobile-client surfaces that mirror PWA today (v0.2.0+)

Surface	Status
Sessions tab (list + refresh + state pills)	✅ shipped Sprint 1
Add server profile (bearer token, self-signed trust-override)	✅ shipped Sprint 1
Settings → Servers (list + delete)	✅ shipped Sprint 1
Settings → About (version + license)	✅ shipped Sprint 1
Animated splash / logo	✅ shipped Sprint 1
Session detail chat	⏳ Sprint 2
xterm terminal view	⏳ Sprint 2
WebSocket real-time streaming	⏳ Sprint 2
FCM push wake	⏳ Sprint 2 (depends on #1)
Voice capture	⏳ Sprint 3
MCP SSE tool invocation	⏳ Sprint 3
Memory / KG views	⏳ Sprint 3
Stats dashboard	⏳ Sprint 3
Channels configuration	⏳ Sprint 3
Alerts tab	⏳ Sprint 3

Cross-links

• ADR-0005 — 1:1 client parity scope
• api-parity.md — REST + MCP coverage matrix
• Linked upstream issues (this repo): feat(api): add /api/devices/register for mobile push tokens #1 (device registration), feat(api): generic voice transcription endpoint (or document Telegram-path reuse) #2 (voice transcribe), feat(api): federation fan-out /api/federation/sessions #3 (federation fan-out)

Ownership

Mobile client work: dmz006/datawatch-app repo (this project).
Server work: dmz006/datawatch repo (this issue + feature-specific).

[dmz006]

Server-side dependencies for datawatch-app Sprint 2+ are all shipped in v3.0.0 — https://github.com/dmz006/datawatch/releases/tag/v3.0.0

Dependency	Status
FCM push wake (issue #1)	✅ shipped (POST /api/devices/register)
Voice capture / transcription (issue #2)	✅ shipped (POST /api/voice/transcribe)
All-servers fan-out (issue #3)	✅ shipped (GET /api/federation/sessions)

This umbrella tracker stays open for ongoing PWA ↔ mobile parity.
New PWA features landing in the server after v3.0.0 should still
cross-reference here.

Full changelog: docs/plans/RELEASE-NOTES-v3.0.0.md

[dmz006]

Upstream issues from the datawatch-app 2026-04-20 audit

As part of the v0.11 → v0.12 mobile-client work, the parity re-audit against this repo's `openapi.yaml` surfaced 9 parent-side gaps. Issues opened:

Blocking v0.11 shipped-client features (client greys these out on `TransportError.NotFound` today)

• feat(api): POST /api/sessions/delete (single + bulk) #5 — `POST /api/sessions/delete` (single + bulk) — Sessions row overflow Delete + long-press multi-select
• feat(api): GET /api/cert (download server CA cert PEM) #6 — `GET /api/cert` — Settings → Servers "Download CA cert" action
• feat(api): POST /api/backends/active (switch active LLM backend) #7 — `POST /api/backends/active` — Channels tab radio picker

Target mobile v0.13 (deferred from v0.12 pending this work)

• feat(api): /api/channels CRUD + /api/channel/send (messaging backend admin) #8 — `/api/channels` CRUD + `/api/channel/send` — Settings → Comms messaging-backend admin
• feat(api): GET /api/sessions/timeline (session event timeline view) #9 — `GET /api/sessions/timeline` — timeline viewer
• feat(api): GET /api/ollama/models + GET /api/openwebui/models (per-session model pickers) #10 — `GET /api/ollama/models` + `GET /api/openwebui/models` — per-session model pickers
• feat(api): GET /api/logs (daemon log stream / paged) #11 — `GET /api/logs` — daemon log viewer
• feat(api): GET /api/interfaces (network interface list) #12 — `GET /api/interfaces` — network interfaces card
• feat(api): POST /api/restart (daemon self-restart) #13 — `POST /api/restart` — daemon restart affordance

Mobile plan docs cross-linked at:

• docs/parity-plan.md
• docs/plans/2026-04-20-v0.12-schedules-files-config.md (explicit deferred list)

No mobile-side blocker for shipping v0.12 — the confirmed-endpoint scope (schedules, files, saved commands, config read-only, backlog pager) is independent of this list. v0.13 scope is directly gated on the 6 issues above.

[dmz006]

v4.0.3 shipped closing 9 of the 10 child parity issues (#5, #6, #7, #8, #9, #10, #11, #12, #13). New endpoints POST /api/backends/active and GET/PATCH/DELETE /api/channels[/{id}]; seven already-implemented endpoints added to openapi.yaml. The architecture diagram viewer at /diagrams.html landed with the same patch — Mermaid.js client-side render with zoom, pan, reset, and fullscreen toggle across six key diagrams.