@camstack/server 1.2.431 → 1.2.433

package/dist/agent/main.js

@@ -406,7 +406,7 @@ async function startAgent(configPath) {
         }
         // ONE COPY PER NODE — the same sweep the hub runs, at this role's own
         // healthy-boot moment (D45, task 32). Operator, 2026-08-13: "l'agente deve
-        // essere identico all'hub". An agent is where the redundant copies actually
+        // essere identico all'hub" [the agent must be identical to the hub]. An agent is where the redundant copies actually
         // are: `little-unraid` still holds `<dataDir>/addons/@camstack/system@1.2.78`
         // — a copy nothing loads (both roles pass `['@camstack/system']` as the
         // loader's skip list) and that WINS over the closure for anything resolving
@@ -484,6 +484,8 @@ async function startAgent(configPath) {
     // back to broker-only (no parentUdsPath propagated). See moleculer.service.ts.
     let agentParentUdsPath;
     let agentUdsRegistry;
+    /** The agent's cluster bus, set once the broker is started (see `lifecycleEvents` below). */
+    let agentLifecycleBus = null;
     try {
         const agentNodeId = broker.nodeID;
         // F0 (slice-5 outbound): route a forked child's unowned `ctx.api.<cap>`
@@ -534,6 +536,21 @@ async function startAgent(configPath) {
         });
         agentUdsRegistry = new system_1.LocalChildRegistry({
             server: (0, system_1.createLocalTransport)().createServer(agentNodeId),
+            // `WorkerOnline` / `WorkerOffline` `<agent>/<childId>` for a forked runner
+            // (no broker of its own, so no `$node.connected`), on the agent's
+            // cluster-broadcasting bus. The bus exists only after `broker.start()`;
+            // runners are spawned after it (`loadClusterCapableAddons`), and an
+            // event before it is said, never silent.
+            lifecycleEvents: {
+                parentNodeId: () => agentNodeId,
+                emit: (event) => {
+                    if (agentLifecycleBus === null) {
+                        consoleLogger.info(`runner lifecycle event before the agent bus exists — dropped: ${event.category}`);
+                        return;
+                    }
+                    agentLifecycleBus.emit(event);
+                },
+            },
             // The agent's own id — a cap call pinned to THIS agent (e.g. the
             // benchmark running `pipeline-executor.runPipeline` on the very node it
             // is on) is served by the co-resident sibling instead of being forwarded
@@ -686,6 +703,7 @@ async function startAgent(configPath) {
     // was not started (no UDS children). Wired after broker.start() so
     // getBrokerEventBus returns the fully operational shared bus.
     const agentBrokerEventBus = (0, system_1.getBrokerEventBus)(broker);
+    agentLifecycleBus = agentBrokerEventBus;
     agentUpdateService.bindAvailability(agentBrokerEventBus, broker.nodeID);
     let udsEventBridgeDispose = null;
     if (agentUdsRegistry !== undefined) {

package/dist/api/core/logging-settings.js

@@ -6,7 +6,7 @@
  *
  * ## Why one document and not one method per knob
  *
- * The audit in `docs/design/plans/2026-08-26-logging-per-componente.md` found
+ * The audit in `docs/design/plans/2026-08-26-per-component-logging.md` found
  * the level spread over five knobs in three settings panels, two kernel config
  * keys and an env var that never reached an addon. Adding a cap method per
  * knob would have reproduced that on the API. So: adding a logging setting

package/dist/api/trpc/device-collection-dispatch.js

@@ -81,7 +81,7 @@ const SOURCE_ADDON_FIELD = 'addonId';
 /**
  * The input field naming WHICH of a device's providers to ask. One at a time,
  * by `addonId`, never a list of source ids: the operator settled the surface
- * on 2026-09-20 (*"l'utilizzatore è uno solo"*).
+ * on 2026-09-20 (*"l'utilizzatore è uno solo"* [there is only one user]).
  *
  * An absent pin narrows NOTHING — the method fans out, which is right for
  * `listSources` and was never right for `listClips`. Whether absence is

package/dist/core/moleculer/moleculer.service.js

@@ -408,6 +408,12 @@ class MoleculerService {
                 // onUnownedCall (a pin to ANOTHER node still bypasses the sibling).
                 ownNodeId: nodeId,
                 onUnownedCall,
+                // A forked runner has no Moleculer broker, so `$node.connected` never
+                // fires for it: the registry says `WorkerOnline` / `WorkerOffline`
+                // `<hub>/<childId>` itself, on the hub's bus — WorkerOnline at the
+                // pre-init register, before the child initializes (the D696 provider
+                // gate forgets a provider there, before it can restore and seed).
+                lifecycleEvents: { parentNodeId: () => nodeId, emit: (event) => this.eventBus.emit(event) },
                 // `getStatus` of a CLAIMED cap is answered by the hub mirror BEFORE the
                 // sibling short-circuit can dispatch it to the owning child (D663, S3)
                 // — the same resolver the handler above and `callCapabilityOnNode` use.

package/dist/first-boot-addon-plan.js

@@ -10,7 +10,7 @@
  *   the first-boot fallback source; every other addon is single-copy, always,
  *   installed during the initial boot;
  * - **no pinning at all** — *"il sistema è designato per essere
- *   addons-agnostic, latest va sempre bene al primo boot"*. There is no version
+ *   addons-agnostic, latest va sempre bene al primo boot"* [the system is designed to be addons-agnostic, latest is always fine at first boot]. There is no version
  *   contract between the closure and an addon, so first boot asks for `latest`
  *   and the copy that lands is the one the node keeps.
  *

package/dist/launcher.js

@@ -341,8 +341,8 @@ async function launch() {
     //
     // The image no longer bakes a NON-system addon tree, so this roster comes
     // from the registry on a fresh node: "tutti gli altri addons devono rimanere
-    // copia unica, sempre, installati durante l'avvio iniziale" (2026-08-12), at
-    // `latest`, because "il sistema e' designato per essere addons-agnostic"
+    // copia unica, sempre, installati durante l'avvio iniziale" [all the other addons must remain a single copy, always, installed during the initial boot] (2026-08-12), at
+    // `latest`, because "il sistema e' designato per essere addons-agnostic" [the system is designed to be addons-agnostic]
     // (2026-08-13). The plan below is what `ensureRequiredPackages` is about to
     // do, said out loud BEFORE it happens: how many packages this node must fetch
     // (i.e. whether this boot needs the registry at all), and where an installed
@@ -565,7 +565,7 @@ async function launch() {
     // that could both run still scream.
     //
     // NEVER fatal — operator directive, 2026-08-12: "non dovremmo mai prevenire
-    // il boot". There is no flag that turns this into a refusal. A node that
+    // il boot" [we should never prevent the boot]. There is no flag that turns this into a refusal. A node that
     // cannot start is a camera system that is not recording, and the inventory is
     // the thing that was supposed to EXPLAIN a bad layout, not enact a verdict on
     // it. Removing a copy stays an operator decision.

package/dist/single-copy-cleanup-runner.js

@@ -37,7 +37,7 @@ exports.runSingleCopyCleanup = runSingleCopyCleanup;
 /**
  * The one adapter that runs the post-boot single-copy sweep on BOTH roles.
  *
- * Operator, 2026-08-13: *"l'agente deve essere identico all'hub"*. Two code
+ * Operator, 2026-08-13: *"l'agente deve essere identico all'hub"* [the agent must be identical to the hub]. Two code
  * paths that must agree get one implementation — the hub calls this after its
  * boot-health confirmation, the agent after its first acked `registerNode`, and
  * neither owns a private idea of what may be deleted.

package/dist/single-copy-cleanup.js

@@ -7,7 +7,7 @@
  *
  * - the SYSTEM seed stays in the image, as the first-boot and fallback source
  *   (*"teniamo gli addons di sistema nell'immagine per il primo boot, da usare
- *   in caso di fallback"*);
+ *   in caso di fallback"* [we keep the system addons in the image for the first boot, to be used in case of fallback]);
  * - once a node **has booted correctly**, the redundant DATA-side copies are
  *   removed — the legacy `<dataDir>/framework` tree and any host-provided
  *   package sitting under the addon root;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/server",
-  "version": "1.2.431",
+  "version": "1.2.433",
   "license": "MIT",
   "private": false,
   "files": [
@@ -37,18 +37,18 @@
     ]
   },
   "dependencies": {
-    "@camstack/addon-admin-ui": "1.2.300",
-    "@camstack/addon-agent-ui": "1.2.162",
+    "@camstack/addon-admin-ui": "1.2.302",
+    "@camstack/addon-agent-ui": "1.2.163",
     "@camstack/addon-auth": "1.2.124",
     "@camstack/addon-decoder-nodeav": "1.2.116",
     "@camstack/addon-notifiers": "1.2.122",
-    "@camstack/addon-pipeline": "1.2.315",
-    "@camstack/addon-pipeline-orchestrator": "1.2.272",
-    "@camstack/addon-post-analysis": "1.2.311",
+    "@camstack/addon-pipeline": "1.2.316",
+    "@camstack/addon-pipeline-orchestrator": "1.2.273",
+    "@camstack/addon-post-analysis": "1.2.313",
     "@camstack/sdk": "1.2.119",
-    "@camstack/system": "1.2.332",
-    "@camstack/types": "1.2.285",
-    "@camstack/ui-library": "1.2.220",
+    "@camstack/system": "1.2.334",
+    "@camstack/types": "1.2.287",
+    "@camstack/ui-library": "1.2.221",
     "@fastify/compress": "^9.0.0",
     "@fastify/cookie": "^11.0.2",
     "@fastify/cors": "^11.2.0",