mosaicstack/stack
1
0
Fork 1
Code Issues 182 Pull Requests 9 Actions Packages Projects Releases 15 Wiki Activity

feat(fleet): F4 Phase 1 — chat connector abstraction + Matrix design #617

Merged
jason.woltje merged 1 commits from feat/f4-matrix-connector into main 2026-06-22 16:14:33 +00:00
Conversation 0 Commits 1 Files Changed 7
+419 -3
jason.woltje commented 2026-06-22 08:12:06 +00:00
Owner
Copy Link
Copy Source

F4 Phase 1 — orchestrator chat connector abstraction + Matrix design (closes #616 Phase 1)

From the north-star (#613) orchestrator-chat-connector decision. Phase 1 establishes the pluggable connector abstraction (your stated goal) + the Matrix design; the live Matrix wire + UX are Phase 2 follow-ups (scoped in the doc).

What's in it

  • connectors/types.ts — OrchestratorConnector with exactly your interface: send / subscribe / health. Thread-aware via optional threadId so Matrix threads and the future first-party Mosaic Discord plugin (threads) drop in with no interface change. SendResult = ack; health() = liveness.
  • connectors/registry.ts — extensible factory registry; resolveConnectorKind defaults tmux (existing rosters unchanged — back-compat); createConnector throws ConnectorNotImplementedError until Phase 2 registers factories.
  • roster.schema.json — optional connector block (tmux|discord|matrix; matrix homeserver/user/room). Secrets via env (the gateway pattern), never the roster.
  • docs/fleet/f4-matrix-connector.md — interface, config model, Matrix client-server API mapping (fetch-based, homeserver-agnostic), Conduit-default local homeserver (Synapse alt), phasing, back-compat.

Design choices (Lead-aligned)

  • Connectors are peers; fleet core depends only on the interface, never branches on kind.
  • Matrix talks the CS-API directly (no SDK) → dependency-light + homeserver-agnostic.
  • Local homeserver is an infra/deploy concern (Phase-2 guide), not connector code.

Verification

  • 7 connector tests green; tsc/eslint/prettier/sanitize clean; schema valid JSON.

Independence

No fleet.ts changes — a self-contained connectors/ module, so this is independent of the stacked #615 (no rebase coupling). Branches from current main.

Phase 2+ (follow-ups, in the doc)

Matrix CS-API client + factory; fleet init/configure connector-selection UX + roster-parse wiring; systemd launch wiring; Conduit deploy guide; first-party Mosaic Discord (threads) as a connector.

🤖 Generated with Claude Code

## F4 Phase 1 — orchestrator chat connector abstraction + Matrix design (closes #616 Phase 1) From the north-star (#613) orchestrator-chat-connector decision. Phase 1 establishes the **pluggable connector abstraction** (your stated goal) + the Matrix design; the live Matrix wire + UX are Phase 2 follow-ups (scoped in the doc). ### What's in it - **`connectors/types.ts`** — `OrchestratorConnector` with exactly your interface: **`send` / `subscribe` / `health`**. Thread-aware via optional `threadId` so Matrix threads **and the future first-party Mosaic Discord plugin (threads)** drop in with no interface change. `SendResult` = ack; `health()` = liveness. - **`connectors/registry.ts`** — extensible factory registry; `resolveConnectorKind` defaults **tmux** (existing rosters unchanged — back-compat); `createConnector` throws `ConnectorNotImplementedError` until Phase 2 registers factories. - **`roster.schema.json`** — optional `connector` block (`tmux|discord|matrix`; matrix homeserver/user/room). **Secrets via env** (the gateway pattern), never the roster. - **`docs/fleet/f4-matrix-connector.md`** — interface, config model, Matrix **client-server API** mapping (fetch-based, homeserver-agnostic), **Conduit-default** local homeserver (Synapse alt), phasing, back-compat. ### Design choices (Lead-aligned) - Connectors are **peers**; fleet core depends only on the interface, never branches on kind. - Matrix talks the CS-API directly (no SDK) → dependency-light + homeserver-agnostic. - Local homeserver is an **infra/deploy** concern (Phase-2 guide), not connector code. ### Verification - **7 connector tests** green; tsc/eslint/prettier/**sanitize** clean; schema valid JSON. ### Independence **No `fleet.ts` changes** — a self-contained `connectors/` module, so this is independent of the stacked #615 (no rebase coupling). Branches from current main. ### Phase 2+ (follow-ups, in the doc) Matrix CS-API client + factory; `fleet init`/`configure` connector-selection UX + roster-parse wiring; systemd launch wiring; Conduit deploy guide; first-party Mosaic Discord (threads) as a connector. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jason.woltje force-pushed feat/f4-matrix-connector from 85a93428eb to c6735d9949 2026-06-22 13:17:49 +00:00 Compare
jason.woltje merged commit 858d90329d into main 2026-06-22 16:14:33 +00:00
jason.woltje deleted branch feat/f4-matrix-connector 2026-06-22 16:14:33 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
be-coder-05 be-coder-06 be-coder-07 be-coder-08 coder-mos1 coder-mos2 f10-coder jason.woltje (Jason Woltje) merge-gate mos-dt-0 pepper rev-974 (Rev-974 (Mosaic reviewer seat, web1)) rev-security-02
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#617