omp-conductor 0.3.16 → 0.3.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +15 -10
  2. package/package.json +1 -1
  3. package/skills/conductor-update/SKILL.md +112 -90
package/README.md CHANGED
@@ -39,7 +39,7 @@ The package ships three deployables, plus two skills:
39
39
  | Standalone daemon | `omp-conductor` binary | The dispatch loop, managed as a background process (`start` / `stop` / `restart`) with a `/healthz` endpoint for a supervisor. |
40
40
  | Orchestrator heartbeat | omp extension, activated by `.conductor-tick.json` | Prompts a 24/7 orchestrator session on a fixed interval so its standing loop actually runs, and marks the session stalled when its prompts stop being consumed. Inert in every other session — including a second session opened in the fleet's own directory. See [Orchestrator tick](#orchestrator-tick). |
41
41
  | Onboarding skill | `skill://conductor-onboarding` | Directs an omp session to interview you, read your repos for real CI gates, and tailor `ORCHESTRATOR.md` — then finish through the wizard. Discovered automatically once the plugin is installed. See [Onboarding](#onboarding). |
42
- | Update skill | `skill://conductor-update` | Treats the npm and Herdr plugins as one maintenance operation: drain, halt, replace both halves, restart, re-arm through Telegram proof, and verify twice. See [Updating](#updating). |
42
+ | Update skill | `skill://conductor-update` | Treats the Bun-global CLI, omp plugin, and Herdr plugin as one operation: pause claims, drain, install one pinned release, reload, verify twice, and restore the prior pause state. See [Updating](#updating). |
43
43
 
44
44
  The first two are thin wrappers over the same `daemon.ts`, so the plugin and the
45
45
  CLI cannot disagree about what a cap means or where the state lives. Claiming is
@@ -169,15 +169,20 @@ Also required on the host:
169
169
  ## Updating
170
170
 
171
171
  Say “update conductor” from an operator shell or maintenance omp session outside
172
- the target `herdr-fleet.service`. The bundled `skill://conductor-update` discovers
173
- the installed and registry versions, drains active work, pins exact-pane recovery,
174
- replaces both independently installed plugins, restarts through
175
- `omp-conductor start`, re-arms through the existing Telegram proof, and verifies
176
- the layered status twice.
177
-
178
- The skill deliberately does not publish npm or edit an install root. It also
179
- refuses to run from the fleet pane it must replace: an updater that kills itself
180
- cannot verify the result. With skill commands enabled, invoke it directly with:
172
+ the target `herdr-fleet.service`. That is the whole operator interface. The bundled
173
+ `skill://conductor-update` discovers the installed and registry versions, pauses
174
+ new claims while active work drains, and pins one release across the Bun-global
175
+ CLI, omp plugin, and Herdr plugin. It converts an old local Herdr link to a managed
176
+ checkout when necessary, reloads the Herdr service and dispatch daemon, verifies
177
+ the layered status twice, and restores the original dispatch state.
178
+
179
+ Ticks remain in their existing armed or disarmed state, so an ordinary update
180
+ does not halt the exact pane or require another Telegram arm challenge. Any
181
+ installation, reload, or verification failure leaves dispatch paused instead of
182
+ bringing up a mixed fleet. The skill does not publish npm or edit an install root.
183
+ It also refuses to run from the fleet pane that Herdr must restart: an updater
184
+ that kills itself cannot verify the result. With skill commands enabled, invoke
185
+ it directly with:
181
186
 
182
187
  ```text
183
188
  /skill:conductor-update
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "omp-conductor",
3
- "version": "0.3.16",
3
+ "version": "0.3.17",
4
4
  "type": "module",
5
5
  "license": "MIT",
6
6
  "description": "A 24/7 dispatcher that takes ready GitHub issues to green, mergeable PRs using omp coding sessions, with tiered escalation first to an orchestrator session and then to a human.",
package/skills/conductor-update/SKILL.md CHANGED
@@ -1,157 +1,179 @@
1
1
  ---
2
2
  name: conductor-update
3
- description: Safely update an installed omp-conductor fleet as one maintenance operation across both separately installed halves: the npm omp plugin and the GitHub herdr-conductor plugin. Use when the user asks to update, upgrade, refresh, reinstall, or deploy a newly published conductor version, or when installed conductor code is behind npm/main. Quiesces work, preserves exact pane identity, performs a whole-version swap, restarts through the supported lifecycle, re-arms through Telegram proof, and verifies the live fleet.
3
+ description: Update an installed conductor fleet through one operator request. Use when the user asks to update, upgrade, refresh, reinstall, or deploy conductor. Pins one npm release across the Bun-global CLI, omp plugin, and Herdr recovery plugin; converts a local Herdr link when needed; pauses claims, reloads processes, verifies the fleet, and restores the operator's prior pause state.
4
4
  ---
5
5
 
6
6
  # Update a conductor fleet
7
7
 
8
- Treat an update as one operation across two independently installed plugins:
8
+ The operator interface is one request: **“update conductor.”** Do not hand them
9
+ the implementation as a checklist unless execution is blocked.
9
10
 
10
- - `omp-conductor` comes from npm and owns dispatch, CLI, status, and heartbeat.
11
- - `herdr-conductor` comes from `TerrifiedBug/conductor/herdr` and owns exact-pane recovery.
11
+ One release has three installed surfaces:
12
12
 
13
- Updating only one half can leave a version that starts but cannot recover correctly.
14
- This skill updates an installed fleet. It does **not** publish npm, merge a PR, tag a
15
- release, or edit files in an install directory.
13
+ 1. Bun-global `omp-conductor`: CLI and systemd daemon source.
14
+ 2. omp npm plugin `omp-conductor`: slash command and heartbeat loaded by sessions.
15
+ 3. Herdr plugin `herdr-conductor`: exact-pane recovery, pinned to the npm
16
+ release's `gitHead`.
17
+
18
+ This skill performs the whole swap. It does not publish npm, merge, tag, edit an
19
+ install root, or update unrelated Bun packages.
16
20
 
17
21
  ## Safety boundary
18
22
 
19
- Run this procedure from an operator shell or maintenance omp session that is not
20
- hosted by the target `herdr-fleet.service`. If the current working directory
21
- contains `.conductor-tick.json`, or stopping that unit would kill the session
22
- executing this skill, stop and move the update to an external maintenance
23
- session. A self-terminating updater cannot produce trustworthy verification.
23
+ Run from an operator shell or maintenance omp session that is not hosted by the
24
+ target `herdr-fleet.service`. If restarting that unit would kill this updater,
25
+ move to an external session first. Never print npm, Telegram, or bot credentials.
26
+
27
+ The normal update is:
28
+
29
+ ```text
30
+ inspect → pause claims → drain → pinned installs → reload → verify → restore pause state
31
+ ```
24
32
 
25
- Use the configured target host. Do not assume a hostname, state directory, Herdr
26
- session name, project name, or systemd availability. Read them from the existing
27
- installation and `omp-conductor status`. Never print bot tokens, npm tokens, or
28
- authentication files.
33
+ Ticks stay in their existing armed or disarmed state. Do not use `hold`,
34
+ `halt --pane`, `disarm`, `arm`, recovery pins, `pkill`, or manual install-root
35
+ edits for a healthy update.
29
36
 
30
- ## 1. Establish the desired version
37
+ ## 1. Resolve one release and inspect every surface
31
38
 
32
- Read, do not guess:
39
+ Use the registry latest unless the operator names another published version:
33
40
 
34
41
  ```bash
35
- omp-conductor --version
36
42
  version=$(npm view omp-conductor version)
37
43
  gitHead=$(npm view "omp-conductor@$version" gitHead)
38
44
  npm view "omp-conductor@$version" version gitHead --json
39
- omp plugin list --json
40
- omp-conductor status [--project NAME]
41
45
  ```
42
46
 
43
- Use the registry latest as `$version` unless the user explicitly names another
44
- published version, then query that exact version as shown. Record its `gitHead`
45
- and require a full commit SHA: the npm spec and Herdr ref below are both pinned,
46
- so a concurrent release cannot mix two versions. If npm has no newer version, do
47
- not churn the fleet: report that it is current. Confirm that `herdr` and
48
- `systemctl` are present before taking anything down when status says Herdr
49
- manages the pane.
50
-
51
- ## 2. Quiesce without losing work
47
+ Require `$version` to be nonempty and `$gitHead` to be a full commit SHA before
48
+ changing state.
52
49
 
53
- First stop new claims and heartbeat prompts:
50
+ Inspect, without mutating:
54
51
 
55
52
  ```bash
56
- omp-conductor hold [--project NAME]
53
+ omp-conductor --version
54
+ omp plugin list --json
55
+ herdr --session "$session" plugin list
56
+ omp-conductor status [--project NAME]
57
57
  ```
58
58
 
59
- Read status until `active runs (none)`. Do not kill workers to make the update
60
- faster. If a run does not drain, report the run and stop; ordinary update authority
61
- does not include discarding work.
59
+ Honor the installation's existing Herdr session and `HERDR_CONFIG_PATH`; discover
60
+ them from the running unit/config rather than assuming `fleet` or a path.
62
61
 
63
- Then stop the exact conductor pane and dispatch daemon through the supported,
64
- fail-closed path:
62
+ Record:
65
63
 
66
- ```bash
67
- omp-conductor halt --pane [--project NAME]
68
- ```
64
+ - Bun-global CLI version;
65
+ - omp plugin version;
66
+ - Herdr plugin source: GitHub revision, `local:<path>`, or missing;
67
+ - initial dispatch state: running, paused, or stopped;
68
+ - initial ticks state, which this update must not change;
69
+ - active runs and layered health.
70
+
71
+ Report “already current” only when **all** of these are true:
72
+
73
+ - Bun-global CLI version equals `$version`;
74
+ - omp plugin version equals `$version`;
75
+ - Herdr source revision equals `$gitHead`;
76
+ - layered status is healthy for the fleet's configured topology.
69
77
 
70
- This writes the recovery pin before stopping the exact configured Herdr agent. If
71
- identity is invalid, missing, or ambiguous, it refuses rather than killing a guess.
72
- Do not bypass that refusal with `pkill`.
78
+ A current npm version with a linked, missing, or stale Herdr plugin is a partial
79
+ update, not a no-op. If all versions match but status is unhealthy, diagnose the
80
+ reported layer; never call an unhealthy fleet current.
73
81
 
74
- When `herdr-fleet.service` is installed, stop it before replacing either plugin:
82
+ ## 2. Pause claims and drain
83
+
84
+ If dispatch was running:
75
85
 
76
86
  ```bash
77
- systemctl stop herdr-fleet.service
87
+ omp-conductor pause [--project NAME]
78
88
  ```
79
89
 
80
- At this point the daemon is stopped, the pane is stopped, and recovery remains
81
- pinned. If any of those statements is false, do not modify the install.
90
+ If it was already paused, preserve that state. If it was stopped, do not start it
91
+ later merely because packages were updated.
92
+
93
+ Wait for `active runs (none)`. Never kill workers for an update. If a run does not
94
+ drain, stop and report it; leave any pause this skill added in place.
82
95
 
83
- ## 3. Replace both installed halves
96
+ ## 3. Replace all three surfaces with the pinned release
84
97
 
85
- Refresh the exact npm version using omp's package installer:
98
+ Use exact versions. A broad `bun update` is prohibited.
86
99
 
87
100
  ```bash
101
+ bun add -g "omp-conductor@$version"
88
102
  omp plugin install "omp-conductor@$version"
89
103
  ```
90
104
 
91
- Then refresh the Herdr managed checkout from the exact npm release commit. Herdr
92
- requires the GitHub source before its options:
105
+ For Herdr, inspect the source found in step 1:
106
+
107
+ - `local:<path>`: unlink the plugin id first;
108
+ - GitHub-managed or missing: do not unlink.
109
+
110
+ Then install the exact npm release commit. Herdr requires the source argument
111
+ before its options:
93
112
 
94
113
  ```bash
114
+ herdr plugin unlink herdr-conductor # only when step 1 reported local:<path>
95
115
  herdr plugin install TerrifiedBug/conductor/herdr --ref "$gitHead" --yes
96
116
  ```
97
117
 
98
- Do not use `git pull`, `scp`, a linked checkout, or edits under either plugin's
99
- install root. This is a whole-version swap. If either install fails, leave the
100
- fleet stopped and recovery pinned; report the failed command and do not continue
101
- with a mixed live version.
118
+ If any install fails, do not reload processes and do not restore dispatch.
119
+ Leave the fleet paused, report the failed surface, and give the one retry command.
120
+ The still-running processes keep their already-loaded code until a successful
121
+ reload.
102
122
 
103
- ## 4. Start through the new lifecycle
123
+ ## 4. Reload the installed code
104
124
 
105
- Run the newly installed CLI:
125
+ When Herdr is systemd-managed, restart its fleet unit. This reloads the managed
126
+ recovery plugin and causes exact-identity recovery to resume the orchestrator pane
127
+ with the new omp extension:
106
128
 
107
129
  ```bash
108
- omp-conductor --version
109
- omp-conductor start [--project NAME]
130
+ systemctl restart herdr-fleet.service
110
131
  ```
111
132
 
112
- `start` clears the recovery pin, starts the optional `herdr-fleet.service`, and
113
- starts the dispatch daemon after a real `/healthz` check. Herdr then recovers the
114
- exact orchestrator pane and requests an immediate tick; the verification below,
115
- not the `start` command alone, proves that recovery completed.
133
+ Wait until Herdr reports its unit active and the exact configured agent live.
116
134
 
117
- Wait until `omp-conductor status` reports the exact pane `live`; `start` returning
118
- only proves the service and dispatch daemon. `hold` deliberately disarmed ticks,
119
- so restore unattended operation through the existing Telegram proof:
135
+ If the dispatch daemon was running or paused initially, restart it so its process
136
+ and source-integrity baseline use the new Bun-global package:
120
137
 
121
138
  ```bash
122
- omp-conductor arm [--project NAME]
139
+ omp-conductor restart [--project NAME]
123
140
  ```
124
141
 
125
- Wait for the operator's inbound Telegram reply. Never create the arm marker by
126
- hand and never treat an outbound challenge as proof.
142
+ Do not substitute `start` when the daemon was initially stopped.
127
143
 
128
- ## 5. Verify the live result
144
+ ## 5. Verify before restoring claims
129
145
 
130
- Require all of the following before reporting success:
146
+ Check every surface again:
131
147
 
132
148
  ```bash
133
149
  omp-conductor --version
134
- npm view "omp-conductor@$version" version gitHead --json
135
150
  omp plugin list --json
136
- herdr plugin list
151
+ herdr --session "$session" plugin list
137
152
  omp-conductor status [--project NAME]
138
153
  systemctl is-active herdr-fleet.service
139
154
  ```
140
155
 
141
- - installed version and the npm package entry both equal `$version`;
142
- - the Herdr plugin source revision equals the npm release `gitHead`;
143
- - `dispatch` is `running`;
144
- - `ticks` is `armed` and a next tick is shown;
145
- - `pane` is `live` for the exact configured Herdr agent;
146
- - `recovery` is `clear`;
147
- - `herdr` is `active` when managed;
148
- - Telegram is `ok` (or its exact supported degraded state is reported);
149
- - daemon `/healthz` is `ok`;
150
- - no unexpected active runs appeared during maintenance.
151
-
152
- Run a second status check after the immediate recovery tick is consumed. A single
153
- healthy snapshot is not proof that recovery and heartbeat scheduling survived the
154
- swap.
155
-
156
- Report the old and new versions, both plugin refreshes, the final layered status,
157
- and any supported degraded state. Do not report success for a partial update.
156
+ Require:
157
+
158
+ - global CLI and omp plugin both equal `$version`;
159
+ - Herdr source equals `TerrifiedBug/conductor` at `$gitHead`;
160
+ - exact pane is live and recovery is clear;
161
+ - Herdr and daemon health are OK when managed;
162
+ - ticks equal their initial state;
163
+ - active runs remain empty;
164
+ - dispatch remains paused if this skill paused it.
165
+
166
+ Run status a second time after recovery settles. Any failed check leaves dispatch
167
+ paused and is reported as a partial update.
168
+
169
+ Only if dispatch was initially running and every check passed:
170
+
171
+ ```bash
172
+ omp-conductor resume [--project NAME]
173
+ ```
174
+
175
+ Verify `dispatch running` once more. If dispatch was initially paused or stopped,
176
+ preserve that state and report it.
177
+
178
+ Finish with one compact result: old → new version, all three installed surfaces,
179
+ final layered status, and whether the original dispatch state was restored.