conductor-update

name	conductor-update
description	Update an installed conductor fleet through its deterministic one-command lifecycle. Use when the user asks to update, upgrade, refresh, reinstall, or deploy conductor.

Update conductor

Run the package-owned lifecycle from a shell or maintenance omp session outside the target Herdr session:

omp-conductor upgrade

If the user requested a published version, run:

omp-conductor upgrade --to X.Y.Z

The command owns the full transaction: release resolution, preflight, pause, drain, exact-version installation across the Bun-global CLI, omp plugin, and Herdr plugin, managed-brief recomposition, process reload, pane recovery, two-pass verification, and restoration of the previous dispatch state.

When it fails on the systemd unit

Since 0.4.0 the command also verifies the unit systemd actually booted from, not just the staged copy. A unit installed before a directive the current configuration requires keeps running without it, and package identities, services, pane and ticks all look perfectly healthy around it, which is why it needed its own check.

The error names the missing directives. Fix it by re-staging rather than by hand-editing the live unit:

# in an omp session
/conductor setup            # amend nothing; it re-renders the unit
# then run the install commands it prints, and:
sudo systemctl daemon-reload && sudo systemctl restart omp-conductor.service
omp-conductor upgrade       # re-run; it now verifies clean

Only directives this configuration requires are checked, so an operator's own MemoryMax, After= or extra Environment= never fails an upgrade.

Report the command's result. Do not reproduce its lifecycle as an AI checklist, edit installed files, publish npm, or substitute separate install/restart steps. If it fails, report the exact error and leave dispatch paused as the command requires.