[Phase 3] Add the optional StarIntel HTTP/WebSocket integration adapter #22

New issue

Closed

opened 2026-07-25 21:55:04 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-25 21:55:04 +00:00

(Migrated from github.com)

Parent: #2
Depends on: #7, #18, #21

Scope

Define a typed integration boundary for search, import, action discovery, action invocation, progress events, and reconnect.
Use native Fetch and WebSocket only.
Model disconnected, connecting, connected, degraded, reconnecting, and disabled states with XState.
Keep remote data in TanStack Query caches until explicitly imported through a graph batch.
Support fixture servers and recorded traces for testing.

Acceptance criteria

Quasar UI runs normally with the adapter disabled.
Remote search results do not become canonical graph data until imported.
Reconnect uses stable invocation or revision identifiers where available.
Stale remote responses cannot overwrite newer local state.
Authentication material is never persisted in exported graph documents.

Parent: #2 Depends on: #7, #18, #21 ## Scope - Define a typed integration boundary for search, import, action discovery, action invocation, progress events, and reconnect. - Use native Fetch and WebSocket only. - Model disconnected, connecting, connected, degraded, reconnecting, and disabled states with XState. - Keep remote data in TanStack Query caches until explicitly imported through a graph batch. - Support fixture servers and recorded traces for testing. ## Acceptance criteria - Quasar UI runs normally with the adapter disabled. - Remote search results do not become canonical graph data until imported. - Reconnect uses stable invocation or revision identifiers where available. - Stale remote responses cannot overwrite newer local state. - Authentication material is never persisted in exported graph documents.