@drisp/cli 0.6.8 → 0.6.10

package/README.md

@@ -215,6 +215,7 @@ Connect a machine from **Settings → Runners** in the web console. It shows a o
 drisp runner connect K7QF-M2PX --hub https://hub.example.com   # join the Team and start the Runner as a background service
 drisp runner connect --hub https://hub.example.com             # or print a code to approve in the web console
 drisp runner status                                            # the saved identity, without its credential, and the service's state
+drisp runner restart                                           # refresh the service definition and restart it, e.g. after npm install -g @drisp/cli@latest
 drisp runner disconnect [<team>]                               # leave a Team: stop its Runs there and delete that Team's credential
 drisp runner recover <run-id> confirmed-stopped                # record a failed outcome after an uncertain crash
 ```
@@ -225,7 +226,7 @@ A machine is one Runner per Team. Connect writes that Team's Runner identity and
 
 Any member of the Team can connect their own machine. It joins as a **Personal** Runner named after its hostname, which runs only its owner's Runs; a Team admin approving a printed code may make it a **Team** Runner instead.
 
-Connect then installs and starts a user-level service, so the Runner keeps running when the terminal closes and starts again at login: a LaunchAgent `com.drisp.runner.<installationId>` on macOS (log in `~/Library/Logs/drisp/runner-<installationId>.log`), a systemd user unit `drisp-runner-<installationId>.service` on Linux (log in `journalctl --user -u drisp-runner-<installationId>`). `drisp runner status` prints the service's name. The service runs this drisp installation with the saved identity and the `PATH` you connected from, so it finds the same harnesses; there is no unit file to write. Each installation (a `DRISP_RUNNER_CONFIG` identity file is a separate one) gets its own service, so connecting one never stops another. On a Linux server, `loginctl enable-linger` keeps it running while you are logged out. Running Connect again where the identity file already exists is refused before the code is spent, and leaves the service as it is. So if the service cannot be installed or started, Connect exits with an error but keeps the identity: run `drisp runner` to run the Runner in the foreground. On macOS, a LaunchAgent that was installed but would not start still starts at your next login.
+Connect then installs and starts a user-level service, so the Runner keeps running when the terminal closes and starts again at login: a LaunchAgent `com.drisp.runner.<installationId>` on macOS (log in `~/Library/Logs/drisp/runner-<installationId>.log`), a systemd user unit `drisp-runner-<installationId>.service` on Linux (log in `journalctl --user -u drisp-runner-<installationId>`). `drisp runner status` prints the service's name. `drisp runner restart` rewrites the service definition for the CLI installed now (a new Node version or global prefix) and restarts it (on Linux it also turns start-at-login back on, with `systemctl --user enable`); it never installs a service, and like any Runner restart it fails a Run in progress ([ADR-0021](docs/adr/0021-runner-boot-closes-orphaned-runs.md)), so run it when no Run is executing. The service runs this drisp installation with the saved identity and the `PATH` you connected from, so it finds the same harnesses; there is no unit file to write. Each installation (a `DRISP_RUNNER_CONFIG` identity file is a separate one) gets its own service, so connecting one never stops another. On a Linux server, `loginctl enable-linger` keeps it running while you are logged out. Running Connect again where the identity file already exists is refused before the code is spent, and leaves the service as it is. So if the service cannot be installed or started, Connect exits with an error but keeps the identity: run `drisp runner` to run the Runner in the foreground. On macOS, a LaunchAgent that was installed but would not start still starts at your next login.
 
 In a container or CI, or on a platform without launchd or systemd (where Connect says so and does this anyway), keep the Runner in the foreground instead:
 

package/dist/{WorkflowInstallWizard-TQ4SF5KB.js → WorkflowInstallWizard-NZFBSBLY.js}

@@ -8,7 +8,7 @@ import {
   installWorkflowPlugins,
   resolveWorkflow,
   writeGlobalConfig
-} from "./chunk-CIPO2P2Q.js";
+} from "./chunk-YUVMVYUF.js";
 import "./chunk-G3PMV62Z.js";
 
 // src/setup/steps/WorkflowInstallWizard.tsx
@@ -93,4 +93,4 @@ function WorkflowInstallWizard({ source, onDone }) {
 export {
   WorkflowInstallWizard as default
 };
-//# sourceMappingURL=WorkflowInstallWizard-TQ4SF5KB.js.map
+//# sourceMappingURL=WorkflowInstallWizard-NZFBSBLY.js.map