@indigoai-us/hq-cli 5.119.6 → 5.119.7

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/CHANGELOG.md CHANGED
@@ -2,6 +2,16 @@
2
2
 
3
3
  ## [Unreleased]
4
4
 
5
+ ## [5.119.7] — 2026-09-17
6
+
7
+ ### Fixed
8
+
9
+ - When the kit cannot install its `@reboot` entry because the host has no
10
+ `crontab` at all, the install now says so and names the package to install,
11
+ instead of reporting a raw ENOENT the operator cannot act on. A minimal
12
+ container image routinely ships without cron; the Muse pilot hit this the
13
+ first time the reboot entry was attempted.
14
+
5
15
  ## [5.119.6] — 2026-09-17
6
16
 
7
17
  ### Fixed
@@ -80,19 +80,5 @@ export interface RebootCronResult {
80
80
  }
81
81
  /** Drop any previously managed block, leaving every other entry untouched. */
82
82
  export declare function stripManagedCron(existing: string): string;
83
- /**
84
- * Install the @reboot entry that brings the fallback supervisor back after a
85
- * restart.
86
- *
87
- * Printing the line and trusting it to be pasted is what the installer used to
88
- * do, and it is how the Muse pilot lost its messages: the host rebooted, the
89
- * supervisor died with it, nothing restarted it, and the bot went quiet while
90
- * every surface still reported healthy. A supervisor that does not survive a
91
- * reboot is not a supervisor, so the entry is now written for real.
92
- *
93
- * Failure is NOT fatal — a host with no crontab is still a working kit until
94
- * it restarts — but it is reported, so the caller can tell the operator the
95
- * one thing they must then do by hand.
96
- */
97
83
  export declare function ensureRebootCrontab(paths: Pick<AgentKitPaths, "agentDir" | "logsDir">, host: ServiceHostPaths, run?: CronRunner): RebootCronResult;
98
84
  //# sourceMappingURL=fallback.d.ts.map
@@ -161,6 +161,10 @@ export function stripManagedCron(existing) {
161
161
  * it restarts — but it is reported, so the caller can tell the operator the
162
162
  * one thing they must then do by hand.
163
163
  */
164
+ /** No cron on the host: spawn failed outright, or the shell could not find it. */
165
+ function isMissingCrontab(r) {
166
+ return r.status === 127 || /\bENOENT\b|command not found|not found/i.test(r.stderr);
167
+ }
164
168
  export function ensureRebootCrontab(paths, host, run) {
165
169
  const exec = run ??
166
170
  ((args, input) => {
@@ -170,6 +174,17 @@ export function ensureRebootCrontab(paths, host, run) {
170
174
  return { status: r.status ?? 1, stdout: r.stdout ?? "", stderr: r.stderr ?? "" };
171
175
  });
172
176
  const listed = exec(["-l"]);
177
+ // A minimal host image often ships without cron at all, which is not an
178
+ // error the operator can act on unless it is named. Observed on the Muse
179
+ // pilot: the reboot entry could not be written because the cron package was
180
+ // simply not installed, and the raw ENOENT did not say so.
181
+ if (isMissingCrontab(listed)) {
182
+ return {
183
+ installed: false,
184
+ reason: "the `crontab` command is not installed on this host (install your distribution's cron package, " +
185
+ "for example `apt-get install -y cron` or `apk add busybox-cron`), then run `hq agent kit install` again",
186
+ };
187
+ }
173
188
  // An empty crontab exits non-zero with "no crontab for <user>"; that is not
174
189
  // a failure, it just means there is nothing to preserve. Anything else is.
175
190
  const noCrontabYet = listed.status !== 0 && /no crontab for/i.test(listed.stderr);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@indigoai-us/hq-cli",
3
- "version": "5.119.6",
3
+ "version": "5.119.7",
4
4
  "description": "HQ by Indigo management CLI \u2014 modules and cloud sync",
5
5
  "main": "dist/index.js",
6
6
  "bin": {