@camstack/system 1.2.271 → 1.2.273

package/dist/index.js

@@ -1,6 +1,6 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 const require_chunk = require("./chunk-Cek0wNdY.js");
-const require_dist = require("./dist-_YWIPtUH.js");
+const require_dist = require("./dist-D5ONNqL6.js");
 const require_builtins_alerts_alerts_addon = require("./builtins/alerts/alerts.addon.js");
 require("./builtins/alerts/index.js");
 const require_formatter = require("./formatter-DqAKDlvN.js");
@@ -94942,14 +94942,19 @@ function runnerRssBudgetMb(addons) {
 	return declared.length === 0 ? void 0 : Math.max(...declared);
 }
 /**
-* Per-placement V8 heap flags (Block D). LIGHT runners cap their young generation
-* (`--max-semi-space-size`) to reclaim V8's over-reservation — a measured ~15 MB/runner win — and
-* keep an opt-in old-space cap (`CAMSTACK_RUNNER_LIGHT_MAX_OLD_MB`, unset = uncapped). HEAVY
+* Per-placement V8 flags (Block D). LIGHT runners cap their young generation
+* (`--max-semi-space-size`) to reclaim V8's over-reservation — a measured ~15 MB/runner win — bound
+* V8's platform thread pool (`--v8-pool-size`, see {@link LIGHT_V8_POOL_SIZE_DEFAULT}: a measured
+* ~58 threads across the hub's 29 light runners, against a cgroup `pids.max` this host has already
+* hit) and keep an opt-in old-space cap (`CAMSTACK_RUNNER_LIGHT_MAX_OLD_MB`, unset = uncapped). HEAVY
 * runners keep V8's default young generation but ALWAYS carry an old-space ceiling; see
 * {@link HEAVY_MAX_OLD_MB_DEFAULT} for why, and how a runner declares its own.
 *
 * Kill-switch: `CAMSTACK_RUNNER_HEAP_TUNING=off` disables all flags (recover without a rebuild).
-* Overrides: `CAMSTACK_RUNNER_LIGHT_SEMI_SPACE_MB` (default 2), `CAMSTACK_RUNNER_LIGHT_MAX_OLD_MB`
+* Overrides: `CAMSTACK_RUNNER_LIGHT_SEMI_SPACE_MB` (default 2),
+* `CAMSTACK_RUNNER_LIGHT_V8_POOL_SIZE` (default {@link LIGHT_V8_POOL_SIZE_DEFAULT}; below 1 omits
+* the flag — `0` means "size from the CPU count" to V8, not "off"),
+* `CAMSTACK_RUNNER_LIGHT_MAX_OLD_MB`
 * (default unset = no old-space cap), `CAMSTACK_RUNNER_HEAVY_MAX_OLD_MB`
 * (default {@link HEAVY_MAX_OLD_MB_DEFAULT}; `0` restores the old uncapped behaviour).
 */
