@gamaze/hicortex 0.17.0 → 0.17.1

package/README.md

@@ -218,6 +218,7 @@ Config at `~/.hicortex/config.json`. Created by `init`. Key options:
 | `captureCooldownHours` | Success-cooldown (hours) for the **capture watchdog** (0.17). The capture timer polls every ~20 min; the watchdog captures only if more than this has elapsed since the last *successful* capture (`state.lastNightly`). Default `6` (≈4 captures/day). A failed preflight retries on the next poll (~20 min) — so a transient fire-instant network miss costs minutes, not a day (#239) |
 | `consolidationHours` | Hours (0–23, local) for the **consolidation** timer — the full nightly (capture + distill + score + reflect + link). Installed for **server/co-located only** (clients have no local DB). Default `[10, 22]`: the 22:00 evening slot runs after the day's capture waves (same-day results); the 10:00 morning slot runs *after* the morning capture so wake-up pushes are caught. Omitted on clients |
 | `consolidateMaxLlmCalls` | Ceiling on total LLM calls across all classify-tier consolidation stages (content-domain, link discovery, supersession) per run. A runaway **backstop**, not a throughput throttle — on a free local model the binding constraint is the nightly unit's wall-clock timeout, not call count. Default `5000` (was a hard-coded 200 that starved link/supersession during a classification backlog) |
+| `updateChannel` | Release channel pinned into the generated daemon/timer ExecStart for **npx-thin** installs (global-binary installs use the absolute binary and are unaffected). A dist-tag (`"rc"`, `"next"`) or an exact version (`"0.17.1"`). E.g. `"rc"` → the timer runs `npx -y @gamaze/hicortex@rc nightly`, so the host tracks the rc dist-tag (an internal fleet can ride rc through a pre-promotion soak). Validated as `[\w.\-]+` (rejects anything that'd break the unit/plist templates). Absent → auto-detect (bare on `latest`, else `@next`). (0.17.1) |
 | `nightlyHour` | **Deprecated (0.17) single-slot fallback.** Local hour (0–23) honoured only when `consolidationHours` is absent — yields one daily consolidation slot at that hour (preserves the pre-0.17 "one daily job" intent). New installs should use `consolidationHours` |
 | `preflightTimeoutMs` | **Client mode only.** Per-attempt timeout for the nightly's server-reachability check before it starts capturing (default: 20000 ms, bumped from 15000 in 0.17 to absorb a cold Tailscale handshake on a roaming laptop) |
 | `preflightAttempts` | **Client mode only.** Reachability-check retries before the nightly aborts (default: 3; floored at 1). `1` = single try, no retry |

package/dist/init.d.ts

@@ -262,6 +262,23 @@ export declare const GENERIC_DEFAULT_DOMAINS: DomainDef[];
 export declare function scaffoldDefaultDomains(configPath: string): {
     scaffolded: boolean;
 };
+/**
+ * Determine the npm package specifier used in the generated daemon/timer
+ * ExecStart (for npx-thin installs — global-binary installs use the absolute
+ * binary path and never call this). Tag-based so restarts pick up new versions.
+ *
+ * Priority:
+ *   1. `updateChannel` config key (e.g. "rc") → `@gamaze/hicortex@<channel>`.
+ *      Lets an install pin a release channel — the internal fleet sets "rc" so
+ *      its npx-thin hosts track the rc dist-tag through a pre-promotion soak
+ *      (otherwise the auto-detect below pins @next, which lags rc).
+ *   2. Auto-detect: bare `@gamaze/hicortex` if the running version matches the
+ *      npm `latest` tag, else `@gamaze/hicortex@next` (legacy pre-0.10 cron
+ *      installs follow @next).
+ *
+ * Exported + `configDir`-parametrised so the channel override is unit-testable.
+ */
+export declare function getPackageSpec(configDir?: string): string;
 /**
  * True if a resolved binary path lives in npm's ephemeral npx cache
  * (`~/.npm/_npx/<hash>/node_modules/.bin/…`). When `hicortex init` is itself

package/dist/init.js

@@ -32,6 +32,7 @@ exports.decideAgentName = decideAgentName;
 exports.writeAgentNameConfig = writeAgentNameConfig;
 exports.writeClientConfig = writeClientConfig;
 exports.scaffoldDefaultDomains = scaffoldDefaultDomains;
+exports.getPackageSpec = getPackageSpec;
 exports.isEphemeralNpxPath = isEphemeralNpxPath;
 exports.installSessionStartHook = installSessionStartHook;
 exports.installRecallHooks = installRecallHooks;
@@ -242,15 +243,23 @@ function verifyCcMcp() {
     }
 }
 function allowHicortexTools() {
-    let settings = {};
-    if ((0, node_fs_1.existsSync)(CC_SETTINGS)) {
-        try {
-            settings = JSON.parse((0, node_fs_1.readFileSync)(CC_SETTINGS, "utf-8"));
-        }
-        catch {
-            console.log(`  ⚠ ${CC_SETTINGS} exists but is not valid JSON — skipping tool permissions. Fix the file, then re-run init or add "mcp__hicortex__*" to permissions.allow manually.`);
-            return;
-        }
+    // Only EDIT an existing CC settings file — never invent one. On a host with
+    // no CC client (a server, or a Hermes-only box) ~/.claude/settings.json is
+    // absent; creating a stub there is wrong, and the earlier mkdir+write was the
+    // ENOENT throw on bedrock's init. Without this entry CC just PROMPTS before
+    // tool use instead of auto-allowing — the MCP still works either way.
+    if (!(0, node_fs_1.existsSync)(CC_SETTINGS)) {
+        console.log(`  ℹ ${CC_SETTINGS} not found — skipping CC tool permissions (no CC client here; ` +
+            `the MCP works, CC will ask before tool use).`);
+        return;
+    }
+    let settings;
+    try {
+        settings = JSON.parse((0, node_fs_1.readFileSync)(CC_SETTINGS, "utf-8"));
+    }
+    catch {
+        console.log(`  ⚠ ${CC_SETTINGS} exists but is not valid JSON — skipping tool permissions. Fix the file, then re-run init or add "mcp__hicortex__*" to permissions.allow manually.`);
+        return;
     }
     if (!settings.permissions)
         settings.permissions = {};
@@ -261,7 +270,6 @@ function allowHicortexTools() {
     const rule = "mcp__hicortex__*";
     if (!allow.includes(rule)) {
         allow.push(rule);
-        (0, node_fs_1.mkdirSync)((0, node_path_1.dirname)(CC_SETTINGS), { recursive: true });
         (0, node_fs_1.writeFileSync)(CC_SETTINGS, JSON.stringify(settings, null, 2));
         console.log(`  ✓ Added Hicortex tool permissions to ${CC_SETTINGS}`);
     }
@@ -1068,14 +1076,38 @@ function scaffoldDefaultDomains(configPath) {
     return { scaffolded: true };
 }
 /**
- * Determine the npm package specifier for the daemon.
- * Uses tag-based resolution so restarts pick up new versions automatically.
+ * Determine the npm package specifier used in the generated daemon/timer
+ * ExecStart (for npx-thin installs — global-binary installs use the absolute
+ * binary path and never call this). Tag-based so restarts pick up new versions.
  *
- * Checks if the current version matches the npm `latest` tag.
- * If not (e.g. running from @next), uses @gamaze/hicortex@next.
- * If it does match latest, uses bare @gamaze/hicortex.
+ * Priority:
+ *   1. `updateChannel` config key (e.g. "rc") → `@gamaze/hicortex@<channel>`.
+ *      Lets an install pin a release channel — the internal fleet sets "rc" so
+ *      its npx-thin hosts track the rc dist-tag through a pre-promotion soak
+ *      (otherwise the auto-detect below pins @next, which lags rc).
+ *   2. Auto-detect: bare `@gamaze/hicortex` if the running version matches the
+ *      npm `latest` tag, else `@gamaze/hicortex@next` (legacy pre-0.10 cron
+ *      installs follow @next).
+ *
+ * Exported + `configDir`-parametrised so the channel override is unit-testable.
  */
-function getPackageSpec() {
+function getPackageSpec(configDir = HICORTEX_HOME) {
+    try {
+        const { config } = loadConfigStrict((0, node_path_1.join)(configDir, "config.json"));
+        const ch = config.updateChannel;
+        if (typeof ch === "string") {
+            const trimmed = ch.trim();
+            // A dist-tag (rc/next/latest) or an exact version — alphanumerics, dot,
+            // dash, underscore only. Reject anything else: a newline would break the
+            // systemd `ExecStart=` one-liner and `<`/`&` would break the launchd plist
+            // XML the timer writes. Fall through to auto-detect + warn.
+            if (/^[\w.\-]+$/.test(trimmed))
+                return `@gamaze/hicortex@${trimmed}`;
+            console.warn(`[hicortex] config "updateChannel" = ${JSON.stringify(ch)} is not a valid dist-tag/version ` +
+                `(use e.g. "rc", "next", or "0.17.1") — ignored.`);
+        }
+    }
+    catch { /* no config yet, or malformed — fall through to auto-detect */ }
     try {
         const currentVersion = JSON.parse((0, node_fs_1.readFileSync)((0, node_path_1.join)(__dirname, "..", "package.json"), "utf-8")).version;
         const latestVersion = (0, node_child_process_1.execSync)("npm view @gamaze/hicortex version 2>/dev/null", {

package/dist/types.d.ts

@@ -244,6 +244,15 @@ export interface HicortexConfig {
      * classification backlog and drained large backlogs at ~cap/night).
      */
     consolidateMaxLlmCalls?: number;
+    /**
+     * Release channel pinned into the generated daemon/timer ExecStart for
+     * **npx-thin** installs (global-binary installs use the absolute binary path
+     * and are unaffected). E.g. `"rc"` → the timer runs
+     * `npx -y @gamaze/hicortex@rc nightly`, so the host tracks the rc dist-tag
+     * (the internal fleet uses this to ride rc through a pre-promotion soak).
+     * Absent → auto-detect (bare on `latest`, else `@next`). (0.17.1)
+     */
+    updateChannel?: string;
     /**
      * Minimum cosine(memory embedding, best domain prototype) for a no-fit
      * memory to earn a WEAK primary instead of decaying (see nofit.ts).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gamaze/hicortex",
-  "version": "0.17.0",
+  "version": "0.17.1",
   "description": "Self-learning memory for AI agents — experience captured automatically, distilled into lessons overnight, shared across your whole fleet. Works with Hermes, OpenClaw, Claude Code, and Pi.",
   "main": "dist/index.js",
   "bin": {