Repository navigation
fix(remote): distinguish SSH transport from runtime availability - #17710
Conversation
Greptile SummaryThe PR separates SSH/control-transport connectivity from Orca runtime availability while preserving the existing remote protocol.
Confidence Score: 4/5The PR should not merge until the explicit status-bar Connect failure path preserves ready transport diagnostics instead of reverting the host to Disconnected. The previously reported explicit Connect defect remains: its catch handler writes a null status without extracting the RPC error's shared-control diagnostics, so a transport-connected host is still presented with the wrong state and action after the runtime request fails. Files Needing Attention: src/renderer/src/components/status-bar/runtime-environment-explicit-connect.ts
|
| Filename | Overview |
|---|---|
| src/renderer/src/runtime/runtime-host-connection-state.ts | Adds renderer-specific transport-aware runtime connection states and preserves authentication and reconnection progress. |
| src/renderer/src/store/slices/runtime-status.ts | Stores independent transport diagnostics alongside runtime status and coordinates status transitions and rechecks. |
| src/renderer/src/components/status-bar/SshStatusSegment.tsx | Uses entry-level transport diagnostics when deriving status-bar host state and actions. |
| src/renderer/src/components/settings/runtime-environment-host-details.ts | Updates Settings labels, descriptions, and actions to distinguish transport connectivity from runtime availability. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
P[Runtime status probe] -->|Runtime responds| S[RuntimeStatus]
P -->|Probe fails| D[Transport diagnostics]
S --> C[Derive host connection state]
D --> C
C -->|Transport ready, runtime absent| U[Orca unavailable]
C -->|Transport negotiating| K[Checking or reconnecting]
C -->|Transport closed or unknown| X[Disconnected]
Reviews (9): Last reviewed commit: "refactor(runtime): reuse status app stat..." | Re-trigger Greptile
| hasStatusEntry, | ||
| status | ||
| status, | ||
| transportStatus = 'disconnected' |
There was a problem hiding this comment.
When the SSH transport remains connected but the runtime status probe records a null status, the live status-bar caller omits transportStatus, so this default classifies the host as disconnected instead of runtime-unavailable, causing the UI to show unreachable guidance and Connect rather than Orca unavailable and Disconnect.
There was a problem hiding this comment.
Important
The new runtime-unavailable state can never actually be produced, so this PR's headline behavior — showing "Orca unavailable" and keeping Disconnect on a transport-connected host — never reaches either UI surface. The status bar continues to say "Disconnected" and offer Connect for exactly the case this is meant to fix.
Reviewed changes
runtime-host-connection-state.ts— adds aruntime-unavailablestate and atransportStatusinput to the single host-health derivation.- Settings pane (
runtime-environment-host-details.ts,runtime-server-row.tsx) — derives the new state when transport is up but runtime status is absent, and keeps Disconnect available viaisRuntimeServerTransportConnected. - Status-bar row (
RuntimeHostStatusRow.tsx) — renders "Orca unavailable" plus recovery guidance and a Disconnect action. - i18n + tests — new strings and unit tests for the derivation and both surfaces.
⚠️ runtime-unavailable is unreachable from both consumers
The state is only returned by runtimeHostConnectionState when status === null && transportStatus === 'connected'. Neither consumer ever reaches that branch:
- Status bar.
SshStatusSegment.tsx:107callsruntimeHostConnectionState(host)withouttransportStatus, so it stays'disconnected'. Worse, the transport evidence is never independently available there:remoteControlis read asstatusEntry?.status?.remoteControl ?? null, which isnullexactly whenstatusisnull. So theruntime-unavailablebranches added toRuntimeHostStatusRow.tsxare dead code reached only by the new test that injects the state directly. - Settings pane.
getRuntimeServerConnectionStateonly reaches the delegation with a null status whendetails.status === 'ready' && details.runtimeStatus === null && details.compatibility === null. EveryRuntimeHostDetailsproducer (use-runtime-environment-catalog.ts,use-runtime-environment-connection-actions.ts) setsstatus: 'ready'only alongside a non-nullruntimeStatus, and setsruntimeStatus: nullonly alongsidestatus: 'error'/'loading'. That combination cannot occur, soruntime-unavailableis never returned here either.
The new tests pass only because they fabricate the unreachable combination (details({ status: 'ready' }) with null status/compat) or render the row with state="runtime-unavailable" directly — neither exercises a real data flow, so neither can fail if the wiring regresses. The one thing that does actually change in production is incidental: for a non-null status, getRuntimeServerConnectionState now delegates to runtimeHostConnectionState, so Settings rows surface workspace-window-closed/reconnecting/disconnected where they previously always read connected.
Technical details
# `runtime-unavailable` never reaches the UI
## Affected sites
- `src/renderer/src/components/status-bar/SshStatusSegment.tsx:107` — `runtimeHostConnectionState(host)` passes no `transportStatus`; transport evidence (`remoteControl`) is nested inside `status`, so it is null when status is null.
- `src/renderer/src/components/settings/runtime-environment-host-details.ts:183` — `transportStatus: 'connected'` is only supplied when `status === 'ready' && runtimeStatus === null`, a combination its own producers never create.
- `src/renderer/src/components/settings/use-runtime-environment-catalog.ts` — `ready` ↔ non-null `runtimeStatus`; `error`/`loading` ↔ null `runtimeStatus`.
- `src/renderer/src/components/settings/use-runtime-environment-connection-actions.ts` — same invariant (connect/disconnect paths).
## Required outcome
- A transport-connected-but-runtime-silent host must render "Orca unavailable" (yellow, Disconnect) in both the status bar and Settings, rather than "Disconnected"/Connect.
- Transport evidence must be tracked independently of the runtime status RPC result and fed into `runtimeHostConnectionState` at every call site.
## Suggested approach (optional)
- Plumb a transport-level signal (e.g. the shared-control connection state, `sharedControlDiagnostics`, or an explicit environment phase) into `SshStatusSegment` so it can pass `transportStatus` when `status === null` but the control channel is up.
- In Settings, derive transport from an independent source rather than reusing `details.status === 'ready'` (which currently means "status RPC succeeded", conflating transport with runtime).
- Replace the fabrication/injection tests with one that drives the real store → `SshStatusSegment` path and asserts the row outcome.
## Open questions for the human (optional)
- Is the intended fix to make `details.status` mean "transport phase" (and add a transport phase to the catalog), or to keep transport separate from `RuntimeStatus`? The catalog currently has no notion of "transport up, status failed".DeepSeek Pro (free via Pullfrog for OSS) | 𝕏
|
Review status: do not land as-is. Findings:
Validation:
Recommended next step: thread the preserved failed-RPC transport diagnostics into the runtime status model and cover the real failed- |
PR #17710 Electron UI validationApp identityLaunched this worktree with isolated profile + CDP:
No source files were edited. What was exercisedIsolated profile has no real SSH/OpenClaw host. Saved runtime environments were seeded into the isolated profile ( Status bar — Remote Hosts dropdown (live derivation)Uncropped screenshot: Visible text:
The status bar overall chip showed Finding: Settings > Remote Orca Servers — product path (failed
|
|
Follow-up correction to the earlier review note: the orchestrated Grok Electron run did complete after the initial startup stall. It verified the intended worktree identity, exercised the status-bar Remote Hosts menu and Settings > Remote Orca Servers, and attached three uncropped screenshots to this PR. The screenshots show:
This strengthens the P2 finding: the requested behavior is implemented in components but is not wired into the real failure paths. No source files were edited. No real SSH/OpenClaw host was available, so transport-up/runtime-down was not exercised against a live remote tunnel. |
|
Review complete for commit 6137ac4. Status: land after fixes.
The branch is pushed and the worktree is clean. |
There was a problem hiding this comment.
ℹ️ No new issues in this delta. The status-bar transport wiring is correct and
runtime-unavailableis now genuinely reachable there. The Settings-pane arm of the earlier review is still not wired, so I'm leaving that thread open rather than approving.
Reviewed changes
- Tracked transport evidence independently of runtime status — failed
status.getprobes now publish the shared-controlremoteControldiagnostics (extractRuntimeTransportDiagnostics) ontoRuntimeEnvironmentStatusinruntime-status-refresh,runtime-status-recheck, and the catalog/connection hooks. - Derived
runtime-unavailablefrom the transport in the status bar —runtimeHostConnectionStategains aremoteControlinput that maps a ready transport + null status toruntime-unavailable, andSshStatusSegmentfeeds the store-levelremoteControlin. - Extended the execution-host registry —
runtimeHealthreportsavailablewhen a ready shared-control socket proves the transport is up, even without a status payload. - Replaced fabricated tests with real-flow coverage — the refresh/recheck tests drive the failure → error → diagnostics → store path and would fail if the extraction wiring regressed.
ℹ️ Nitpicks
execution-host-registry.tsreportsavailable(green) for a ready transport with null status, while the status bar reportsruntime-unavailable(yellow) for the same underlying state. The two surfaces now describe the identical condition with different vocabularies — worth confirming the picker's "available" is the intended read of a transport-up-but-runtime-silent host.
DeepSeek Pro (free via Pullfrog for OSS) | 𝕏
There was a problem hiding this comment.
✅ No new issues found. The transport diagnostics are now wired through every consumer — Settings, status bar, and the host-setup section — so
runtime-unavailableis genuinely reachable, and the stale-compat guard prevents an errored probe from readingconnected.
Reviewed changes
- Propagated transport diagnostics into the Settings pane —
RuntimeHostDetailsgainsremoteControl;getRuntimeServerConnectionStatenow delegates with that evidence plus aready/disconnectedtransport status, so a failed probe with a ready shared-control socket returnsruntime-unavailableinstead ofdisconnected. - Populated
remoteControlfrom failed probes — the catalog and connection-action hooks both set the details field fromextractRuntimeTransportDiagnosticson the error path. - Refined the shared derivation — a null status with a reconnecting or handshaking transport now reads
reconnecting/checkingrather thandisconnected, andruntime-unavailableis folded into the connected-host totals. - Kept unavailable runtime owners out of
Readysetups —RepositoryHostSetupsSectionexcludesruntime-unavailableowners fromsetupReadyand labels themUnknown. - Added real-path coverage — tests now drive the error + transport-diagnostics flow, the stale-compat guard, and the host-setup section against the live store.
DeepSeek Pro (free via Pullfrog for OSS) | 𝕏
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 10 included reviews per hour; 4 remain after this review. 📝 WalkthroughWalkthroughThe change adds a Merge Risk: 🟡 Moderate · up to Some transport-connected hosts may still show Connect instead of Disconnect, preventing users from intentionally disconnecting them, while reconnecting diagnostics may suppress automatic recovery retries and leave runtimes unavailable until manual action. The PR is not merge-ready until these bounded behavior issues are fixed or explicitly accepted. 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
Full details: Description checkExplanation The description explains the implementation and testing, but it omits most required template sections, including ELI5, What Changed, Why, Linked Issue, Visual Proof, AI Disclosure, Review, Agent skill boundary, Notes, and Checklist. Resolution Complete the required template sections. Add the linked issue after
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Team
Run ID: c900bdc8-f899-4ccb-85c7-712fe9d211e0
📒 Files selected for processing (23)
src/renderer/src/components/settings/RepositoryHostSetupsSection.tsxsrc/renderer/src/components/settings/RepositoryHostSetupsSection.workspace-window.test.tsxsrc/renderer/src/components/settings/RuntimeEnvironmentsPane.test.tssrc/renderer/src/components/settings/RuntimeEnvironmentsPane.tsxsrc/renderer/src/components/settings/runtime-environment-host-details.tssrc/renderer/src/components/settings/runtime-server-row.tsxsrc/renderer/src/components/settings/use-runtime-environment-catalog.tssrc/renderer/src/components/settings/use-runtime-environment-connection-actions.tssrc/renderer/src/components/status-bar/RuntimeHostStatusRow.test.tsxsrc/renderer/src/components/status-bar/RuntimeHostStatusRow.tsxsrc/renderer/src/components/status-bar/SshStatusSegment.tsxsrc/renderer/src/i18n/locales/en.jsonsrc/renderer/src/runtime/runtime-host-connection-state.test.tssrc/renderer/src/runtime/runtime-host-connection-state.tssrc/renderer/src/runtime/runtime-status-probe-diagnostics.tssrc/renderer/src/store/slices/runtime-status-recheck.test.tssrc/renderer/src/store/slices/runtime-status-recheck.tssrc/renderer/src/store/slices/runtime-status-refresh-diagnostics.test.tssrc/renderer/src/store/slices/runtime-status-refresh.tssrc/renderer/src/store/slices/runtime-status.tssrc/shared/execution-host-registry.test.tssrc/shared/execution-host-registry.tssrc/shared/runtime-host-connection-state.ts
Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review.
| if (details.compatibility?.kind === 'blocked') { | ||
| return 'disconnected' | ||
| } |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Preserve transport connectivity for blocked runtimes.
A blocked compatibility verdict comes from a successful runtime status probe. Returning disconnected here discards that transport evidence. RuntimeServerRow then shows Connect instead of Disconnect, so users cannot disconnect an already connected incompatible host.
Let runtimeHostConnectionState derive transport state. It already handles a closed transport correctly.
Proposed fix
- if (details.compatibility?.kind === 'blocked') {
- return 'disconnected'
- }📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| if (details.compatibility?.kind === 'blocked') { | |
| return 'disconnected' | |
| } |
| runtimeStatusRecheck.reconcileRuntimeStatusRecheck({ | ||
| environmentId, | ||
| status: status.status, | ||
| connectionGeneration: getRuntimeEnvironmentConnectionGeneration(environmentId), | ||
| environmentExists: () => | ||
| get().runtimeEnvironments.some((environment) => environment.id === environmentId), | ||
| getConnectionGeneration: () => getRuntimeEnvironmentConnectionGeneration(environmentId), | ||
| publish: (entry) => get().setRuntimeEnvironmentStatus(environmentId, entry) | ||
| }) |
There was a problem hiding this comment.
🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
Keep retry eligibility when diagnostics report reconnecting.
This call passes only status.status. After fireRuntimeStatusRecheck publishes a failed probe with remoteControl.state equal to reconnecting or handshaking, this becomes null; shouldRecheck(null) then cancels the retry loop. The host remains unavailable until another path manually refreshes it.
Pass the complete entry into reconciliation, and retain recheck eligibility from transport diagnostics for an already eligible remote-control host.
There was a problem hiding this comment.
Caution
The origin/main merge resolved the runtime-status.ts conflict by dropping #17531's publishRuntimeEnvironmentDiagnostics action, but left main's callsite in place — so the renderer now invokes a store method that no longer exists. pnpm tc fails, runtime-status-diagnostics.test.ts fails, and the shared-control diagnostics bridge throws at runtime on every transport-outage event (silently reverting the already-shipped "publish remote control outages to host surfaces" behavior).
Reviewed changes
- Merged
origin/maininto the branch — pulled in ~70 commits, most importantly #17531, whose files overlap heavily with this PR (runtime-status.ts,runtime-host-connection-state.ts,runtime-environment-host-details.ts,runtime-server-row.tsx,runtime-status-recheck.ts,en.json). - Kept this PR's
runtime-status.tswholesale — the merge left inline connection-generation tracking and the directreconcileRuntimeStatusRecheckcall, discarding #17531's extractedruntime-status-connection-generation.tsand its diagnostics-publish action. - Replaced #17531's
runtime-host-connection-statere-export with a duplicate — the renderer file went back to a full local implementation, while the shared module (also used by CLI/main/contracts) carries an identical derivation.
🚨 Merge dropped #17531's publishRuntimeEnvironmentDiagnostics
The merged tree is internally inconsistent: app-lifetime-ipc-bridge.ts and runtime-status-diagnostics.test.ts still call publishRuntimeEnvironmentDiagnostics, but RuntimeStatusSlice/createRuntimeStatusSlice no longer declare or implement it, so the method is absent from AppState. This reverts the already-merged shared-control diagnostics push and crashes the renderer the first time an outage event arrives.
Technical details
# Re-integrate #17531's diagnostics-publish wiring that the merge dropped
## Affected sites
- `src/renderer/src/hooks/ipc-events/app-lifetime-ipc-bridge.ts:67` — calls `useAppStore.getState().publishRuntimeEnvironmentDiagnostics(event)`; the method is absent from `AppState` → typecheck error + runtime `TypeError` on the `onSharedControlDiagnostics` path.
- `src/renderer/src/store/slices/runtime-status-diagnostics.test.ts:44,58,73` — calls the same missing method; the test cannot compile or pass.
- `src/renderer/src/store/slices/runtime-status.ts` — the diff removes `publishRuntimeEnvironmentDiagnostics` (type + `createRuntimeEnvironmentDiagnosticsPublisher` impl), the `runtime-status-diagnostics-*` / `runtime-status-connection-generation` imports, and the `reconcileRuntimeStatusForSlice` call.
- `src/renderer/src/store/slices/runtime-status-diagnostics-publish.ts:57` — `createRuntimeEnvironmentDiagnosticsPublisher` is now exported but never invoked; `runtime-status-diagnostics-generation.ts` and `runtime-status-connection-generation.ts` are orphaned.
## Required outcome
- `publishRuntimeEnvironmentDiagnostics` must exist on the store again (declared in `RuntimeStatusSlice`, implemented via `createRuntimeEnvironmentDiagnosticsPublisher` in `createRuntimeStatusSlice`), so the `onSharedControlDiagnostics` bridge resumes pushing transport diagnostics into `runtimeStatusByEnvironmentId` and the diagnostics test passes.
- The orphaned `runtime-status-connection-generation.ts` / `runtime-status-diagnostics-*` modules must be re-wired or removed so no dead module ships.
## Suggested approach (optional)
- Re-apply #17531's `runtime-status.ts` delta (`aabcc57366`) on top of this PR's status-tracking changes: restore `publishRuntimeEnvironmentDiagnostics`, re-export `runtime-status-connection-generation`, and switch the recheck call to `reconcileRuntimeStatusForSlice`.
## Open questions for the human (optional)
- Is #17531's main-side push path (live outage broadcasts) meant to coexist with this PR's probe-error pull path (`extractRuntimeTransportDiagnostics`)? They feed the same `remoteControl` state from different sources, so dropping the push regresses the behavior already shipped on `main`.ℹ️ Nitpicks
- The merge now carries two identical
runtimeHostConnectionStateimplementations —src/shared/runtime-host-connection-state.ts(used by CLI/main/contracts) andsrc/renderer/src/runtime/runtime-host-connection-state.ts(used by the renderer). #17531 had already made the renderer a re-export of the shared module; this PR reverted that to a full local copy. Restore the re-export (export { ... } from '../../../shared/runtime-host-connection-state') so the derivation stays in one place.
DeepSeek Pro (free via Pullfrog for OSS) | 𝕏
There was a problem hiding this comment.
ℹ️ The dropped-diagnostics regression from the
origin/mainmerge is fixed —publishRuntimeEnvironmentDiagnosticsis re-integrated, the orphaned diagnostics/connection-generation modules are re-wired, and the i18n keys are preserved. One minor consistency nitpick remains.
Reviewed changes
- Re-integrated
publishRuntimeEnvironmentDiagnostics— the slice type andcreateRuntimeStatusSlicerestore the method, re-exportruntime-status-connection-generation, and route the recheck throughreconcileRuntimeStatusForSlice, soapp-lifetime-ipc-bridge.tsandruntime-status-diagnostics.test.tswork again. - Preserved i18n keys across the merge —
serverReconnecting(and the surrounding settings strings) survived theen.jsonmerge rather than being dropped. - Refreshed the settings row from the store —
RuntimeServerRowre-readsruntimeStatusByEnvironmentIdand deriveseffectiveDetails, folding store status/compatibility/remoteControlinto the connection state, label, and description.
ℹ️ Nitpicks
RuntimeServerRow(runtime-server-row.tsxline 117) still computes the summary line from the rawdetailsprop (getHostDetailsSummary(details)) while the dot, label, and description now derive fromeffectiveDetails. When the catalog has not yet produceddetails(or it lags the store), the row shows a store-derived label ("Orca unavailable" / "Connected") alongside a "Checking…" summary. PassingeffectiveDetailstogetHostDetailsSummarywould keep every part of the row on the same source.
DeepSeek Pro (free via Pullfrog for OSS) | 𝕏
There was a problem hiding this comment.
✅ No new issues found. The two follow-up commits cleanly resolve the remaining nitpick —
getHostDetailsSummarynow readseffectiveDetails— and consolidate connection-generation access through theruntime-status-connection-generationmodule while clearing diagnostics generations on test reset.
Reviewed changes
- Refreshed the availability summary from the store —
RuntimeServerRownow feedsgetHostDetailsSummary(effectiveDetails)and theblockedstyling fromeffectiveDetails, so the summary line, dot, label, and description all derive from the same store-backed source. - Consolidated connection-generation access —
runtime-status.tsroutes every generation read/advance through theruntimeStatusConnectionGenerationnamespace and clears diagnostics generations inclearRuntimeEnvironmentConnectionGenerationsForTests, matching the pre-merge #17531 structure.
DeepSeek Pro (free via Pullfrog for OSS) | 𝕏
|
Review complete for PR #17710 at commit 0691ed3. Status: land after fixes.
GitHub currently reports MERGEABLE. |
|
Update: final CI-blocking lint issue is fixed structurally and pushed.
|
There was a problem hiding this comment.
ℹ️ No critical issues — the type split and publisher extraction are behavior-preserving. One minor suggestion inline about the JSDoc that got dropped in the move.
Reviewed changes
- Split the status-slice types into
runtime-status-types.ts—RuntimeEnvironmentStatus,RuntimeStatusRefreshOptions, andRuntimeStatusSlicemoved out ofruntime-status.tsand are re-exported unchanged, preserving every field and the namedpublishRuntimeEnvironmentDiagnosticsargs. - Reused the app-store type in the diagnostics publisher — extracted
createRuntimeEnvironmentDiagnosticsSlicePublisherfrom the inline closure inruntime-status.ts, threadinggetStoreandgetConnectionGenerationthrough so thereconcileRuntimeStatusForSlicecall is byte-for-byte equivalent.
DeepSeek Pro (free via Pullfrog for OSS) | 𝕏
| import type { RuntimeStatus } from '../../../../shared/runtime-types' | ||
| import type { RemoteRuntimeSharedConnectionDiagnostics } from '../../../../shared/remote-runtime-shared-control-types' | ||
|
|
||
| export type RuntimeEnvironmentStatus = { |
There was a problem hiding this comment.
This refactor dropped the JSDoc that documented the non-obvious invariants behind these types. Worth restoring: publishUnreachable maps a failed probe to unverifiable per docs/reference/ssh-execution-boundary.md, checkedAt records the last observed change (not a probe-freshness clock), and the RuntimeStatusSlice fields encode the fail-closed hydration gate and the #8881 tombstone-set rationale.
|
Final validation update: PR #17710 is fully validated at 1beccd6.
The checks that are marked skipped are unrelated optional gates (for example mobile/IME/shell/cross-version suites) and were correctly not selected for this diff. |
|
Live OpenClaw target check clarification:
Conclusion: real SSH reachability and real OpenClaw-host presence are confirmed, but the exact transport-connected/runtime-unavailable UI state remains unverified because the saved runtime endpoint was not reachable/authenticated from the isolated PR build. |
|
Final OpenClaw/SSH validation correction for
|
…blyai#17710) * fix(remote): distinguish transport from runtime availability * fix(remote): preserve transport diagnostics for unavailable runtime * fix(remote): propagate transport diagnostics to host setups * fix(remote): keep unavailable runtimes out of ready setups * fix(remote): preserve unavailable runtime state in settings * fix(remote): preserve reconnecting runtime state * fix(remote): guard stale settings connectivity * fix(remote): preserve diagnostics after main merge * fix(i18n): preserve translations during runtime status merge * fix(remote): refresh settings row health from store * fix(remote): refresh settings row health from store * fix(remote): clear diagnostics generations in tests * fix(settings): refresh runtime availability summary * refactor(runtime): split status slice types * refactor(runtime): reuse status app state type --------- Co-authored-by: Merge Sim <sim@local>





Summary
Orca unavailablewith recovery guidance instead of implying the remote process exitedTests
pnpm test src/renderer/src/runtime/runtime-host-connection-state.test.ts src/renderer/src/components/settings/RuntimeEnvironmentsPane.test.ts src/renderer/src/components/status-bar/RuntimeHostStatusRow.test.tsx(27/27)pnpm tcpnpm tc:webpnpm run check:code-quality:changedgit diff --checkValidation notes
Orca: brennanb2025/remote-runtime-status) with an isolated profile.openclaw 6768environment was seeded into that isolated profile. A realruntimeEnvironments.getStatuscall succeeded against runtime086913a1-a7a8-4eb0-a3c5-826b34e4467bon Orca1.4.190, and the rendered Remote Hosts menu showedopenclaw 6768 · Remote Server · Connectedwith Disconnect.16770Orca instance was killed by systemd-oomd; with no supervisor, the later normal GUI relaunch bound the default6768port after an interactive keyring-unlock delay. The fresh pairing is healthy; the old saved endpoint is stale configuration, not a defect in this PR.Orca unavailable.