v1.2: Multi-client subscription (post-v1 — only if second client materializes) #86

New Issue

2026-05-12T19:31:18Z

KofTwentyTwo commented

2026-05-12 19:31:18 +00:00

(Migrated from github.com)

Summary

Multi-client subscription support, gated on a real second client emerging. `WebviewBridge` is single-client by construction in v1.0 (per F-020). The eval CLI currently uses direct actor calls instead of the API; if a second wire-protocol client appears (Voice Log standalone, remote control, mobile companion), the bridge needs to fan out.

Evidence

Migration plan §10 v1.2: `.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:744`.
F-020 in v1.0 spec: "single client at v1.0."

Gap classification

"design-mapped but not built" — only if needed.

Recommended action

File against v1.2 milestone as a gated item — DO NOT pre-build. If a second client is needed, this becomes a real plan; otherwise stays parked.

Cross-references

Migration plan §10 v1.2

## Summary Multi-client subscription support, gated on a real second client emerging. \`WebviewBridge\` is single-client by construction in v1.0 (per F-020). The eval CLI currently uses direct actor calls instead of the API; if a second wire-protocol client appears (Voice Log standalone, remote control, mobile companion), the bridge needs to fan out. ## Evidence - Migration plan §10 v1.2: \`.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:744\`. - F-020 in v1.0 spec: \"single client at v1.0.\" ## Gap classification \"design-mapped but not built\" — only if needed. ## Recommended action File against v1.2 milestone as a gated item — DO NOT pre-build. If a second client is needed, this becomes a real plan; otherwise stays parked. ## Cross-references - Migration plan §10 v1.2

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/Jarvis#86