@@ -94960,6 +94965,8 @@ function runnerHeapFlags(addons) {
 	if (!heavy) {
 		const semiMb = positiveIntEnv("CAMSTACK_RUNNER_LIGHT_SEMI_SPACE_MB", 2);
 		if (semiMb > 0) flags.push(`--max-semi-space-size=${semiMb}`);
+		const v8Pool = positiveIntEnv("CAMSTACK_RUNNER_LIGHT_V8_POOL_SIZE", 2);
+		if (v8Pool > 0) flags.push(`--v8-pool-size=${v8Pool}`);
 	}
 	const oldMb = runnerMaxOldSpaceMb(addons, heavy);
 	if (oldMb > 0) flags.push(`--max-old-space-size=${oldMb}`);

package/dist/index.mjs

@@ -1,5 +1,5 @@
 import { a as __toCommonJS, i as __require, n as __esmMin, o as __toESM$1, r as __exportAll, t as __commonJSMin$1 } from "./chunk-CNf5ZN-e.mjs";
-import { An as readinessKey, Cn as expandCapMethods, F as addonSettingsCapability, Ft as procedureAuthKey, Mn as scopeKey, Mt as objectInputDeclaresAddonId, On as parseJsonObject, Pn as EventCategory$1, S as RUNTIME_DEFAULTS, Tt as looseSchema, Ut as scopesAllowAddon, Vt as resolveMethodAuth, Wt as scopesAllowDeviceCap, _n as asJsonObject$1, _t as isVoidInput, an as errMsg$1, bn as createEvent, bt as lifecycleJobSchema, cn as DATAPLANE_SECRET_HEADER$1, dt as isArrayOutputSchema, ft as isCollectionArrayMethod, g as LOG_LEVEL_RANK, hn as ReadinessTimeoutError, jn as resolveCapMount, kn as parseJsonUnknown, ln as DEVICE_SETTINGS_CONTRIBUTION_METHODS, mn as ReadinessRegistry, mt as isObjectInput, st as extractNestedAddonId, t as ALL_CAPABILITY_DEFINITIONS, un as DEVICE_STATUS_METHOD, vn as asNumber, vt as kebabToCamel, wt as logLevelAtMost, xn as emitDownForOwnedCaps, y as METHOD_ACCESS_MAP, yn as asString$1 } from "./dist-Diz59Dhi.mjs";
+import { An as readinessKey, Cn as expandCapMethods, F as addonSettingsCapability, Ft as procedureAuthKey, Mn as scopeKey, Mt as objectInputDeclaresAddonId, On as parseJsonObject, Pn as EventCategory$1, S as RUNTIME_DEFAULTS, Tt as looseSchema, Ut as scopesAllowAddon, Vt as resolveMethodAuth, Wt as scopesAllowDeviceCap, _n as asJsonObject$1, _t as isVoidInput, an as errMsg$1, bn as createEvent, bt as lifecycleJobSchema, cn as DATAPLANE_SECRET_HEADER$1, dt as isArrayOutputSchema, ft as isCollectionArrayMethod, g as LOG_LEVEL_RANK, hn as ReadinessTimeoutError, jn as resolveCapMount, kn as parseJsonUnknown, ln as DEVICE_SETTINGS_CONTRIBUTION_METHODS, mn as ReadinessRegistry, mt as isObjectInput, st as extractNestedAddonId, t as ALL_CAPABILITY_DEFINITIONS, un as DEVICE_STATUS_METHOD, vn as asNumber, vt as kebabToCamel, wt as logLevelAtMost, xn as emitDownForOwnedCaps, y as METHOD_ACCESS_MAP, yn as asString$1 } from "./dist-DrLhdcwI.mjs";
 import { AlertCenterAddon } from "./builtins/alerts/alerts.addon.mjs";
 import "./builtins/alerts/index.mjs";
 import { t as formatLogLine } from "./formatter-B7qW8bPJ.mjs";
@@ -94935,14 +94935,19 @@ function runnerRssBudgetMb(addons) {
 	return declared.length === 0 ? void 0 : Math.max(...declared);
 }
 /**
-* Per-placement V8 heap flags (Block D). LIGHT runners cap their young generation
-* (`--max-semi-space-size`) to reclaim V8's over-reservation — a measured ~15 MB/runner win — and
-* keep an opt-in old-space cap (`CAMSTACK_RUNNER_LIGHT_MAX_OLD_MB`, unset = uncapped). HEAVY
+* Per-placement V8 flags (Block D). LIGHT runners cap their young generation
+* (`--max-semi-space-size`) to reclaim V8's over-reservation — a measured ~15 MB/runner win — bound
+* V8's platform thread pool (`--v8-pool-size`, see {@link LIGHT_V8_POOL_SIZE_DEFAULT}: a measured
+* ~58 threads across the hub's 29 light runners, against a cgroup `pids.max` this host has already
+* hit) and keep an opt-in old-space cap (`CAMSTACK_RUNNER_LIGHT_MAX_OLD_MB`, unset = uncapped). HEAVY
 * runners keep V8's default young generation but ALWAYS carry an old-space ceiling; see
 * {@link HEAVY_MAX_OLD_MB_DEFAULT} for why, and how a runner declares its own.
 *
 * Kill-switch: `CAMSTACK_RUNNER_HEAP_TUNING=off` disables all flags (recover without a rebuild).
-* Overrides: `CAMSTACK_RUNNER_LIGHT_SEMI_SPACE_MB` (default 2), `CAMSTACK_RUNNER_LIGHT_MAX_OLD_MB`
+* Overrides: `CAMSTACK_RUNNER_LIGHT_SEMI_SPACE_MB` (default 2),
+* `CAMSTACK_RUNNER_LIGHT_V8_POOL_SIZE` (default {@link LIGHT_V8_POOL_SIZE_DEFAULT}; below 1 omits
+* the flag — `0` means "size from the CPU count" to V8, not "off"),
+* `CAMSTACK_RUNNER_LIGHT_MAX_OLD_MB`
 * (default unset = no old-space cap), `CAMSTACK_RUNNER_HEAVY_MAX_OLD_MB`
 * (default {@link HEAVY_MAX_OLD_MB_DEFAULT}; `0` restores the old uncapped behaviour).
 */
@@ -94953,6 +94958,8 @@ function runnerHeapFlags(addons) {
 	if (!heavy) {
 		const semiMb = positiveIntEnv("CAMSTACK_RUNNER_LIGHT_SEMI_SPACE_MB", 2);
 		if (semiMb > 0) flags.push(`--max-semi-space-size=${semiMb}`);
+		const v8Pool = positiveIntEnv("CAMSTACK_RUNNER_LIGHT_V8_POOL_SIZE", 2);
+		if (v8Pool > 0) flags.push(`--v8-pool-size=${v8Pool}`);
 	}
 	const oldMb = runnerMaxOldSpaceMb(addons, heavy);
 	if (oldMb > 0) flags.push(`--max-old-space-size=${oldMb}`);

package/dist/kernel/moleculer/process-service.d.ts

@@ -59,6 +59,60 @@ interface RunnerAddonSpec {
  * Reaching for a bigger number here when RSS is the complaint is the standard wrong move.
  */
 export declare const HEAVY_MAX_OLD_MB_DEFAULT = 1024;
+/**
+ * V8 platform worker threads for a LIGHT runner (`--v8-pool-size`).
+ *
+ * ## What this bounds
+ *
+ * Node gives every process a V8 platform thread pool — background compilation,
+ * parallel marking and sweeping — defaulted to 4. It is not the libuv pool
+ * (`UV_THREADPOOL_SIZE`, which serves `fs`/`dns`/`zlib`/`crypto`) and it is
+ * deliberately not touched here; see below.
+ *
+ * ## Why it is worth a flag
+ *
+ * A container cgroup counts THREADS, not processes, and this cluster forks a
+ * runner per addon (D2). Measured on the live hub 2026-09-18 (20 cores,
+ * `pids.max=2048`), after 22 fork refusals in 45 minutes earlier that day:
+ *
+ *   pids.current 991 · 47 node processes holding 469 threads
+ *   of those, 29 LIGHT runners holding 274 (mean 9.4 threads each)
+ *
+ * A light runner is a control-plane addon with a 2 MB young generation. It does
+ * not generate the background GC work four marking threads exist for, and it
+ * pays 4 threads of the cgroup's pid budget for them anyway. Two returns ~58
+ * threads — ~6% of the container's live thread count — for background GC that
+ * is, on these heaps, a few milliseconds a cycle.
+ *
+ * ## Why TWO and never ZERO
+ *
+ * `--v8-pool-size=0` does not disable the pool: it tells V8 to size it from the
+ * detected parallelism. Measured locally 2026-09-18 on a node process holding
+ * the libuv pool open:
+ *
+ *   default            11 threads
+ *   --v8-pool-size=2    9 threads
+ *   --v8-pool-size=0   18 threads
+ *
+ * So a value below 1 omits the flag entirely rather than being passed through —
+ * the same trap as `MALLOC_ARENA_MAX=0` in `runner-native-allocator.ts`. To turn
+ * the tuning off, use `CAMSTACK_RUNNER_HEAP_TUNING=off`.
+ *
+ * ## What is deliberately NOT bounded
+ *
+ * HEAVY runners keep V8's default: they hold real heaps (the recorder declares
+ * 3072 MB) where parallel marking is the difference between a pause and a stall.
+ *
+ * `UV_THREADPOOL_SIZE` is left alone on every runner. Its 4 threads are lazily
+ * spawned, and the measurement above says most light runners have spawned all
+ * four — i.e. they really do run concurrent `fs` work. Halving that would trade
+ * ~58 more threads for serialized filesystem I/O in runners whose I/O profile
+ * has not been measured, on a media system. A thread saving is not worth a
+ * media gap.
+ *
+ * Override: `CAMSTACK_RUNNER_LIGHT_V8_POOL_SIZE`.
+ */
+export declare const LIGHT_V8_POOL_SIZE_DEFAULT = 2;
 interface SpawnedProcess {
     readonly pid: number;
     readonly nodeId: string;

package/dist/{retired-settings-keys-C2ocoH_l.js → retired-settings-keys-1686ou3s.js}

@@ -1,4 +1,4 @@
-const require_dist = require("./dist-_YWIPtUH.js");
+const require_dist = require("./dist-D5ONNqL6.js");
 //#region src/builtins/sqlite-storage/retired-settings-keys.ts
 /**
 * Is THIS node the one whose settings store is the cluster's authority?

package/dist/{retired-settings-keys-C_Hg5d37.mjs → retired-settings-keys-Du_0qedo.mjs}

@@ -1,4 +1,4 @@
-import { _n as asJsonObject } from "./dist-Diz59Dhi.mjs";
+import { _n as asJsonObject } from "./dist-DrLhdcwI.mjs";
 //#region src/builtins/sqlite-storage/retired-settings-keys.ts
 /**
 * Is THIS node the one whose settings store is the cluster's authority?

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/system",
-  "version": "1.2.271",
+  "version": "1.2.273",
   "description": "Core addon for CamStack — builtins, pipeline, process management, auth, logging, events",
   "keywords": [
     "camstack",