@indigoai-us/hq-cli 5.108.2 → 5.108.4

package/dist/utils/qmd-workdir-missing-error.js

@@ -0,0 +1,78 @@
+// src/utils/qmd-workdir-missing-error.ts
+//
+// Classify a qmd spawn failure caused by a MISSING WORKING DIRECTORY — the
+// directory the qmd child was told to run in (`cwd`, always the resolved hq
+// root at the qmd call sites) does not exist — rather than an hq-cli code
+// defect or a genuinely missing qmd. This is the caller's LOCAL filesystem (a
+// deleted tree, a `--hq-root` pointing at a directory that is not there), not a
+// bug HQ can fix in code, so the CLI surfaces an actionable remedy and SKIPS
+// Sentry capture. Sibling of qmd-store-missing-error.ts (HQ-CLI-16, a missing
+// STORE directory) and qmd-store-unopenable-error.ts (HQ-CLI-18): a failure
+// that is NOT an hq-cli defect is printed with an actionable message and never
+// filed as a crash.
+//
+// HQ-CLI-1A (Sentry indigo-d0/hq-cli 7705642434): `hq index status --hq-root
+// /home/ec2-user/hq` spawned the bundled qmd as `<node interpreter> <qmd
+// launcher>`, and spawnSync failed with `spawnSync /usr/bin/node ENOENT`. On
+// Linux, spawnSync reports ENOENT with `path`/`syscall` set to the COMMAND both
+// when the command is missing AND when chdir into `cwd` fails — two distinct
+// causes with byte-identical text. finishRunQmd was handed only the qmd
+// launcher path, so it blamed a THIRD path Node never faulted
+// (`QmdBinaryMissingError: Unable to execute qmd at …/@tobilu/qmd/bin/qmd`) with
+// a remedy (`Install @tobilu/qmd`) that cannot fix either real cause, and — with
+// no boundary branch for it — the misattributed error was captured as a crash.
+// finishRunQmd now disambiguates at the failure site: when the ENOENT is a
+// missing working directory it raises the typed carrier this module classifies.
+//
+// Classification is STRUCTURAL — the typed carrier's own `name` plus its
+// hq-populated `workdir` field, NEVER a text match on qmd's output or the
+// caller's argv — so a search query or a document body can never trip it, and
+// the class need not be imported here (avoiding a cycle with the module that
+// defines it). Reading `name`/`workdir` off the error object also lets the
+// top-level boundary, which reconstructs typed carriers structurally, branch on
+// it the same way it does the sibling qmd errors.
+/**
+ * True when `err` is a qmd working-directory-missing failure: it carries the
+ * QmdWorkdirMissingError name and an hq-populated `workdir`. Accepts either the
+ * thrown error or a bare `{ name, workdir }` probe object. A true result means
+ * the caller should print the classified remedy, exit non-zero, and SKIP Sentry
+ * capture.
+ */
+export function isQmdWorkdirMissingError(err) {
+    if (err === null || typeof err !== "object")
+        return false;
+    const record = err;
+    return (record.name === "QmdWorkdirMissingError" &&
+        typeof record.workdir === "string" &&
+        record.workdir.length > 0);
+}
+/**
+ * The actionable remedy, naming the working directory that does not exist. The
+ * directory is an hq-DERIVED value — the resolved `cwd` (the hq root) the qmd
+ * child was handed — never caller argv/query or upstream free text, so the line
+ * stays input-free. Deliberately does NOT suggest reinstalling qmd (the reported
+ * misattribution's dead-end remedy) or `hq index sync` (reconciliation runs the
+ * same spawn and would hit the identical failure, a dead-end loop): the only fix
+ * is to make the working directory exist.
+ */
+function remedyMessage(workdir) {
+    return (`hq's working directory (${workdir}) does not exist, so its local search index ` +
+        "could not run there. This is your machine's filesystem, not an hq bug: " +
+        "re-create that directory, or re-run with --hq-root pointing at a directory " +
+        "that exists.");
+}
+/**
+ * If `err` is a qmd working-directory-missing failure, return the actionable
+ * remedy; otherwise return `null`. Mirrors qmdStoreMissingMessage /
+ * qmdStoreUnopenableMessage so the top-level handler can branch on it the same
+ * way: a non-null result means print-and-skip-Sentry, null means "handle as
+ * usual". The working directory is read STRUCTURALLY from the error's own
+ * hq-populated `workdir` field, NEVER from qmd's output.
+ */
+export function qmdWorkdirMissingMessage(err) {
+    if (!isQmdWorkdirMissingError(err))
+        return null;
+    const record = err;
+    return remedyMessage(record.workdir);
+}
+//# sourceMappingURL=qmd-workdir-missing-error.js.map

package/dist/utils/sentry-fingerprint.js

@@ -86,6 +86,11 @@ const KNOWN_ERROR_NAMES = new Set([
     "QmdStoreUnopenableError",
     "QmdQueryDocumentError",
     "QmdModelDownloadError",
+    // Shares the `Qmd` prefix the qmd branch keys on. The boundary now SUPPRESSES
+    // capture for this class, so it should never reach a capture route — allow-
+    // listed defensively so a future capture path cannot mint an unbounded group
+    // (HQ-CLI-1A).
+    "QmdWorkdirMissingError",
 ]);
 /** Fixed bucket for any error name outside the closed allowlist. */
 const FALLBACK_ERROR_NAME = "other";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@indigoai-us/hq-cli",
-  "version": "5.108.2",
+  "version": "5.108.4",
   "description": "HQ by Indigo management CLI — modules and cloud sync",
   "main": "dist/index.js",
   "bin": {