mirror of
https://github.com/openclaw/openclaw.git
synced 2026-08-15 07:04:01 -06:00
Vyctor H. Brzezowski
3f006ba0fc
* fix(ui): complete pairing setup lifecycle Redeemed and expired mobile setup codes stayed on screen as usable QR codes, so a successful pairing had no visible outcome and expired bearer material still looked live. The Gateway now mints an opaque, non-authorizing setupId beside each setup credential, returns its authoritative expiresAtMs, records the terminal outcome of the exact redemption, and broadcasts device.pair.setup.completed. Because that broadcast is dropped for buffered operator sockets, the completion is persisted first and can be reconciled through the new device.pair.setupStatus method: the Control UI asks for the recorded outcome before it may present a credential as expired, so a pairing that succeeds is never shown as a failure. The Control UI models one closed lifecycle (selection, loading, waiting, success, expired, error) correlated only by the active setupId, and Pairing help now carries the external-link affordance. * fix(ui): preserve unknown pairing outcomes * test(ui): target pairing terminal headings * test(ui): align pairing completion fixture * fix(gateway-protocol): decode setup-code results from older gateways Older protocol-v4 gateways omit the new setupId and expiresAtMs lifecycle fields, so requiring them in the generated native model broke decoding an existing device.pair.setupCode response. Keep both optional at the wire boundary, require lifecycle metadata before the Control UI enters its waiting state so a missing outcome stays visible, and cover the legacy payload with Swift and schema regressions. * fix(ui): surface rejected pairing dialog loads The lazy pairing chunk could reject while its overlay was already open, leaving the shell rendering nothing at all. Record the rejection on the shell and render a recoverable modal with a reason and a retry so the open action always ends in a visible outcome. * fix(state): preserve pairing setup schema compatibility * test(gateway): cover pairing setup release train * fix(gateway): commit pairing setup completion atomically * refactor(state): distinguish setup transaction helpers * refactor(state): remove obsolete bootstrap restore path * fix(gateway): preserve setup handoff type safety * fix(gateway): keep pairing completion terminal after consume * fix(gateway): validate Watch binding during setup commit * fix(gateway): revalidate setup credential expiry at commit * chore: refresh Plugin SDK API contracts after rebase * fix(pairing): prune expired setup completions * chore: retrigger CI * fix(protocol): deduplicate setup expiry field * fix(protocol): refresh pairing setup clients * fix(gateway): make pairing setup completion durable * fix(ui): retire expired pairing credentials immediately * fix(ui): keep pairing dialog visible while loading * fix(macos): align setup result initializer order * fix(gateway): restore generic bootstrap retries * chore(ui): record pairing startup budget * chore(ui): refresh pairing startup budget * style(gateway): format maintenance imports * test(gateway): cover session-sharing mock * fix(state): defer setup correlation schema --------- Co-authored-by: Patrick Erichsen <patrick.a.erichsen@gmail.com>
72 lines
7.8 KiB
JSON
72 lines
7.8 KiB
JSON
{
|
|
"$comment": "Gateway events each mobile client intentionally does not handle yet, with a one-line reason. Consumed by scripts/check-protocol-event-coverage.mjs (pnpm check:protocol-coverage). Adding a gateway event without a client handler requires either handling it or adding an entry here; the check also fails when an entry goes stale (event removed or now handled).",
|
|
"ios": {
|
|
"controlUi.sessionPullRequests.changed": "Sidebar PR indicators are a Control UI surface; native apps do not render session PR chips.",
|
|
"cron": "Cron run activity is not surfaced in the iOS app.",
|
|
"device.pair.requested": "Device pairing flows poll via device.pair.* methods on iOS.",
|
|
"device.pair.resolved": "Device pairing flows poll via device.pair.* methods on iOS.",
|
|
"device.pair.setup.completed": "Generated setup lifecycle is a Control UI surface; iOS direct Watch setup completes through Watch connectivity.",
|
|
"device.pair.setup.deliveryUncertain": "Generated setup recovery is a Control UI surface; native clients receive the handoff response directly.",
|
|
"heartbeat": "iOS liveness uses tick and WebSocket-level ping; heartbeat is unused.",
|
|
"node.pair.requested": "Node pairing state is fetched on demand; no push consumer on iOS yet.",
|
|
"node.pair.resolved": "Node pairing state is fetched on demand; no push consumer on iOS yet.",
|
|
"node.presence": "Node activity is reported by macOS nodes and consumed by gateway routing; iOS has no presence reporter yet.",
|
|
"node.runnerInventory.changed": "Session-host placement refresh is a Control UI surface; iOS does not offer device runner placement yet.",
|
|
"openclaw.approval.requested": "OpenClaw system-agent config approvals are a web/desktop operator surface; iOS has no operator-approval prompt.",
|
|
"openclaw.approval.resolved": "OpenClaw system-agent config approvals are a web/desktop operator surface; iOS has no operator-approval prompt.",
|
|
"plugin.approval.requested": "Plugin approval prompts are not implemented on iOS.",
|
|
"plugin.approval.resolved": "Plugin approval prompts are not implemented on iOS.",
|
|
"portal.changed": "Control-UI-only surface; native apps have no portal viewer yet.",
|
|
"presence": "Presence roster is a control-UI (web/desktop) surface; iOS does not render it.",
|
|
"session.approval": "Native approval review uses exec.approval push/nudge delivery; the session-scoped approval stream is a Control UI chat surface.",
|
|
"session.operation": "Chat UI derives run state from chat/agent events; no session.operation consumer yet.",
|
|
"session.sharing": "Session visibility/membership management is a Control UI operator surface; iOS reads visibility/sharingRole from session rows and has no sharing editor.",
|
|
"session.suggestion": "The suggestion queue is a Control UI collaboration surface; iOS does not render or resolve session suggestions.",
|
|
"session.tool": "Session tool stream is not rendered by the iOS chat surface yet.",
|
|
"session.typing": "Collaborative typing state is a Control UI-only ephemeral indicator; iOS does not render it.",
|
|
"shutdown": "iOS relies on socket close plus reconnect/backoff instead of the shutdown notice.",
|
|
"skills.changed": "Skills settings is a macOS operator surface; iOS does not expose skill management yet.",
|
|
"task.suggestion": "Task suggestion cards are a Control UI-only surface; iOS does not render them.",
|
|
"terminal.data": "Embedded terminal is a web/desktop surface; iOS has no terminal client.",
|
|
"terminal.exit": "Embedded terminal is a web/desktop surface; iOS has no terminal client.",
|
|
"ui.command": "Web Control UI-only layout commands; iOS does not consume them.",
|
|
"update.available": "Gateway self-update notices do not apply to iOS; app updates ship via the App Store.",
|
|
"voicewake.routing.changed": "iOS only consumes voicewake.changed trigger updates; routing changes are not surfaced."
|
|
},
|
|
"android": {
|
|
"controlUi.sessionPullRequests.changed": "Sidebar PR indicators are a Control UI surface; native apps do not render session PR chips.",
|
|
"cron": "Cron run activity is not surfaced in the Android app.",
|
|
"device.pair.requested": "Device pairing flows poll via device.pair.* methods on Android.",
|
|
"device.pair.resolved": "Device pairing flows poll via device.pair.* methods on Android.",
|
|
"device.pair.setup.completed": "Generated setup lifecycle is a Control UI surface; Android consumes setup codes but does not issue or track them.",
|
|
"device.pair.setup.deliveryUncertain": "Generated setup recovery is a Control UI surface; Android consumes setup codes but does not issue or track them.",
|
|
"heartbeat": "Android liveness uses tick and WebSocket-level ping; heartbeat is unused.",
|
|
"node.invoke.cancel": "Cancel targets streaming agent.cli.claude.run.v1 invokes; app nodes never advertise agent runs, so no cancel can address them.",
|
|
"node.invoke.input": "Carries terminal keystrokes/resize to a node PTY relay invoke; the relay runs on gateway/CLI node hosts and app nodes never host it, so Android has no consumer.",
|
|
"node.pair.requested": "Android's bounded operator session lacks operator.pairing; onboarding refreshes node approval with explicit node.list requests.",
|
|
"node.pair.resolved": "Android's bounded operator session lacks operator.pairing; onboarding refreshes node approval with explicit node.list requests.",
|
|
"node.presence": "Node activity is reported by macOS nodes and consumed by gateway routing; Android has no presence reporter yet.",
|
|
"node.runnerInventory.changed": "Session-host placement refresh is a Control UI surface; Android does not offer device runner placement yet.",
|
|
"openclaw.approval.requested": "OpenClaw system-agent config approvals are a web/desktop operator surface; Android has no operator-approval prompt.",
|
|
"openclaw.approval.resolved": "OpenClaw system-agent config approvals are a web/desktop operator surface; Android has no operator-approval prompt.",
|
|
"plugin.approval.requested": "Plugin approval prompts are not implemented on Android.",
|
|
"plugin.approval.resolved": "Plugin approval prompts are not implemented on Android.",
|
|
"portal.changed": "Control-UI-only surface; native apps have no portal viewer yet.",
|
|
"presence": "Presence roster is a control-UI (web/desktop) surface; Android does not render it.",
|
|
"session.approval": "Native approval review uses exec.approval push/nudge delivery; the session-scoped approval stream is a Control UI chat surface.",
|
|
"session.operation": "Chat UI derives run state from chat/agent events; no session.operation consumer yet.",
|
|
"session.sharing": "Session visibility/membership management is a Control UI operator surface; Android reads visibility/sharingRole from session rows and has no sharing editor.",
|
|
"session.suggestion": "The suggestion queue is a Control UI collaboration surface; Android does not render or resolve session suggestions.",
|
|
"session.tool": "Session tool stream is not rendered by the Android chat surface yet.",
|
|
"session.typing": "Collaborative typing state is a Control UI-only ephemeral indicator; Android does not render it.",
|
|
"shutdown": "Android relies on socket close plus reconnect/backoff instead of the shutdown notice.",
|
|
"skills.changed": "Skills settings is a macOS operator surface; Android does not expose skill management yet.",
|
|
"talk.mode": "Android toggles talk mode locally; gateway talk.mode sync is not consumed.",
|
|
"task.suggestion": "Task suggestion cards are a Control UI-only surface; Android does not render them.",
|
|
"terminal.data": "Embedded terminal is a web/desktop surface; Android has no terminal client.",
|
|
"terminal.exit": "Embedded terminal is a web/desktop surface; Android has no terminal client.",
|
|
"ui.command": "Web Control UI-only layout commands; Android does not consume them.",
|
|
"voicewake.routing.changed": "Android reads voicewake state on demand via voicewake.get; no push consumer yet."
|
|
}
|
|
}
|