@indigoai-us/hq-cli 5.109.4 → 5.109.6

package/CHANGELOG.md

@@ -2,6 +2,35 @@
 
 ## [Unreleased]
 
+## [5.109.6] — 2026-09-10
+
+### Fixed
+
+- A torn hq install no longer files an unactionable crash when a bundled
+  third-party dependency of a dependency is missing (HQ-CLI-1Q). `hq packs list`
+  loaded the mesh presence client, whose `import mqtt` chain reached
+  mqtt-packet's `parser.js` requiring `bl` — mqtt-packet's OWN declared
+  transitive dependency — which a partial Windows global install had left
+  unwritten. The in-process incomplete-install classifier shipped in 5.108.14
+  recognised only a RELATIVE missing specifier for the CJS shape, so this BARE
+  specifier fell through to a bare Sentry crash plus an `hq:` line the operator
+  could not act on. The classifier now also recognises a bare miss from UNDER
+  the running install's own `node_modules/`, but ONLY when the missing specifier
+  names a WHOLE package (not a subpath like `bl/lib/x`, which can mean the
+  package is present and only that file gone to a version mismatch) AND the
+  REQUIRING third-party package's own manifest declares it in its REQUIRED
+  `dependencies` (`optionalDependencies` are excluded, being not guaranteed
+  installed) — a correct install always writes such a
+  dependency, so its absence beside a present requirer can only be a torn
+  install, never an hq-cli manifest defect. Those are printed with the same
+  input-free reinstall remedy and skipped, at the top-level boundary and in the
+  shared `beforeSend`. A bare miss the requirer does NOT declare (a possible
+  undeclared or peer-only dependency) stays reported, now enriched on every
+  capture route with a bounded `incomplete_install` context naming both packages
+  so the next occurrence is attributable instead of bare.
+
+## [5.109.5] — 2026-09-10
+
 ## [5.109.4] — 2026-09-09
 
 ### Fixed
@@ -342,12 +371,13 @@
   `npm i -g @indigoai-us/hq-cli` / `pnpm add -g @indigoai-us/hq-cli`) while
   skipping Sentry capture, the same disposition established for the qmd child in
   HQ-CLI-Y. An hq-cli packaging fault stays reportable: a miss under the
-  package's own `dist/` or `assets/`, a bare-specifier miss (a possible
-  undeclared dependency), and an esm-loader ENOENT whose path did not survive
-  delivery are NOT suppressed — the last is captured WITH a bounded
-  `incomplete_install` context so the next occurrence is attributable. The drop
-  is wired both at the top-level boundary and in the shared `beforeSend`, so it
-  covers every capture route.
+  package's own `dist/` or `assets/`, a bare-specifier miss (then kept loud as a
+  possible undeclared dependency — refined for a dependency the requiring package
+  actually declares in HQ-CLI-1Q, see Unreleased), and an esm-loader ENOENT whose
+  path did not survive delivery are NOT suppressed — the last is captured WITH a
+  bounded `incomplete_install` context so the next occurrence is attributable.
+  The drop is wired both at the top-level boundary and in the shared
+  `beforeSend`, so it covers every capture route.
 
 ## [5.108.13] — 2026-09-06
 

package/dist/main.js

