hook

@@ -33,10 +33,21 @@ Under cron, stdout goes to mail or `/dev/null`, so the durable record is `~/.adom/last-update.status` (`running`, or the last exit code) and `~/.adom/last-update.log`. -| Layer | Updates | Cadence |+One pass updates **everything installed**, not just `adom/core`'s tree:++| What | How | Cadence | | --- | --- | --- |-| `adom-wiki` CLI | its own binary | ~2 h, on use |-| `adom/hook` (this) | installed apps + skills | ~30 min, on prompt **or** cron |+| every installed package (apps, skills, bootstraps), including ones you installed yourself | `pkg update` | ~30 min, on prompt **or** cron |+| newly added `adom/core` members | `pkg install adom/core` (update alone never *adds*) | same run |+| the `adom-wiki` CLI itself | just another package -- `adom/core` depends on it | same run |++The CLI is **not** a separate self-updating layer: there is no automatic+self-update and no CLI timer. `adom-wiki self-update` is a manual fallback for the+one case the package path cannot handle (the atomic binary swap failing with+ETXTBSY). If this hook is broken, the CLI goes stale along with everything else.++Components are out of scope: they are wiki content you reference, not packages you+install.  ## Install 

@@ -47,11 +47,24 @@ A failed update is also reported to the next interactive prompt, and the CLI version each container reports to the registry answers "is the fleet current?" fleet-wide (`GET /api/admin/clients?name=adom-wiki-cli`) without SSHing anywhere. -## Two layers of auto-update+## What gets updated -- **CLI layer** -- `adom-wiki` self-updates its own binary on use (throttled ~2h).-- **Content layer (this hook)** -- keeps the installed packages (`adom/core`'s apps-  and skills) current, throttled ~30 min.+**Everything installed, in one pass.** `pkg update` covers every package+`adom-wiki pkg list` shows -- apps, skills and bootstraps -- including ones you+installed yourself from other owners, not just `adom/core`'s tree. Then+`pkg install adom/core` re-resolves core so any NEWLY ADDED member arrives (update+alone only refreshes what you already have; it never adds).++**The CLI is not a separate layer.** `adom/adom-wiki-cli` is an ordinary package+that `adom/core` depends on, so it comes down the same path as everything else, in+the same run. There is no automatic self-update and no separate CLI timer -- the+`self-update` verb is a MANUAL fallback for the one case the package path cannot+handle: if the atomic binary swap ever fails with ETXTBSY ("text file busy"), the+CLI hints you toward it. Do not count on the CLI healing itself; if this hook is+broken, the CLI goes stale with everything else.++**Components are out of scope.** They are wiki content (symbols, footprints, 3D+models) you reference, not packages you install.  ## Controls 

@@ -1,6 +1,6 @@ {   "slug": "hook",-  "version": "1.1.8",+  "version": "1.1.9",   "type": "app",   "org": "adom",   "bundled": true,

@@ -1,6 +1,6 @@ {   "slug": "hook",-  "version": "1.1.8",+  "version": "1.1.9",   "type": "app",   "org": "adom",   "bundled": true,