diff --git a/skills/freebsd-os-upgrade/SKILL.md b/skills/freebsd-os-upgrade/SKILL.md
index b67a982..0a7ba25 100644
--- a/skills/freebsd-os-upgrade/SKILL.md
+++ b/skills/freebsd-os-upgrade/SKILL.md
@@ -122,7 +122,20 @@ pkg update -f && pkg upgrade      # ports packages (separate from base here)
    PostgreSQL bump needs no dump/restore (restart/reboot to load new binaries).
 7. **Upgrade the jails** — the host upgrade does NOT touch them. Do this after
    the host is on the new kernel. See *Jails* below.
-8. **Vulnerability audit**: if `pkg audit` still flags packages (host or jails),
+8. **Re-register with mother** — the node's OS version changed. Re-run the
+   hardware probe and push the updated profile so the mother's hive_nodes row
+   reflects the new `freebsd_version`. If COLIBRI_AUTOSPAWN is active, the
+   daemon will re-spawn zot on the next tick and the RPC prompt includes
+   node_register; otherwise run the probe + MCP call manually:
+
+   ```sh
+   clawdie-hw-probe | jq .freebsd_version   # confirm 15.1
+   # Re-run node_register via the MCP boundary (or let autospawn handle it)
+   ```
+
+   This is what makes the upgrade visible to the scheduler — without it,
+   the mother still thinks the node is on the old release.
+9. **Vulnerability audit**: if `pkg audit` still flags packages (host or jails),
    do not imply the upgrade failed — the upgrade completed; unrelated packages
    remain vulnerable until fixed versions land. (Wording in the reference.)