@@ -563,21 +563,24 @@ export async function handleTopLevelError(err, deps = defaultTopLevelErrorDepend
         // An IN-PROCESS module-load failure that means hq-cli's OWN installed
         // package tree is incomplete at load time — a partial/interrupted global
         // install left a bundled file unwritten (HQ-CLI-1N, a CJS relative-sibling
-        // MODULE_NOT_FOUND), or a concurrent global install rewrote the running
-        // tree so an ESM module present at resolve was gone at read (HQ-CLI-1M, an
-        // esm-loader ENOENT). Both carry no hq-cli frames and reached the final
-        // else, filing a bare crash and an unactionable line. An incomplete
-        // install is the caller's machine, the disposition HQ-CLI-Y already
-        // established for the qmd CHILD — print the input-free reinstall remedy and
-        // skip capture. Placed with the environmental family (after the typed qmd
-        // carriers and the hq state-write carrier, before environmentalFsErrorMessage):
-        // the signatures are disjoint — ENVIRONMENTAL_FS_CODES is only
-        // ENOSPC/EDQUOT/EROFS (never ENOENT/MODULE_NOT_FOUND), no qmd carrier sets
-        // requireStack or an esm-loader frame, and the classified file must sit
-        // under <packageRoot>/node_modules — so ordering changes nothing that
-        // exists. The UNATTRIBUTABLE shape (an esm-loader ENOENT whose path did not
-        // survive) is deliberately NOT suppressed; it is captured WITH bounded
-        // context on the generic path below.
+        // MODULE_NOT_FOUND; HQ-CLI-1Q, a CJS BARE-specifier MODULE_NOT_FOUND for a
+        // dependency the requiring third-party package's own manifest declares), or
+        // a concurrent global install rewrote the running tree so an ESM module
+        // present at resolve was gone at read (HQ-CLI-1M, an esm-loader ENOENT).
+        // All carry no hq-cli frames and reached the final else, filing a bare
+        // crash and an unactionable line. An incomplete install is the caller's
+        // machine, the disposition HQ-CLI-Y already established for the qmd CHILD —
+        // print the input-free reinstall remedy and skip capture. Placed with the
+        // environmental family (after the typed qmd carriers and the hq state-write
+        // carrier, before environmentalFsErrorMessage): the signatures are disjoint
+        // — ENVIRONMENTAL_FS_CODES is only ENOSPC/EDQUOT/EROFS (never
+        // ENOENT/MODULE_NOT_FOUND), no qmd carrier sets requireStack or an
+        // esm-loader frame, and the classified file must sit under
+        // <packageRoot>/node_modules — so ordering changes nothing that exists. The
+        // UNATTRIBUTABLE shapes are deliberately NOT suppressed and are captured
+        // WITH bounded context on the generic path below: an esm-loader ENOENT
+        // whose path did not survive, and a bare miss the requirer does NOT declare
+        // (a possible undeclared/peer dependency, now named in the context).
         const incompleteInstallMsg = qmdMsg || collectionMsg || terminatedMsg || llmDisabledMsg || moduleMissingMsg || storeMissingMsg || storeUnopenableMsg || queryDocumentMsg || modelDownloadMsg || workdirMissingMsg || stateWriteMsg
             ? null
             : incompleteInstallMessage(err);

package/dist/sentry.js

@@ -6,7 +6,7 @@ import { CLI_VERSION } from "./cli-version.js";
 import { getCachedSentryUser } from "./utils/sentry-identity.js";
 import { isEpipe } from "./utils/epipe.js";
 import { environmentalFsErrorMessage } from "./utils/environmental-error.js";
-import { incompleteInstallMessage } from "./utils/incomplete-install-error.js";
+import { incompleteInstallCaptureContext, incompleteInstallMessage, } from "./utils/incomplete-install-error.js";
 import { sentryFingerprintFor } from "./utils/sentry-fingerprint.js";
 /**
  * Drop broken-pipe (EPIPE) crashes before scrubbing/send. A closed downstream
@@ -35,17 +35,33 @@ export function epipeAwareBeforeSend(event, hint) {
     // Path-independent belt for an IN-PROCESS incomplete-install module-load
     // failure — hq-cli's own globally installed tree is not intact at load time
     // (HQ-CLI-1N, a CJS relative-sibling MODULE_NOT_FOUND under its bundled
-    // node_modules; HQ-CLI-1M, an esm-loader ENOENT for a file present at resolve
-    // and gone at read). handleTopLevelError already prints the reinstall remedy
-    // for the top-level route; dropping the event here suppresses the fatal
-    // regardless of route — the unhandled-rejection boundary, the command-level
-    // captureException sites, and bin/hq-auth-refresh — mirroring the EPIPE and
-    // environmental-fs drops above. The classifier reads only structured fields
-    // and the failing file must sit under the running install's node_modules, so
-    // an hq-cli packaging fault (a dist/ miss, a bare-specifier miss) and the
+    // node_modules; HQ-CLI-1Q, a CJS BARE-specifier MODULE_NOT_FOUND the requiring
+    // third-party package's own manifest declares; HQ-CLI-1M, an esm-loader ENOENT
+    // for a file present at resolve and gone at read). handleTopLevelError already
+    // prints the reinstall remedy for the top-level route; dropping the event here
+    // suppresses the fatal regardless of route — the unhandled-rejection boundary,
+    // the command-level captureException sites, and bin/hq-auth-refresh —
+    // mirroring the EPIPE and environmental-fs drops above. The classifier reads
+    // only structured fields (plus, for the bare shape, the requiring package's
+    // own manifest) and the failing file must sit under the running install's
+    // node_modules, so an hq-cli packaging fault (a dist/ miss, or a bare miss the
+    // requirer does NOT declare — a possible undeclared/peer dependency) and the
     // path-less unattributable shape are NOT dropped here and stay captured.
     if (incompleteInstallMessage(hint?.originalException))
         return null;
+    // An incomplete-install shape that is NOT suppressed (a bare miss the requirer
+    // does not declare, or a path-less esm-loader ENOENT) should still arrive
+    // ATTRIBUTABLE on every capture route, not only the top-level boundary:
+    // handleTopLevelError in main.ts is the ONLY caller of
+    // incompleteInstallCaptureContext, so events reaching this hook directly — the
+    // unhandled-rejection integration, the command-level captureException sites,
+    // and bin/hq-auth-refresh — would otherwise survive bare. Merge the bounded
+    // context here too. Idempotent: main.ts attaches the same block on its route,
+    // and an already-present context wins the spread.
+    const installContext = incompleteInstallCaptureContext(hint?.originalException);
+    if (installContext) {
+        event.contexts = { ...installContext, ...event.contexts };
+    }
     // Group an event that survives to send by a BOUNDED machine discriminator so
     // unrelated gateway/HTTP failures stop colliding into one fungible issue
     // (HQ-CLI collision, Sentry 7642756130). Placed here — path-independent,

package/dist/utils/incomplete-install-error.d.ts

@@ -21,9 +21,9 @@ export type PackageRootResolver = () => string | null;
  * means "handle as usual (capture to Sentry)". Never throws — a resolver that
  * fails yields null.
  */
-export declare function incompleteInstallMessage(err: unknown, resolvePackageRoot?: PackageRootResolver): string | null;
-/** Bounded, scrubber-safe diagnostics for an unattributable esm-loader ENOENT. */
-export type IncompleteInstallDiagnostics = {
+export declare function incompleteInstallMessage(err: unknown, resolvePackageRoot?: PackageRootResolver, fileSystem?: Pick<typeof fs, "readFileSync">): string | null;
+/** Bounded, scrubber-safe diagnostics for an unattributable esm-loader ENOENT (HQ-CLI-1M). */
+export type IncompleteInstallEsmDiagnostics = {
     packageRoot: string;
     packageJsonExists: boolean;
     nodeModulesExists: boolean;
@@ -31,20 +31,42 @@ export type IncompleteInstallDiagnostics = {
     code: string;
 };
 /**
- * When an esm-loader ENOENT reaches the capture path WITHOUT being suppressed —
- * the exact shape the delivered HQ-CLI-1M payload arrived in, where neither the
- * exception value nor node_system_error carried a `path` — return a bounded
- * `contexts.incomplete_install` block so the next occurrence carries the
- * evidence this one lacked; otherwise return undefined (bare capture). Built
- * with the byte-capped, scrubber-safe discipline of package-root-diagnostics.ts:
- * the resolved package root and whether its package.json / node_modules exist,
- * the loader-frame marker, and the bounded errno code — never a caller argv,
- * query, or user-minted value. Never throws.
- *
- * main.ts attaches this on the generic capture path exactly as
- * qmdSpawnFailureCaptureContext already does.
+ * Bounded, scrubber-safe diagnostics for a NOT-suppressed third-party bare miss
+ * (HQ-CLI-1Q): a possible undeclared / peer-only dependency defect, made
+ * attributable — the missing package, the requiring package, and the fact that
+ * the requirer's own manifest did NOT declare it. Both names live inside
+ * hq-cli's dependency graph, so grouping cardinality stays bounded.
+ */
+export type IncompleteInstallBareDiagnostics = {
+    missingPackage: string;
+    requiringPackage: string;
+    requirerDeclaresMissing: false;
+};
+/**
+ * Both enriched shapes as a single OPEN record — every field optional so a
+ * consumer can forward either shape to Sentry without narrowing (the boundary
+ * and beforeSend only pass the block through). Every value CONSTRUCTED here is
+ * exactly one of the two strict shapes above; the looseness is only at the read
+ * boundary.
+ */
+export type IncompleteInstallDiagnostics = Partial<IncompleteInstallEsmDiagnostics & IncompleteInstallBareDiagnostics>;
+/**
+ * When an incomplete-install failure reaches the capture path WITHOUT being
+ * suppressed, return a bounded `contexts.incomplete_install` block so the next
+ * occurrence carries the evidence this one lacked; otherwise return undefined
+ * (bare capture). Two enriched shapes:
+ *   - a third-party BARE-specifier miss the requirer did not declare (HQ-CLI-1Q)
+ *     → { missingPackage, requiringPackage, requirerDeclaresMissing:false };
+ *   - an esm-loader ENOENT whose path did not survive delivery (HQ-CLI-1M) — the
+ *     shape the delivered payload arrived in, where neither the exception value
+ *     nor node_system_error carried a `path` → { packageRoot, packageJsonExists,
+ *     nodeModulesExists, esmLoaderFrame, code }.
+ * Built with the byte-capped, scrubber-safe discipline of
+ * package-root-diagnostics.ts — never a caller argv, query, or user-minted
+ * value. Never throws. main.ts attaches this on the generic capture path
+ * exactly as qmdSpawnFailureCaptureContext already does.
  */
-export declare function incompleteInstallCaptureContext(err: unknown, resolvePackageRoot?: PackageRootResolver, fileSystem?: Pick<typeof fs, "existsSync">): {
+export declare function incompleteInstallCaptureContext(err: unknown, resolvePackageRoot?: PackageRootResolver, fileSystem?: Pick<typeof fs, "existsSync"> & Partial<Pick<typeof fs, "readFileSync">>): {
     incomplete_install: IncompleteInstallDiagnostics;
 } | undefined;
 //# sourceMappingURL=incomplete-install-error.d.ts.map

package/dist/utils/incomplete-install-error.js

@@ -7,7 +7,7 @@
 // failure inside THIS process rather than a qmd child's captured stderr, which
 // is the gap HQ-CLI-Y's classifier cannot cover.
 //
-// Two shapes, one cause — a partial/interrupted global install left a file
+// Three shapes, one cause — a partial/interrupted global install left a file
 // unwritten, or a concurrent global install rewrote the running tree
 // underneath a command:
 //
@@ -19,6 +19,16 @@
 //   specifier internal to a third-party package can only be a truncated on-disk
 //   copy, never an hq-cli manifest defect.
 //
+//   HQ-CLI-1Q (Sentry 7716586928) — CJS, in-process. The SAME `import mqtt`
+//   chain, one hop further down: mqtt-packet's `parser.js` requires the BARE
+//   specifier `bl` — mqtt-packet's OWN declared transitive dependency — and it
+//   is absent inside hq-cli's bundled node_modules after a torn Windows global
+//   install. A bare miss looks like an undeclared dependency, but when the
+//   REQUIRING third-party package's own manifest declares it, its absence
+//   beside a present requirer can only be a torn install. hq-cli declares
+//   nothing about a contract between two third-party packages, so this is never
+//   an hq-cli manifest defect.
+//
 //   HQ-CLI-1M (Sentry 7714870912) — ESM load, in-process. A module that existed
 //   at RESOLVE was gone at READ (a concurrent writer rewrote the install tree),
 //   so Node's ESM loader raised `ENOENT` from getSourceSync/readFileSync/openSync
@@ -26,7 +36,7 @@
 //   ERR_MODULE_NOT_FOUND at resolve, never ENOENT at load; an ENOENT at load
 //   proves the file vanished between resolve and read.
 //
-// Both shapes carry no hq-cli frames, reach the boundary's final `else`, and —
+// All shapes carry no hq-cli frames, reach the boundary's final `else`, and —
 // before this classifier — filed a bare captureException plus an unactionable
 // `hq: <fallback>` line. The disposition is the one HQ-CLI-Y already
 // established: an incomplete install is the caller's machine, so the CLI prints
@@ -35,19 +45,26 @@
 // The gate is deliberately narrow so neither an hq-cli packaging fault nor
 // user free-text can trip it. Only structured fields are read — `code`,
 // `syscall`, `path`, `requireStack`, and the stack's loader-frame marker, plus
-// the first message line for the CJS specifier. THREE independent narrowings
+// the first message line for the CJS specifier — plus, for the bare CJS shape
+// only, the requiring package's own on-disk manifest. Independent narrowings
 // keep a genuine hq-cli defect reportable:
 //   1. The failing file must sit under `<packageRoot>/node_modules/` — a
 //      third-party file hq-cli does not author. A miss under `<packageRoot>/dist`
 //      or `/assets` is hq-cli's OWN shipped output and stays captured.
-//   2. The CJS shape additionally requires a RELATIVE specifier — a
-//      bare-specifier miss (`Cannot find module 'mqtt'`) can be an undeclared
-//      dependency (an hq-cli manifest defect) and stays captured.
+//   2. The CJS shape splits on the specifier. A RELATIVE specifier internal to
+//      a package under node_modules can only be a truncated copy (HQ-CLI-1N). A
+//      BARE PACKAGE-ROOT specifier stays captured UNLESS the requiring
+//      third-party package's own manifest declares it in its REQUIRED
+//      `dependencies` (HQ-CLI-1Q). A subpath miss (`bl/lib/x`), an
+//      optional-dependency miss (not guaranteed installed), and an undeclared or
+//      peer-only miss (`Cannot find module 'mqtt'` from a requirer that does not
+//      declare it) all stay loud — the last two enriched with both package names.
 //   3. The ESM shape additionally requires an esm-loader frame — an ordinary
 //      `fs.readFileSync` ENOENT written by hq's own code stays captured.
 import * as fs from "fs";
 import * as path from "path";
 import { packageRoot } from "./hq-roots.js";
+import { packageNameOf } from "./install-tree-torn.js";
 import { boundedDiagnosticValue } from "./package-root-diagnostics.js";
 /**
  * The actionable remedy shown to the operator. Input-free — nothing from the
@@ -72,6 +89,11 @@ const RELATIVE_SPECIFIER = /^\.\.?[\\/]/;
 const ESM_LOADER_FRAME = /node:internal[\\/]modules[\\/]esm[\\/]/;
 const ROOT_DIAGNOSTIC_BYTES = 256;
 const CODE_DIAGNOSTIC_BYTES = 32;
+// Package names live inside hq-cli's own dependency graph, so their universe is
+// bounded; the cap is a belt for a pathological requireStack, not a real limit.
+const PACKAGE_NAME_DIAGNOSTIC_BYTES = 128;
+/** The `<something>/node_modules/<something>` directory-boundary marker. */
+const NODE_MODULES_SEGMENT = "/node_modules/";
 /**
  * packageRoot() walks up from the compiled module and THROWS
  * PackageRootResolutionError when it cannot resolve. This classifier runs inside
@@ -132,6 +154,114 @@ function parseMissingSpecifier(message) {
     const match = message.match(/Cannot find module ['"]([^'"]+)['"]/);
     return match ? match[1] : null;
 }
+/**
+ * True when `specifier` is a BARE package specifier — neither a RELATIVE
+ * specifier (`./x`, `..\x`) nor an ABSOLUTE POSIX (`/x`) or Windows (`C:\x`,
+ * `\\unc`) path. Shape-based (never `process.platform`) so a reported Windows
+ * path classifies on a Linux CI runner, mirroring normalizeForCompare's win32
+ * detection.
+ */
+function isBareSpecifier(specifier) {
+    if (specifier.length === 0)
+        return false;
+    if (RELATIVE_SPECIFIER.test(specifier))
+        return false;
+    if (specifier.startsWith("/"))
+        return false; // absolute POSIX
+    if (looksWin32(specifier))
+        return false; // absolute Windows (drive letter or UNC)
+    return true;
+}
+/**
+ * True when `specifier` is a bare specifier naming a PACKAGE ROOT with no
+ * subpath — `bl` or `@scope/name`, never `bl/lib/inner.js` or `@scope/name/sub`.
+ * Only a WHOLE-package miss is a proven torn install; a subpath miss can mean the
+ * package IS installed but that one file is absent because of a version or
+ * packaging mismatch — a real defect that must stay reported, not be silenced as
+ * a torn install.
+ */
+function isBarePackageRoot(specifier) {
+    return isBareSpecifier(specifier) && specifier === packageNameOf(specifier);
+}
+/**
+ * From a file under `<root>/node_modules/…`, derive the REQUIRING package's
+ * directory and its package name, nesting- and scope-aware:
+ *   `<root>/node_modules/a/node_modules/b/index.js` → dir `…/b`,          name `b`
+ *   `<root>/node_modules/@scope/pkg/index.js`       → dir `…/@scope/pkg`, name `@scope/pkg`
+ * Keyed on the LAST `node_modules` segment so the INNERMOST (actually requiring)
+ * package is chosen, consuming two path segments for an `@scope/name` dir. The
+ * returned dir preserves the original case and is folded to `/` (Node's fs
+ * accepts `/` on every platform); the win32 shape only case-folds the SEARCH so
+ * the segment is found, never the returned value. Returns null when the path
+ * holds no usable package segment.
+ */
+function requiringPackage(requiringFile) {
+    const folded = foldSeparators(requiringFile);
+    const win = looksWin32(requiringFile);
+    const haystack = win ? folded.toLowerCase() : folded;
+    const marker = win ? NODE_MODULES_SEGMENT.toLowerCase() : NODE_MODULES_SEGMENT;
+    const lastNm = haystack.lastIndexOf(marker);
+    if (lastNm === -1)
+        return null;
+    const prefixEnd = lastNm + NODE_MODULES_SEGMENT.length;
+    const prefix = folded.slice(0, prefixEnd); // `…/node_modules/`, original case
+    const rest = folded
+        .slice(prefixEnd)
+        .split("/")
+        .filter((segment) => segment.length > 0);
+    if (rest.length === 0)
+        return null;
+    const take = rest[0].startsWith("@") ? 2 : 1;
+    if (rest.length < take)
+        return null;
+    const name = rest.slice(0, take).join("/");
+    return { dir: prefix + name, name };
+}
+/** True when `deps` is an object carrying `packageName` as an OWN key. */
+function declaresDependency(deps, packageName) {
+    return (typeof deps === "object" &&
+        deps !== null &&
+        Object.prototype.hasOwnProperty.call(deps, packageName));
+}
+/**
+ * Whether the third-party package that REQUIRED `requiringFile` declares
+ * `packageName` in its own REQUIRED `dependencies` — the decisive discriminator
+ * for Shape C (HQ-CLI-1Q). A correct install of a package that declares a
+ * REQUIRED dependency ALWAYS writes it, so its absence beside a present requirer
+ * can only be a torn install. `optionalDependencies` are deliberately EXCLUDED:
+ * they are not guaranteed installed (`npm install --omit optional`, or a
+ * tolerated optional-install failure), so a missing optional package can be a
+ * persistent, expected omission — not a torn install — and must stay captured. A
+ * peer-only / undeclared / hoisting assumption is likewise NOT declared here.
+ * Fails CLOSED: an unresolved dir, an unreadable or invalid-JSON manifest, or a
+ * non-object dependency map all return false. Never throws — every fs and
+ * JSON.parse call is individually guarded. Reached only after the cheap
+ * in-memory narrowings of Shape C pass, so at most one small manifest read per
+ * process.
+ */
+function requirerDeclaresDependency(requiringFile, packageName, fileSystem) {
+    const requirer = requiringPackage(requiringFile);
+    if (!requirer)
+        return false;
+    let raw;
+    try {
+        raw = fileSystem.readFileSync(`${requirer.dir}/package.json`, "utf-8");
+    }
+    catch {
+        return false;
+    }
+    let manifest;
+    try {
+        manifest = JSON.parse(raw);
+    }
+    catch {
+        return false;
+    }
+    if (manifest === null || typeof manifest !== "object")
+        return false;
+    const record = manifest;
+    return declaresDependency(record.dependencies, packageName);
+}
 /** True when `stack` carries a Node ESM loader frame. */
 function hasEsmLoaderFrame(stack) {
     return typeof stack === "string" && ESM_LOADER_FRAME.test(stack);
@@ -161,7 +291,7 @@ function isEsmLoaderEnoent(err) {
  * means "handle as usual (capture to Sentry)". Never throws — a resolver that
  * fails yields null.
  */
-export function incompleteInstallMessage(err, resolvePackageRoot = safePackageRoot) {
+export function incompleteInstallMessage(err, resolvePackageRoot = safePackageRoot, fileSystem = fs) {
     if (err === null || typeof err !== "object")
         return null;
     const record = err;
@@ -172,16 +302,36 @@ export function incompleteInstallMessage(err, resolvePackageRoot = safePackageRo
     if (!root)
         return null;
     if (code === "MODULE_NOT_FOUND") {
-        // Shape A (CJS, HQ-CLI-1N): a RELATIVE specifier internal to a package under
-        // the running install's node_modules can only be a truncated on-disk copy.
         const requireStack = record.requireStack;
         if (!Array.isArray(requireStack) || typeof requireStack[0] !== "string") {
             return null;
         }
+        const requiringFile = requireStack[0];
         const specifier = parseMissingSpecifier(record.message);
-        if (specifier === null || !RELATIVE_SPECIFIER.test(specifier))
+        if (specifier === null)
+            return null;
+        // Shape A (CJS, HQ-CLI-1N) — UNCHANGED: a RELATIVE specifier internal to a
+        // package under the running install's node_modules can only be a truncated
+        // on-disk copy. Kept byte-for-byte so 1N cannot regress.
+        if (RELATIVE_SPECIFIER.test(specifier)) {
+            return isUnderNodeModules(requiringFile, root)
+                ? INCOMPLETE_INSTALL_REMEDY
+                : null;
+        }
+        // Shape C (CJS, HQ-CLI-1Q): a BARE PACKAGE-ROOT specifier missing from UNDER
+        // the running install's node_modules is a torn install ONLY when the
+        // REQUIRING third-party package's own manifest declares it in its required
+        // `dependencies`. A subpath specifier (`bl/lib/inner.js`) is excluded — the
+        // package may be present and only that file gone to a version mismatch — and
+        // an absolute-path specifier is neither relative nor bare, so both stay
+        // captured. The manifest read is the ONLY filesystem access here and is
+        // reached only after the cheap in-memory narrowings above — a combination
+        // that cannot occur on a healthy run — so a healthy event never touches disk.
+        if (!isBarePackageRoot(specifier))
+            return null;
+        if (!isUnderNodeModules(requiringFile, root))
             return null;
-        return isUnderNodeModules(requireStack[0], root)
+        return requirerDeclaresDependency(requiringFile, specifier, fileSystem)
             ? INCOMPLETE_INSTALL_REMEDY
             : null;
     }
@@ -197,27 +347,80 @@ export function incompleteInstallMessage(err, resolvePackageRoot = safePackageRo
         ? INCOMPLETE_INSTALL_REMEDY
         : null;
 }
+/** A readFileSync surface, defaulting to the real fs when the caller injects none. */
+function readFileFrom(fileSystem) {
+    return { readFileSync: fileSystem.readFileSync ?? fs.readFileSync };
+}
 /**
- * When an esm-loader ENOENT reaches the capture path WITHOUT being suppressed —
- * the exact shape the delivered HQ-CLI-1M payload arrived in, where neither the
- * exception value nor node_system_error carried a `path` — return a bounded
- * `contexts.incomplete_install` block so the next occurrence carries the
- * evidence this one lacked; otherwise return undefined (bare capture). Built
- * with the byte-capped, scrubber-safe discipline of package-root-diagnostics.ts:
- * the resolved package root and whether its package.json / node_modules exist,
- * the loader-frame marker, and the bounded errno code — never a caller argv,
- * query, or user-minted value. Never throws.
- *
- * main.ts attaches this on the generic capture path exactly as
- * qmdSpawnFailureCaptureContext already does.
+ * When a third-party BARE-specifier CJS miss UNDER the running install's
+ * node_modules reached the capture path WITHOUT being suppressed (HQ-CLI-1Q) —
+ * i.e. the requiring package did NOT declare it, so it is a possible undeclared
+ * or peer-only dependency defect — return a bounded `incomplete_install` block
+ * naming both packages so the next occurrence is attributable instead of bare;
+ * otherwise undefined. The suppression decision is delegated to
+ * incompleteInstallMessage against the SAME injected filesystem, so a declared
+ * (torn-install) miss is never double-attributed here. Never throws.
+ */
+function bareSpecifierCaptureContext(err, resolvePackageRoot, fileSystem) {
+    if (err === null || typeof err !== "object")
+        return undefined;
+    const record = err;
+    if (record.code !== "MODULE_NOT_FOUND")
+        return undefined;
+    const requireStack = record.requireStack;
+    if (!Array.isArray(requireStack) || typeof requireStack[0] !== "string")
+        return undefined;
+    const requiringFile = requireStack[0];
+    const specifier = parseMissingSpecifier(record.message);
+    // Only a WHOLE-package bare miss is attributed here, matching the classifier's
+    // Shape C gate: a subpath miss is a version/packaging defect, not "the package
+    // is missing", so naming the package would misattribute it.
+    if (specifier === null || !isBarePackageRoot(specifier))
+        return undefined;
+    const root = resolveRootSafely(resolvePackageRoot);
+    if (!root || !isUnderNodeModules(requiringFile, root))
+        return undefined;
+    // Suppressed (the requirer declares it) → printed-and-skipped, never captured.
+    if (incompleteInstallMessage(err, resolvePackageRoot, readFileFrom(fileSystem)) !== null) {
+        return undefined;
+    }
+    return {
+        incomplete_install: {
+            missingPackage: boundedDiagnosticValue(specifier, PACKAGE_NAME_DIAGNOSTIC_BYTES),
+            requiringPackage: boundedDiagnosticValue(requiringPackage(requiringFile)?.name ?? "<unresolved>", PACKAGE_NAME_DIAGNOSTIC_BYTES),
+            requirerDeclaresMissing: false,
+        },
+    };
+}
+/**
+ * When an incomplete-install failure reaches the capture path WITHOUT being
+ * suppressed, return a bounded `contexts.incomplete_install` block so the next
+ * occurrence carries the evidence this one lacked; otherwise return undefined
+ * (bare capture). Two enriched shapes:
+ *   - a third-party BARE-specifier miss the requirer did not declare (HQ-CLI-1Q)
+ *     → { missingPackage, requiringPackage, requirerDeclaresMissing:false };
+ *   - an esm-loader ENOENT whose path did not survive delivery (HQ-CLI-1M) — the
+ *     shape the delivered payload arrived in, where neither the exception value
+ *     nor node_system_error carried a `path` → { packageRoot, packageJsonExists,
+ *     nodeModulesExists, esmLoaderFrame, code }.
+ * Built with the byte-capped, scrubber-safe discipline of
+ * package-root-diagnostics.ts — never a caller argv, query, or user-minted
+ * value. Never throws. main.ts attaches this on the generic capture path
+ * exactly as qmdSpawnFailureCaptureContext already does.
  */
 export function incompleteInstallCaptureContext(err, resolvePackageRoot = safePackageRoot, fileSystem = fs) {
+    // (A) HQ-CLI-1Q — the not-suppressed third-party bare miss, made attributable.
+    const bare = bareSpecifierCaptureContext(err, resolvePackageRoot, fileSystem);
+    if (bare)
+        return bare;
+    // (B) HQ-CLI-1M — the path-less esm-loader ENOENT, unchanged.
     if (!isEsmLoaderEnoent(err))
         return undefined;
     // Only instrument what we did NOT already confidently suppress: a path under
     // node_modules is classified and printed above, never captured.
-    if (incompleteInstallMessage(err, resolvePackageRoot) !== null)
+    if (incompleteInstallMessage(err, resolvePackageRoot, readFileFrom(fileSystem)) !== null) {
         return undefined;
+    }
     const record = err;
     const root = resolveRootSafely(resolvePackageRoot);
     const code = typeof record.code === "string" ? record.code : "";

package/dist/utils/network-transport-error.js

@@ -53,11 +53,21 @@ const TRANSPORT_CODE_REASONS = {
  * Recognized undici error names, for builds where the `code` property is
  * absent but the typed error still identifies itself (the shape Sentry
  * recorded for HQ-CLI-G was `ConnectTimeoutError`).
+ *
+ * `TimeoutError` is the DOMException `AbortSignal.timeout(...)` rejects a
+ * bounded `fetch()` with when the peer accepts the connection but never answers
+ * — Sentry HQ-CLI-1P (issue 7716090679). It is the one transport failure here
+ * that identifies itself ONLY by name: its legacy DOMException `code` is the
+ * NUMBER 23, so the string-typed `readStringProperty(node, "code")` above skips
+ * it, and it carries no `cause` to walk, leaving just the name. `AbortError` is
+ * deliberately NOT listed — a caller-initiated abort is not a transport fault
+ * and must stay reportable.
  */
 const TRANSPORT_NAME_REASONS = {
     ConnectTimeoutError: "the connection timed out",
     HeadersTimeoutError: "the server did not respond in time",
     SocketError: "the connection closed unexpectedly",
+    TimeoutError: "the server did not respond in time",
 };
 /**
  * Depth cap for `cause` traversal. A self-referential or mutually-referential

package/dist/utils/vault-api.js

@@ -19,6 +19,24 @@ import { planGateErrorFromResponse } from './plan-gate-error.js';
  * whole-process watchdog.
  */
 const IDENTITY_LOOKUP_TIMEOUT_MS = 15_000;
+/**
+ * The identity-lookup abort bound, in milliseconds. Defaults to the shipped
+ * IDENTITY_LOOKUP_TIMEOUT_MS (15s). An optional HQ_IDENTITY_LOOKUP_TIMEOUT_MS
+ * override (clamped to a sane 100..120_000 ms window; absent or non-numeric
+ * input keeps the 15s default) exists purely so the artifact E2E can force the
+ * abort in well under a second instead of stalling a spawned CLI for the full
+ * 15s per case. It does NOT change shipped behaviour: with the var unset every
+ * call uses 15s exactly as before.
+ */
+function identityLookupTimeoutMs() {
+    const raw = process.env.HQ_IDENTITY_LOOKUP_TIMEOUT_MS?.trim();
+    if (!raw)
+        return IDENTITY_LOOKUP_TIMEOUT_MS;
+    const parsed = Number(raw);
+    if (!Number.isFinite(parsed))
+        return IDENTITY_LOOKUP_TIMEOUT_MS;
+    return Math.min(120_000, Math.max(100, Math.trunc(parsed)));
+}
 /**
  * Best-effort peek of a 2xx JSON body for plan-limit status (US-016).
  *
@@ -279,7 +297,7 @@ async function resolveCompanyByUid(token, uid) {
     const res = await vaultApiFetch({
         token,
         path: `/entity/${encodeURIComponent(uid)}`,
-        signal: AbortSignal.timeout(IDENTITY_LOOKUP_TIMEOUT_MS),
+        signal: AbortSignal.timeout(identityLookupTimeoutMs()),
     });
     if (!res.ok) {
         raiseIfUnauthorized(res);
@@ -312,7 +330,7 @@ async function resolveSlugInCallerNamespace(token, slug) {
         token,
         path: '/entity/check-slug/me',
         query: { type: 'company', slug },
-        signal: AbortSignal.timeout(IDENTITY_LOOKUP_TIMEOUT_MS),
+        signal: AbortSignal.timeout(identityLookupTimeoutMs()),
     });
     if (!res.ok) {
         raiseIfUnauthorized(res);
@@ -336,7 +354,28 @@ async function resolveCompanyUid(token, ref) {
     // PRIMARY PATH — caller-scoped slug resolution. Resolves the slug to the
     // caller's OWN company (unique within their namespace by the invariant
     // above), making a stranger's same-slug company invisible.
-    const mine = await resolveSlugInCallerNamespace(token, ref);
+    //
+    // A non-2xx already degrades to the global fallback below (via `return null`).
+    // A TRANSPORT failure must degrade the SAME way, not abort the command:
+    // `resolveSlugInCallerNamespace`'s fetch is bounded by AbortSignal.timeout, so
+    // a vault gateway that accepts the connection but never answers rejects with a
+    // DOMException named `TimeoutError`. Before this catch, that rejection threw
+    // straight out of `resolveCompanyUid`, skipped the global by-slug lookup, and
+    // — being unclassified by main.ts — filed a Sentry crash report instead of an
+    // actionable connectivity message (Sentry HQ-CLI-1P / issue 7716090679).
+    // Degrade ONLY on a recognized transport failure; re-throw everything else
+    // unchanged, so a genuine hq-cli defect stays fatal and the 401 AuthError that
+    // `raiseIfUnauthorized` throws still short-circuits before any fallback.
+    let mine;
+    try {
+        mine = await resolveSlugInCallerNamespace(token, ref);
+    }
+    catch (err) {
+        if (networkTransportErrorCode(err) === null) {
+            throw err;
+        }
+        mine = null;
+    }
     if (mine) {
         return mine;
     }
@@ -347,7 +386,7 @@ async function resolveCompanyUid(token, ref) {
     const res = await vaultApiFetch({
         token,
         path: `/entity/by-slug/company/${encodeURIComponent(ref)}`,
-        signal: AbortSignal.timeout(IDENTITY_LOOKUP_TIMEOUT_MS),
+        signal: AbortSignal.timeout(identityLookupTimeoutMs()),
     });
     if (!res.ok) {
         raiseIfUnauthorized(res);
@@ -374,7 +413,7 @@ async function resolveCompanyFromMemberships(token) {
     const res = await vaultApiFetch({
         token,
         path: '/membership/me',
-        signal: AbortSignal.timeout(IDENTITY_LOOKUP_TIMEOUT_MS),
+        signal: AbortSignal.timeout(identityLookupTimeoutMs()),
     });
     if (!res.ok) {
         throw new Error("Failed to fetch memberships — run `hq login` and try again");
@@ -421,7 +460,7 @@ export async function resolveCallerPersonUid(token, baseUrl) {
         token,
         path: '/entity/by-type/person',
         baseUrl,
-        signal: AbortSignal.timeout(IDENTITY_LOOKUP_TIMEOUT_MS),
+        signal: AbortSignal.timeout(identityLookupTimeoutMs()),
     });
     if (!res.ok) {
         throw new Error("Failed to fetch person entity — run `hq login` and try again");

package/package.json

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