@indigoai-us/hq-cli 5.313.0 → 5.314.0

package/dist/utils/feedback-screenshots.d.ts

@@ -1,4 +1,5 @@
 export declare const MAX_SCREENSHOTS = 5;
+export declare const MAX_SCREENSHOT_BYTES: number;
 export declare function contentTypeForPath(filePath: string): string;
 export interface ScreenshotInput {
     path: string;

package/dist/utils/feedback-screenshots.js

@@ -3,7 +3,7 @@ import * as path from "node:path";
 import { vaultApiFetch } from "./vault-api.js";
 export const MAX_SCREENSHOTS = 5;
 // Per-image ceiling. Screenshots are PNG/JPEG captures; 10 MB is generous.
-const MAX_SCREENSHOT_BYTES = 10 * 1024 * 1024;
+export const MAX_SCREENSHOT_BYTES = 10 * 1024 * 1024;
 // Extension → content type. Must stay in sync with the server's allowed set
 // (hq-pro feedback-screenshots.ts ALLOWED_CONTENT_TYPES).
 const EXT_CONTENT_TYPE = {

package/dist/utils/hq-roots.d.ts

@@ -59,31 +59,8 @@ export declare function createPackageRootResolver(options: PackageRootResolverOp
  * answer survives a change in output layout.
  */
 export declare function packageRoot(): string;
-/**
- * Derive this package's installed root from the running module's OWN path using
- * STRING operations only — no `readFileSync`, `realpathSync`, or `existsSync`.
- *
- * {@link packageRoot} must read `<dir>/package.json` and `realpathSync` the
- * module directory to answer, so it THROWS in exactly the situation that most
- * needs an answer: a concurrent global install has renamed the installed
- * package directory aside (`.hq-cli-<rand>`) and is re-extracting it file by
- * file, so both the manifest walk and the dist-owner fallback fail on a
- * directory that is momentarily gone. This walks the compiled module's
- * ancestors as strings and returns the DEEPEST one whose trailing segments are
- * `node_modules/@indigoai-us/hq-cli`, which stays correct while that directory
- * does not exist on disk.
- *
- * It is a FALLBACK only — {@link packageRoot} validates the manifest name and
- * is authoritative whenever it succeeds. Returns null for a dev checkout or any
- * layout without that segment triple, so a caller that falls back to it can
- * only ever degrade to today's behaviour (no resolution), never widen it.
- *
- * The deepest match is deliberate: a nested `node_modules/@indigoai-us/hq-cli`
- * inside another package resolves to ITSELF (the copy the module belongs to),
- * never an outer decoy. Case is folded only for a Windows-shaped path, matching
- * the POSIX case-sensitivity the rest of this module assumes.
- */
-export declare function stringDerivedPackageRoot(moduleFilePath?: string): string | null;
+/** Reset the memoized package root. Tests only. */
+export declare function __resetPackageRootCache(): void;
 export type LiveRootOptions = {
     /** Explicit `--hq-root` value. Highest precedence. */
     hqRoot?: string;

package/dist/utils/hq-roots.js

@@ -170,7 +170,7 @@ export function createPackageRootResolver(options) {
     };
 }
 const currentModulePath = fileURLToPath(import.meta.url);
-const defaultPackageRootResolver = createPackageRootResolver({
+let defaultPackageRootResolver = createPackageRootResolver({
     moduleDir: path.dirname(currentModulePath),
     modulePath: currentModulePath,
 });
@@ -184,72 +184,12 @@ const defaultPackageRootResolver = createPackageRootResolver({
 export function packageRoot() {
     return defaultPackageRootResolver();
 }
-/**
- * The trailing path segments that mark an installed copy of this package:
- * `node_modules` followed by the package name's own segments (for
- * `@indigoai-us/hq-cli`, that is `node_modules/@indigoai-us/hq-cli`).
- */
-const INSTALLED_ROOT_SEGMENTS = ["node_modules", ...CLI_PACKAGE_NAME.split("/")];
-/** A Windows-shaped absolute path (drive letter or UNC), regardless of host OS. */
-function looksWin32Path(p) {
-    return /^[a-zA-Z]:[\\/]/.test(p) || /^\\\\/.test(p);
-}
-/**
- * Derive this package's installed root from the running module's OWN path using
- * STRING operations only — no `readFileSync`, `realpathSync`, or `existsSync`.
- *
- * {@link packageRoot} must read `<dir>/package.json` and `realpathSync` the
- * module directory to answer, so it THROWS in exactly the situation that most
- * needs an answer: a concurrent global install has renamed the installed
- * package directory aside (`.hq-cli-<rand>`) and is re-extracting it file by
- * file, so both the manifest walk and the dist-owner fallback fail on a
- * directory that is momentarily gone. This walks the compiled module's
- * ancestors as strings and returns the DEEPEST one whose trailing segments are
- * `node_modules/@indigoai-us/hq-cli`, which stays correct while that directory
- * does not exist on disk.
- *
- * It is a FALLBACK only — {@link packageRoot} validates the manifest name and
- * is authoritative whenever it succeeds. Returns null for a dev checkout or any
- * layout without that segment triple, so a caller that falls back to it can
- * only ever degrade to today's behaviour (no resolution), never widen it.
- *
- * The deepest match is deliberate: a nested `node_modules/@indigoai-us/hq-cli`
- * inside another package resolves to ITSELF (the copy the module belongs to),
- * never an outer decoy. Case is folded only for a Windows-shaped path, matching
- * the POSIX case-sensitivity the rest of this module assumes.
- */
-export function stringDerivedPackageRoot(moduleFilePath = currentModulePath) {
-    if (typeof moduleFilePath !== "string" || moduleFilePath.length === 0) {
-        return null;
-    }
-    const wanted = INSTALLED_ROOT_SEGMENTS;
-    const caseInsensitive = looksWin32Path(moduleFilePath);
-    const sameSegment = (a, b) => caseInsensitive ? a.toLowerCase() === b.toLowerCase() : a === b;
-    // Tokenise into segments with each one's end offset in the ORIGINAL string,
-    // so the returned root keeps the source path's leading root and separators
-    // verbatim (a leading `/`, or a `C:\` drive) rather than a rejoined guess.
-    const segments = [];
-    const segmentPattern = /[^\\/]+/g;
-    let match;
-    while ((match = segmentPattern.exec(moduleFilePath)) !== null) {
-        segments.push({ text: match[0], end: match.index + match[0].length });
-    }
-    if (segments.length < wanted.length)
-        return null;
-    // Scan from the deepest segment upward; the first (deepest) leaf whose
-    // preceding segments complete the triple wins.
-    for (let leaf = segments.length - 1; leaf >= wanted.length - 1; leaf--) {
-        let matched = true;
-        for (let k = 0; k < wanted.length; k++) {
-            if (!sameSegment(segments[leaf - (wanted.length - 1) + k].text, wanted[k])) {
-                matched = false;
-                break;
-            }
-        }
-        if (matched)
-            return moduleFilePath.slice(0, segments[leaf].end);
-    }
-    return null;
+/** Reset the memoized package root. Tests only. */
+export function __resetPackageRootCache() {
+    defaultPackageRootResolver = createPackageRootResolver({
+        moduleDir: path.dirname(currentModulePath),
+        modulePath: currentModulePath,
+    });
 }
 /**
  * Resolve the user's live HQ installation.

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

@@ -10,14 +10,11 @@ import * as fs from "fs";
 export declare const INCOMPLETE_INSTALL_REMEDY: string;
 /** A resolver for the running install's root; returns null instead of throwing. */
 export type PackageRootResolver = () => string | null;
-/** Which strategy produced the running install's root, recorded in diagnostics. */
-type PackageRootResolverSource = "manifest-walk" | "string-derivation" | "unresolved" | "injected";
 /**
- * If `err` is an in-process incomplete-install module-load failure — the CJS
- * relative-sibling shape (HQ-CLI-1N), the ESM vanished-at-read shape (HQ-CLI-1M),
- * or the resolve-time lstat shape (HQ-CLI-1S), with the failing file confirmed
- * under `<packageRoot>/node_modules/` — return the actionable, input-free reinstall
- * remedy; otherwise return null.
+ * If `err` is an in-process incomplete-install module-load failure — either the
+ * CJS relative-sibling shape (HQ-CLI-1N) or the ESM vanished-file shape
+ * (HQ-CLI-1M), with the failing file confirmed under `<packageRoot>/node_modules/`
+ * — return the actionable, input-free reinstall remedy; otherwise return null.
  *
  * Mirrors qmdModuleMissingMessage so the top-level handler and beforeSend branch
  * the same way: a non-null result means print-the-remedy-and-skip-Sentry, null
@@ -25,51 +22,14 @@ type PackageRootResolverSource = "manifest-walk" | "string-derivation" | "unreso
  * fails yields null.
  */
 export declare function incompleteInstallMessage(err: unknown, resolvePackageRoot?: PackageRootResolver, fileSystem?: Pick<typeof fs, "readFileSync">): string | null;
-/**
- * Bounded, scrubber-safe diagnostics for an unattributable loader/resolver ENOENT
- * whose `path` did not survive delivery — the esm-loader open shape (HQ-CLI-1M) or
- * the resolve-time lstat shape (HQ-CLI-1S). The two frame booleans say which.
- */
-type IncompleteInstallEsmDiagnostics = {
-    /** The resolved install root, or the literal `<unresolved>` when none was found. */
+/** Bounded, scrubber-safe diagnostics for an unattributable esm-loader ENOENT (HQ-CLI-1M). */
+export type IncompleteInstallEsmDiagnostics = {
     packageRoot: string;
-    /** True only when a root was actually resolved (by any strategy). */
-    packageRootResolved: boolean;
-    /** Which resolver answered — so an unresolved root is never read as resolved-but-missing. */
-    resolver: PackageRootResolverSource;
-    /**
-     * Whether `<root>/package.json` and `<root>/node_modules` exist on disk.
-     * Present ONLY when a root was resolved: reported for an unresolved root,
-     * a bare `false` is indistinguishable from "resolved but the file is missing"
-     * — the ambiguity that made the delivered HQ-CLI-1M evidence weaker than
-     * intended (the two booleans were uninitialised defaults).
-     */
-    packageJsonExists?: boolean;
-    nodeModulesExists?: boolean;
-    /** The stack carried an esm-loader (source-read) frame — the HQ-CLI-1M route. */
+    packageJsonExists: boolean;
+    nodeModulesExists: boolean;
     esmLoaderFrame: boolean;
-    /** The stack carried a module-resolver frame — the HQ-CLI-1S resolve-time route. */
-    resolverFrame: boolean;
-    /** The stack carried a CJS loader (source-read) frame — the HQ-CLI-20 route. */
-    cjsLoaderFrame: boolean;
     code: string;
 };
-/**
- * Bounded, scrubber-safe diagnostics for a module-EVALUATION throw that reached
- * the boundary raw (HQ-CLI-1T) — a code-less TypeError/ReferenceError/SyntaxError
- * whose throw site sits under the running install's node_modules, so the next
- * occurrence names the offending third-party package instead of filing bare. Only
- * the closed error name and the bounded package name are recorded; never the
- * message, argv, or a full path.
- */
-type IncompleteInstallEvalThrowDiagnostics = {
-    evalThrow: true;
-    errorName: string;
-    throwSitePackage: string;
-    packageRoot: string;
-    packageRootResolved: boolean;
-    resolver: PackageRootResolverSource;
-};
 /**
  * Bounded, scrubber-safe diagnostics for a NOT-suppressed third-party bare miss
  * (HQ-CLI-1Q): a possible undeclared / peer-only dependency defect, made
@@ -77,57 +37,30 @@ type IncompleteInstallEvalThrowDiagnostics = {
  * the requirer's own manifest did NOT declare it. Both names live inside
  * hq-cli's dependency graph, so grouping cardinality stays bounded.
  */
-type IncompleteInstallBareDiagnostics = {
+export type IncompleteInstallBareDiagnostics = {
     missingPackage: string;
     requiringPackage: string;
     requirerDeclaresMissing: false;
 };
-/** The four lexical scopes a NOT-suppressed CJS relative requirer can fall into. */
-type RelativeRequirerScope = "dist" | "assets" | "outside-root" | "unresolved-root";
-/**
- * Bounded, scrubber-safe diagnostics for a NOT-suppressed CJS RELATIVE-specifier
- * miss (HQ-CLI-1N): the CJS relative-sibling shape that reached the capture path
- * WITHOUT being suppressed — its requirer sits under the install's own `dist/` or
- * `assets/`, outside the running install entirely, or the install root could not
- * be resolved. Records only a bounded, four-value LEXICAL scope of the requirer
- * against the root — never the requirer path and never the specifier — so
- * grouping cardinality cannot inflate. `code` is always `MODULE_NOT_FOUND`.
- */
-type IncompleteInstallRelativeDiagnostics = {
-    code: string;
-    relativeSpecifier: true;
-    packageRoot: string;
-    packageRootResolved: boolean;
-    resolver: PackageRootResolverSource;
-    requirerScope: RelativeRequirerScope;
-};
 /**
- * The enriched shapes as a single OPEN record — every field optional so a
- * consumer can forward any shape to Sentry without narrowing (the boundary and
- * beforeSend only pass the block through). Every value CONSTRUCTED here is
- * exactly one of the strict shapes above; the looseness is only at the read
+ * 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 & IncompleteInstallRelativeDiagnostics & IncompleteInstallEvalThrowDiagnostics>;
+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). Three enriched shapes:
+ * (bare capture). Two enriched shapes:
  *   - a third-party BARE-specifier miss the requirer did not declare (HQ-CLI-1Q)
  *     → { missingPackage, requiringPackage, requirerDeclaresMissing:false };
- *   - a CJS RELATIVE-specifier miss whose requirer sits under the install's own
- *     dist/ or assets/, outside the install, or under an unresolved root
- *     (HQ-CLI-1N) → { code, relativeSpecifier:true, packageRoot,
- *     packageRootResolved, resolver, requirerScope };
- *   - a loader/resolver ENOENT whose path did not survive delivery (HQ-CLI-1M
- *     esm-load open, HQ-CLI-1S resolve-time lstat, HQ-CLI-20 CJS load-time open) —
- *     where neither the exception value nor node_system_error carried a `path` →
- *     { packageRoot, packageJsonExists, nodeModulesExists, esmLoaderFrame,
- *     resolverFrame, cjsLoaderFrame, code };
- *   - a module-EVALUATION throw that reached the boundary raw (HQ-CLI-1T) →
- *     { evalThrow, errorName, throwSitePackage, packageRoot, packageRootResolved,
- *     resolver }.
+ *   - 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
@@ -136,5 +69,4 @@ export type IncompleteInstallDiagnostics = Partial<IncompleteInstallEsmDiagnosti
 export declare function incompleteInstallCaptureContext(err: unknown, resolvePackageRoot?: PackageRootResolver, fileSystem?: Pick<typeof fs, "existsSync"> & Partial<Pick<typeof fs, "readFileSync">>): {
     incomplete_install: IncompleteInstallDiagnostics;
 } | undefined;
-export {};
 //# sourceMappingURL=incomplete-install-error.d.ts.map