Adom Hydrogen (platform base)

@@ -1,59 +1,37 @@ --- name: hd-workspace-updater-description: "How Hydrogen Desktop keeps THIS workspace's Adom tooling up to date, and how an Adom employee ships a skill / extension / CLI to EVERY Adom workspace automatically. Use when asked \"how do I get the latest skills or tooling from Adom\", \"how are updates delivered here\", \"what's the reload banner\", \"how do I make a skill that distributes to all Adom users\", \"how do I publish tooling to every workspace\". Trigger words: workspace updater, adom-workspace-updater, latest skills, get updates, how do updates work, auto update, distribute a skill, publish to all users, ship to every workspace, reload banner."+description: How this Hydrogen Desktop workspace's Adom tooling stays up to date (registry-native — the old adom-workspace-updater daemon is retired), and how an Adom employee ships a skill / CLI / app to every workspace. Use when asked "how do I get the latest skills or tooling", "how do updates work here", "what's the reload banner", "how do I distribute a tool to all Adom users", or anything about the retired workspace-updater daemon. Trigger words: workspace updater, adom-workspace-updater, latest skills, get updates, how do updates work, auto update, distribute a skill, publish to all users, reload banner, adom-wiki pkg update. --- -# How this workspace stays up to date — and how to ship to every workspace+# How this workspace stays up to date  ## TL;DR (anyone)-You don't do anything. A gentle background daemon, **`adom-workspace-updater`**, keeps this-workspace's Adom tooling current automatically. It runs **~5 minutes after the workspace-starts**, then **every ~2 hours** — low-priority and **out-of-band** (it is never part of-startup and can't slow or break it). When an update needs the editor reloaded (e.g. a new VS-Code extension landed), Hydrogen Desktop fades in a banner at the top of the editor:-**"<Tool> is ready — click to reload."** Click it. Done.+You don't do anything. Your workspace's Adom tooling is **registry-native**: everything is an+`adom-wiki` package (CLIs, skills, apps), and the **auto-update hook** (`adom/hook`, installed by+`adom/core`) runs `adom-wiki pkg update` in the background (throttled ~30 min, on your prompts, for+both Claude Code and Codex) and re-resolves `adom/core` so newly added tools arrive automatically.+- Force a check now: `adom-wiki pkg update`+- See what's installed / behind: `adom-wiki pkg list` / `adom-wiki pkg outdated` -Why a daemon at all? Your workspace is imaged **once at install and never re-imaged** — so-in-place delivery is the *only* way you ever get new tooling. This daemon is that delivery.--## "How do I get the latest skills / tooling from Adom?"-You already are — automatically. To force a check now instead of waiting:-```-adom-workspace-updater --once-```-It converges this workspace to a wiki **desired-state manifest**: SHA-verified, never-downgrades, and **surgical** — it only touches the specific named tooling, never your files or-anything you installed yourself.-- Installed skill-bundle version: `cat ~/.claude/skills/.hd-skills-version`-- Last run + what changed:        `cat ~/.adom/workspace-updater-status.json`--(code-server and the Claude Code extension are **baked fundamentals** that self-update — the-daemon does *not* manage them; it just notices a change and offers the reload.)--## "How do I make a skill that gets distributed to ALL Adom workspaces automatically?" (Adom employees)-1. Add it to `skills/public-facing/shared/<your-skill>/SKILL.md` in the **hydrogen-desktop** repo.-2. Publish the bundle:-   ```-   scripts/publish-tooling.sh publish-skills-   ```-   (bundles every public hd-* skill, pushes it to the `hd-workspace-tooling` wiki page, bumps the version.)-3. That's it — every workspace's daemon picks it up on its next tick and extracts it into `~/.claude/skills/`.--To distribute an **extension** or a **CLI** instead, add a manifest entry then publish:-```-scripts/publish-tooling.sh add <name> --kind extension --id <publisher.name> --version X   # Open VSX-scripts/publish-tooling.sh add <name> --kind bin --url <wiki blob> --version X              # a CLI-scripts/publish-tooling.sh publish-```-Operator details (the manifest, the kinds, the visibility flow) are in the **`workspace-tooling`**-skill in the hydrogen-desktop repo.+Skills arrive via the **`adom/hd-skillpack`** package (all hd-* workspace skills, symlinked into+`~/.claude/skills/`). Org member apps (e.g. the employee build of adom-google) arrive via your+org's **`org-bootstrap`** meta-package. Both are just dependencies — kept current like everything.  ## The reload banner-When a new version is on disk but not yet active (a daemon-installed extension, or one the-editor auto-updated), HD shows **"<Tool> is ready / has an update — click to reload"** at the-top of the editor; clicking reloads it to activate the new code. **Skills need no reload** —-Claude re-reads them itself.------*Meta: this very skill was delivered to your workspace by the mechanism it describes — which is-the proof that the pipeline works end to end.*+code-server self-updates on disk but only takes effect after a restart. Hydrogen Desktop detects+that natively and shows **"code-server has an update — click to reload"** at the top of the editor+(only after setup is complete, never mid-cascade). Clicking restarts code-server + reloads the+editor. Extensions never banner — VS Code's own auto-update activates them.++## "How do I ship a tool/skill/app to every Adom workspace?" (Adom employees)+Publish it as an `adom-wiki` package, then add it as a **dependency** of the right bootstrap:+- every container: `adom/core` · every HD workspace: `adom/hd-bootstrap` ·+  org members only: your org's `org-bootstrap` · HD skills: add the skill to+  `skills/public-facing/` in the hydrogen-desktop repo and republish `adom/hd-skillpack`.+The hook's re-resolve delivers it fleet-wide within ~30 minutes of users prompting.++## The retired daemon (history)+`adom-workspace-updater` (a systemd timer converging a wiki manifest) previously delivered+tooling in-place. It was retired 2026-07-16 in favor of the registry updater; legacy distros are+migrated off it automatically by its final self-update. If you still see it:+`systemctl status adom-workspace-updater.timer` should be disabled/absent on a migrated workspace.