update and refresh

skills/sibling-project-updates.md

@@ -2,14 +2,14 @@
 
 ## Overview
 
-CoreDesktop's `coreupdate` script sources every `*.sh` file found in
+CoreDesktop's `update` script sources every `*.sh` file found in
 `~/.local/share/coredesktop/updates.d/` in filename order. A sibling project
 hooks into this system by installing a numbered shell script into that directory
 during its own install step.
 
 ## How It Works
 
-When a user runs `coreupdate`:
+When a user runs `update`:
 
 1. The coredesktop repo at `~/.local/share/coredesktop` is pulled.
 2. All `*.sh` files in `updates.d/` are **sourced** (not executed as subprocesses)
@@ -63,7 +63,7 @@ echo "Registering MyProject update hook..."
 cp updates.d/70-myproject.sh ~/.local/share/coredesktop/updates.d/
 ```
 
-This is a one-time step that wires the sibling into every future `coreupdate`
+This is a one-time step that wires the sibling into every future `update`
 run on the machine.
 
 ## Available Helpers
@@ -84,7 +84,7 @@ remove_packages "${MY_REMOVE_PACKAGES[@]}"
 ## Checklist for Sibling Project Authors
 
 - [ ] Create `updates.d/7X-<project>.sh` in the sibling repo
-- [ ] Hook script echoes its name so progress is visible during `coreupdate`
+- [ ] Hook script echoes its name so progress is visible during `update`
 - [ ] Install step copies the hook to `~/.local/share/coredesktop/updates.d/`
 - [ ] Numeric prefix is 70+ (does not conflict with coredesktop's own hooks)
 - [ ] Script is idempotent — safe to run multiple times without side effects