@indigoai-us/hq-cli 5.345.27 → 5.345.29

package/dist/commands/core-checkpoint.d.ts

@@ -1,76 +1,3 @@
-/**
- * `hq core checkpoint` — synchronous end-of-turn state capture plus an
- * optional detached HQ-maintenance sibling.
- *
- * The foreground command intentionally performs only local filesystem and git
- * reads/writes. It never waits for the sibling, and it never performs network
- * I/O itself.
- */
-import * as fs from "node:fs";
-import { Command } from "commander";
-type Backend = "claude" | "codex" | "grok" | "none";
-type SpawnableBackend = Exclude<Backend, "none">;
-/**
- * Printed after every non-dry-run checkpoint, real or --idle. Agents were
- * treating the checkpoint call as the end of the turn, leaving their actual
- * findings only in the checkpoint payload — which the user never sees. This
- * line rides the command output (the one channel guaranteed to reach the
- * calling agent) to force the user-facing reply. Deliberately conditional on
- * whether the reply was already delivered this turn: an unconditional
- * "restate in full" made agents repeat a reply the user had already seen
- * (both the CLI and the desktop app render pre-tool-call text), while an
- * unconditional "no commentary after" hid the reply from agents that had not
- * yet written one. The Stop gate makes the same distinction from the
- * transcript — and backstops this reminder mechanically: a satisfying
- * checkpoint on a work turn whose genuine reply is still missing is blocked
- * once with a dedicated reply demand. This line covers proactive checkpoints
- * the gate never sees. Mirrors the hq-core policies
- * `checkpoint-is-bookkeeping-not-user-communication` and
- * `checkpoint-is-not-the-user-report`.
- */
-export declare const CHECKPOINT_REPLY_REMINDER: string;
-/**
- * The --idle variant: an idle-only turn (nothing ran, nothing to report) is
- * exempt at the Stop gate, so this text must never order a reply into
- * existence — but an --idle after read-only work is NOT exempt (the gate
- * demands the findings), so the conditional half still points there.
- */
-export declare const CHECKPOINT_IDLE_REPLY_REMINDER: string;
-export declare function renderSiblingPrompt(runDir: string, payloadPath: string, options?: {
-    company?: string | null;
-    hqRoot?: string;
-}): string;
-export type WriteStampsOptions = {
-    /**
-     * Filesystem seam (default the real `node:fs`); injected in tests to force a
-     * permission errno so the HqStateWriteError conversion can be proven without a
-     * real unwritable path.
-     */
-    fs?: Pick<typeof fs, "mkdirSync" | "writeFileSync" | "renameSync" | "unlinkSync">;
-    /** Runtime seam for proving the Windows-only atomic path without host assumptions. */
-    platform?: NodeJS.Platform;
-    /** Synchronous delay seam for the bounded Windows lock retry. */
-    waitForRetry?: (delayMs: number) => void;
-};
-export declare function writeStamps(liveRoot: string, sessionId: string | undefined, options?: WriteStampsOptions): string[];
-/**
- * Preference order for `--backend auto`: the caller's own backend first, so a
- * claude session keeps using claude and a codex session keeps using codex
- * (same-engine continuity), then the fallback priority claude -> codex -> grok
- * for whatever the caller is not. Deterministic and env-only, so it is unit
- * tested directly. `preferGrok` (the company's grok-backend flag) puts grok
- * ahead of that order and leaves the rest as the fallback.
- */
-export declare function autoBackendPreference(preferGrok?: boolean): SpawnableBackend[];
-/**
- * Whether the payload company's last ontology plan recorded
- * checkpoint.ontology.grok-backend as on. Reads only the local state file the
- * detached sibling writes, so a foreground checkpoint never waits on the flag
- * registry; a flag change takes effect from the checkpoint after the next plan.
- */
-export declare function companyPrefersGrok(liveRoot: string, companySlug: string | null | undefined): boolean;
-export declare function siblingArgs(backend: SpawnableBackend, prompt: string): string[];
-/** Attach the native checkpoint command to the hidden `hq core` group. */
-export declare function registerCoreCheckpointCommand(core: Command): void;
-export {};
+/** Full command-graph compatibility entry for the isolated checkpoint handler. */
+export * from "./core-checkpoint-native.js";
 //# sourceMappingURL=core-checkpoint.d.ts.map