RAGE #133: migrate CLI and desktop onto ZaraClient #188

Merged

lost-rob0t merged 35 commits from rage/133-client-migration into master

2026-08-24 02:10:05 +00:00

lost-rob0t commented

2026-08-23 17:15:14 +00:00

(Migrated from github.com)

RAGE implementation for #133 under daemon epic #127.

Immutable RAGE start: 4c6018b30ff4be2e168551f0cf256f8333bc58af (exact master after #132 / PR #185 merged).

Research/design and append-only evidence are recorded under rage/133-client-migration*.org.

Implemented/verified direction:

one application-facing ZaraClient boundary for CLI/desktop;
explicit InProcessZaraClient standalone compatibility remains available;
CLI --connect routes text turns through ZmqZaraClient and fails closed rather than silently starting a private runtime;
desktop runtime/event transport is injected through ZaraClient, and client close is distinct from daemon shutdown;
reconnect preserves durable conversation selection, fences stale queued pre-reconnect events, and adds bounded/coalesced retry/backoff;
reuse existing ZARA/1 idempotency, isolation, and #132 voice-device ownership rather than creating parallel stacks;
no Qt-specific wire protocol and no Prolog-RLM path.

Historical exact-head gates #481/#482/#483 passed before master advanced via the docs-only #132 post-merge evidence PR #187. The #133 branch was then synchronized with current master using a normal two-parent merge commit. Current exact head: 3e626b47de7830b5c9ffbd6d516259c0be7b66af. CI #484 is the sole current merge authority; merge only after it is green on this exact SHA.

Closes #133 after the exact-head final gate passes.

RAGE implementation for #133 under daemon epic #127. Immutable RAGE start: `4c6018b30ff4be2e168551f0cf256f8333bc58af` (exact master after #132 / PR #185 merged). Research/design and append-only evidence are recorded under `rage/133-client-migration*.org`. Implemented/verified direction: - one application-facing `ZaraClient` boundary for CLI/desktop; - explicit `InProcessZaraClient` standalone compatibility remains available; - CLI `--connect` routes text turns through `ZmqZaraClient` and fails closed rather than silently starting a private runtime; - desktop runtime/event transport is injected through `ZaraClient`, and client close is distinct from daemon shutdown; - reconnect preserves durable conversation selection, fences stale queued pre-reconnect events, and adds bounded/coalesced retry/backoff; - reuse existing ZARA/1 idempotency, isolation, and #132 voice-device ownership rather than creating parallel stacks; - no Qt-specific wire protocol and no Prolog-RLM path. Historical exact-head gates #481/#482/#483 passed before `master` advanced via the docs-only #132 post-merge evidence PR #187. The #133 branch was then synchronized with current `master` using a normal two-parent merge commit. Current exact head: `3e626b47de7830b5c9ffbd6d516259c0be7b66af`. CI #484 is the sole current merge authority; merge only after it is green on this exact SHA. Closes #133 after the exact-head final gate passes.