@rallycry/conveyor-skills 1.0.0 → 1.0.2
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.
package/package.json
CHANGED
|
@@ -149,6 +149,16 @@ and never silence a failure with a filter, a `.skip`, or a "known flake" note:
|
|
|
149
149
|
either your diff broke it, or the test is broken or environment-dependent and
|
|
150
150
|
you fix the test.
|
|
151
151
|
|
|
152
|
+
**Long gates in a pod: background them the sanctioned way.** Launch a long
|
|
153
|
+
gate with the harness's `run_in_background` Bash option and end the turn — the
|
|
154
|
+
runner tracks the launch, holds pod liveness while a gate process is alive,
|
|
155
|
+
and wakes you when it finishes (or if its completion callback is lost). In a
|
|
156
|
+
repo without Conveyor's `scripts/singleton.sh`, wrap the command in the
|
|
157
|
+
shipped `conveyor-gate` bin — `conveyor-gate <label> -- <cmd…>` — which writes
|
|
158
|
+
the same pid/exit contract under `$CONVEYOR_RUN_DIR/gates/` so the runner can
|
|
159
|
+
see it. Hand-rolled backgrounding (`nohup`, `&`, `disown`) is invisible to the
|
|
160
|
+
runner: the pod can sleep mid-run and nothing will wake you.
|
|
161
|
+
|
|
152
162
|
**A UI-visible change needs visual proof before the PR**, in both environments:
|
|
153
163
|
capture a screenshot (static) or a short recording (interaction) with the host
|
|
154
164
|
repo's own tooling and attach it with `mcp__conveyor__upload_attachment`, then
|
|
@@ -173,7 +173,10 @@ notification is the wake. The `ScheduleWakeup` you still arm is the fallback for
|
|
|
173
173
|
the case where the wait dies silently — use the pacing table's background-gate
|
|
174
174
|
row (1200–1800s), not a second, shorter timer.
|
|
175
175
|
|
|
176
|
-
- Prefer `node_modules/.bin/conveyor-wait`.
|
|
176
|
+
- Prefer `node_modules/.bin/conveyor-wait`. Gate on
|
|
177
|
+
`[ -x node_modules/.bin/conveyor-wait ]`, not on the path existing: in a
|
|
178
|
+
checkout that has not been built the bin is a symlink into an unbuilt
|
|
179
|
+
`dist/`, so it looks present and fails to run. When that test is false, use
|
|
177
180
|
`npx -y -p @rallycry/conveyor-mcp@latest conveyor-wait`. The `-p` form
|
|
178
181
|
matters: inside the conveyor monorepo a bare
|
|
179
182
|
`npx @rallycry/conveyor-mcp` misresolves.
|