Adom Hydrogen (macOS / Lima)

⋯ 1 unchanged line ⋯

@@ -1,48 +0,0 @@-----name: hydrogen-workspace-monitoring-description: >-  How Adom Hydrogen's UI monitors the local workspace on macOS: the editor-  panel's health polling, the two health levels (Lima VM up; machine running +-  code-server reachable on the container's port), the in-panel floaty states-  with their Start/Setup actions, and the lifecycle dialog that streams-  start/stop/restart output. Trigger words — workspace stopped, lima vm not-  available, workspace monitoring, start workspace, code-server reachable,-  lifecycle dialog, workspace state.------# Hydrogen Workspace Monitoring (macOS)--Two health levels, probed through the runtime layer:--1. **Lima VM up** — is `hydrogen-builder` responding?-2. **Workspace healthy** — is the container's machine registered AND running-   AND code-server actually answering on that container's port from the Mac?-   ("Machine present" is never trusted as healthy — a machine can run with a-   dead editor.)--The VS Code panel polls workspace state and reacts; `/workspace/health` on the-control API is the same probe for programmatic callers (it reports the FOCUSED-window's container).--## Floaty states (inside the VS Code panel, draggable — never full-app modals)--- **Lima VM not available** (red) → "Run Setup Steps" walks provisioning.-- **Workspace stopped / not ready** (red) → "Start Workspace" runs-  `setup_and_start`; the lifecycle dialog streams progress; when code-server-  answers again the editor iframe auto-reloads.--There is no daemon middle-state (nothing like Docker Desktop to launch): the-VM is up or it isn't; the workspace is healthy or it isn't.--## The lifecycle dialog--`ContainerLifecycleDialog.svelte` — a draggable card showing live output for-start/stop/restart, driven by `hydrogen-container-lifecycle` window events-(`restart|stop|start`, `step`, `done`, `stopped`, `error`). After `done` it-polls code-server health and reloads the editor iframe when it answers.--## Related skills--- `hydrogen-workspace-lifecycle` — what the start/stop/restart actions-  actually do, and the scoping rules-- `hydrogen-networking` — why reachability is probed the way it is