@solongate/proxy 0.83.55 → 0.83.57

package/dist/hook-health.d.ts

@@ -0,0 +1,26 @@
+export interface HookStart {
+    ok: boolean;
+    /** The node the launcher resolved, when it resolved one. */
+    node?: string;
+    detail: string;
+}
+/**
+ * Run the launcher's own resolution and report what it found.
+ *
+ * It runs the INSTALLED launcher rather than reimplementing its search here.
+ * A second copy of the candidate list would drift from the first, and the drift
+ * would be invisible: the check would pass while the thing it stands for
+ * failed.
+ */
+export declare function hookCanStart(): HookStart;
+export interface HookBeat {
+    hook: string;
+    at: Date;
+    /** What the launcher resolved that time, or `no-node` when it resolved nothing. */
+    node: string;
+}
+/** Every hook that has ever been invoked on this machine, newest first. */
+export declare function hookBeats(): HookBeat[];
+/** The guard's own beat, which is the one that means enforcement happened. */
+export declare function guardBeat(): HookBeat | null;
+export declare function agoLabel(d: Date): string;

package/dist/hook-launcher.d.ts

@@ -0,0 +1,57 @@
+/**
+ * The launcher that stands between an agent client and a hook script.
+ *
+ * WHY THIS EXISTS
+ *
+ * A hook is registered as a command string in somebody else's config file, and
+ * that string used to name a node binary by absolute path — `process.execPath`
+ * at install time. The absolute path was deliberate and is still right: Claude
+ * Code runs hooks in a non-interactive environment whose PATH frequently has no
+ * `node` on it, and bare `node` there fails with "command not found" while the
+ * client reports nothing at all.
+ *
+ * What was wrong is that `process.execPath` RESOLVES SYMLINKS. On the machines
+ * where this bit, that is the whole story:
+ *
+ *   Homebrew  /opt/homebrew/bin/node is a symlink into
+ *             /opt/homebrew/Cellar/node/<version>/bin/node, so execPath records
+ *             the VERSIONED path — and `brew upgrade` moves it and `brew
+ *             cleanup` deletes it. The stable symlink was right there and we
+ *             wrote down the thing it pointed at.
+ *   nvm/fnm   ~/.nvm/versions/node/v22.11.0/bin/node, and the version directory
+ *   /volta    goes away the moment that version is uninstalled or pruned.
+ *
+ * Linux distro node is /usr/bin/node and Windows node is under Program Files;
+ * neither moves. macOS is where node is nearly always under a version manager,
+ * which is why "it works everywhere except on the Mac" is the shape this took.
+ *
+ * When the recorded path is gone, the client spawns a command that cannot start.
+ * Nothing enforces, nothing is logged, and every status this CLI printed still
+ * said "guard registered" — because it was registered. It just could not run.
+ *
+ * WHAT THIS DOES
+ *
+ * Resolve node at RUN time, from a list that starts with the recorded path and
+ * falls through every place a Mac actually keeps one. Then exec the hook, so no
+ * extra process is left behind.
+ *
+ * And leave a mark. The launcher touches a beat file before it does anything
+ * else, which is the one fact nothing else in this product could establish: that
+ * the client invoked the hook at all. "Registered but never fired" and "fired
+ * but enforcing nothing" are different faults with different fixes and they
+ * looked identical from the outside.
+ */
+/** Where the launcher lives, relative to the hooks directory. */
+export declare const LAUNCHER_NAME = "sg-run.sh";
+/** Where the beat files live, relative to ~/.solongate. */
+export declare const BEAT_DIR = ".beat";
+/**
+ * The launcher, with the install-time node baked in.
+ *
+ * POSIX sh, because /bin/sh is the one interpreter every macOS and Linux has at
+ * a fixed path. It runs before every single tool call, so it forks nothing on
+ * the happy path: the candidate tests are builtins, the beat file is written by
+ * a redirect whose MTIME is the timestamp, and the hook is `exec`d rather than
+ * spawned.
+ */
+export declare function launcherScript(pinnedNode: string): string;