@indigoai-us/hq-cli 5.339.0 → 5.340.1-beta.0

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## [Unreleased]
 
+## [5.340.1-beta.0] — 2026-10-03
+- Let `hq sync now` skip unchanged server-owned cloud placeholders while keeping their warnings visible, so the sync can complete.
+
+## [5.340.0] — 2026-10-03
+- Preserve resolver output when child processes exit before Windows pipe data has drained.
+- Native `hq core dm-bind` on Windows now finds an `hq.exe` on PATH, and no longer accepts an `hq.cmd` shim it cannot launch.
+- Document the flag-gated HQ Anywhere global install and hqd daemon. The runtime flag remains off by default.
+
 ## [5.339.0] — 2026-10-03
 - Reduce cold-start imports for the `checkpoint-stop-gate` and `session-journal` native fast routes.
 

package/README.md

@@ -7,6 +7,11 @@ npm install -g @indigoai-us/hq-cli
 hq --help
 ```
 
+The global HQ runtime installs hooks for supported agent runtimes. When the
+`hq-anywhere-runtime` flag is enabled, the hooks use hqd and a per-user folder
+registry. The flag is off by default. See [HQ Anywhere runtime](docs/anywhere-runtime.md)
+for install and link commands.
+
 ## Deploy comments
 
 List comments left on an app in your current hq-deploy organization. Use the

package/assets/scaffold/core/scripts/resolve-company.sh

@@ -142,16 +142,60 @@ const command = process.argv[1];
 if (!command) process.exit(127);
 const child = spawn(command, process.argv.slice(2), { detached: true, stdio: ["ignore", "pipe", "ignore"] });
 let finished = false;
+let exited = false;
+let exitStatus = 1;
+let flushedAfterExit = false;
+let pendingWrites = 0;
+let stdoutEnded = false;
+let drainTimer;
+const finishWhenReady = () => {
+  if (finished || !exited || pendingWrites !== 0) return;
+  if (!stdoutEnded && !flushedAfterExit) return;
+  finished = true;
+  clearTimeout(timer);
+  clearTimeout(drainTimer);
+  try { process.kill(-child.pid, "SIGTERM"); } catch (_) {}
+  process.exit(exitStatus);
+};
+const forward = (chunk) => {
+  pendingWrites++;
+  process.stdout.write(chunk, () => {
+    pendingWrites--;
+    finishWhenReady();
+  });
+};
 const finish = (status) => {
   if (finished) return;
   finished = true;
   clearTimeout(timer);
+  clearTimeout(drainTimer);
   try { process.kill(-child.pid, "SIGTERM"); } catch (_) {}
   process.exit(status);
 };
-child.stdout.on("data", (chunk) => process.stdout.write(chunk));
+child.stdout.on("data", forward);
+child.stdout.once("end", () => {
+  stdoutEnded = true;
+  finishWhenReady();
+});
 child.once("error", () => finish(127));
-child.once("exit", (code) => finish(typeof code === "number" ? code : 1));
+child.once("exit", (code) => {
+  exited = true;
+  exitStatus = typeof code === "number" ? code : 1;
+  try { process.kill(-child.pid, "SIGTERM"); } catch (_) {}
+  // Normally EOF follows child exit once the pipe has drained. A detached
+  // grandchild can keep the pipe open, so bound that wait and flush buffered
+  // bytes after a short drain window.
+  drainTimer = setTimeout(() => {
+    child.stdout.pause();
+    let chunk;
+    while ((chunk = child.stdout.read()) !== null) forward(chunk);
+    process.stdout.write("", () => {
+      flushedAfterExit = true;
+      finishWhenReady();
+    });
+  }, 250);
+  finishWhenReady();
+});
 const timer = setTimeout(() => finish(124), 2000);
 ' "$@"
 }

package/dist/commands/cloud.js

@@ -1751,6 +1751,7 @@ async function runNowSingle(hqRoot, company, personal, message, onConflict, mode
             hqRoot,
             progressRecorder: trackingProgressRecorder(planLimitTracker, pushProgressCompany),
             skipUnchanged: true,
+            serverOwnedPathPolicy: "skip",
             propagateDeletes: true,
             propagateDeletePolicy: resolveDeletePolicy(),
             ...(onConflict ? { onConflict } : {}),

package/dist/commands/core-dm-bind-native.d.ts

@@ -11,6 +11,8 @@ export type DmBindDeps = {
     home: string;
     now: () => Date;
     fs: typeof fs;
+    /** Defaults to process.platform; tests pass it to exercise the Windows lookup. */
+    platform?: NodeJS.Platform;
     runHq: (args: string[], env: NodeJS.ProcessEnv) => {
         code: number;
         stdout: string;

package/dist/commands/core-dm-bind-native.js

@@ -91,12 +91,20 @@ function hasHqOnPath(d) {
     for (const directory of (d.env.PATH ?? "").split(path.delimiter)) {
         if (!directory)
             continue;
-        try {
-            const stat = d.fs.statSync(path.join(directory, "hq"));
-            if (stat.isFile() && (stat.mode & 0o111) !== 0)
-                return true;
+        // runHq spawns "hq" without a shell. On Windows that resolves only .exe and
+        // .com files, and Windows file modes carry no execute bits, so accept exactly
+        // what the spawn can launch. npm's hq.cmd shim needs a shell and is not
+        // accepted here.
+        const windows = (d.platform ?? process.platform) === "win32";
+        const names = windows ? ["hq.exe", "hq.com"] : ["hq"];
+        for (const name of names) {
+            try {
+                const stat = d.fs.statSync(path.join(directory, name));
+                if (stat.isFile() && (windows || (stat.mode & 0o111) !== 0))
+                    return true;
+            }
+            catch { /* PATH entry is absent */ }
         }
-        catch { /* PATH entry is absent */ }
     }
     return false;
 }

package/docs/anywhere-runtime.md

@@ -0,0 +1,60 @@
+# HQ Anywhere runtime
+
+HQ Anywhere installs global hooks for supported agent runtimes and uses the
+local hqd daemon on macOS and Linux. Windows does not currently start hqd, so
+the daemon-backed routing described here is unavailable there. A per-user
+registry links repositories to HQ companies. The `hq-anywhere-runtime` flag
+controls these features and is off by default.
+
+## Install
+
+Install and start hqd before registering global hooks. The global installer
+checks for the daemon service when choosing the hook target.
+
+```sh
+hq daemon install
+hq daemon status
+hq install --global --runtime claude
+```
+
+`hq install --global` defaults to Claude. Select other supported runtimes
+explicitly with `--runtime codex`, `--runtime chatgpt`, or `--runtime grok`.
+Claude and Codex receive local hook configuration. ChatGPT and Grok print
+connector setup instructions and require the runtime flag to be enabled.
+
+The CLI stores the HQ root at `~/.hq/root` and keeps the folder registry in
+`~/.hq/registry.json`. These files belong to the current host. They are not
+stored in a repository or synced HQ folder.
+
+On Windows, `hq daemon install` reports that hqd cannot start because its
+named-pipe ACL is not supported. Global hook installation may still configure
+local runtime hooks, but it does not provide the hqd routing described below.
+
+When the flag is enabled, the global hook uses hqd for events outside the HQ
+root. Inside the root, the project hook routes through hqd when it is running
+and uses the direct master hook when it is stopped.
+
+## Link a repository
+
+Run `hq link <company>` from a repository to associate it with a company. The
+registry uses the normalized Git remote when one is available. Otherwise, it
+uses the repository's canonical absolute path.
+
+`HQ_REGISTRY_DIR` changes the registry directory, and `HQ_HQD_SOCKET` changes
+the daemon socket path. The managed service does not inherit overrides from
+the shell that ran `hq daemon install`; it persists `PATH` and
+`HQ_DAEMON_DIR`. Keep the defaults for a managed install unless you configure
+both the daemon service and the agent runtime with the same overrides. For a
+systemd user service, add `Environment=HQ_REGISTRY_DIR=...` and
+`Environment=HQ_HQD_SOCKET=...` in `systemctl --user edit hq-daemon.service`,
+then run `systemctl --user daemon-reload` and
+`systemctl --user restart hq-daemon.service`. For launchd, set both keys in the
+`EnvironmentVariables` dictionary in
+`~/Library/LaunchAgents/ai.getindigo.hq-daemon.plist`, then restart the job
+with `launchctl kickstart -k gui/$(id -u)/ai.getindigo.hq-daemon`. Also set
+both variables in the agent runtime environment so hooks and `hq link` use
+the same paths.
+
+The registry does not infer a company when a repository has no matching entry.
+That session uses personal context. The socket protocol and registry format are
+documented in the HQ Anywhere runtime knowledge entry in hq-core.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@indigoai-us/hq-cli",
-  "version": "5.339.0",
+  "version": "5.340.1-beta.0",
   "description": "HQ by Indigo management CLI — modules and cloud sync",
   "main": "dist/index.js",
   "bin": {
@@ -16,6 +16,7 @@
     "assets/lanes-reconcile",
     "assets/lanes-hooks",
     "templates",
+    "docs/anywhere-runtime.md",
     "CHANGELOG.md",
     "README.md",
     "contracts",