@camstack/server 1.2.631 → 1.2.633

package/THIRD_PARTY_MODELS.md

@@ -218,6 +218,6 @@ object-detection catalogs) on request. They are downloaded from their
 publishers, are not hosted or redistributed by CamStack, and keep their
 publishers' licences; Model Studio shows the licence where the source declares
 one. A model you upload or convert
-yourself, or pull from your own Frigate+ account, likewise keeps whatever
+yourself, or pull from your own plus catalog account, likewise keeps whatever
 licence its author published. CamStack does not change it and does not record
 it.

package/dist/agent/addon-scan.js

@@ -48,7 +48,7 @@ exports.planAgentAddonScan = planAgentAddonScan;
  * drifted because no update channel refreshed it"*.
  *
  * The agent never got the change, and drifted exactly as predicted. Measured
- * 2026-08-11: little-unraid carried `@camstack/system@1.2.61` and macmini
+ * 2026-08-11: agent-a carried `@camstack/system@1.2.61` and macmini
  * `1.2.62` in their addon roots while both ran a `1.2.78` closure. Nothing
  * refreshed them, because `seedBuiltinsFromClosure` (now deleted) only wrote
  * the copy when it was ABSENT — a self-heal that guaranteed a copy existed and

package/dist/agent/agent-infra-capabilities.js

@@ -22,7 +22,7 @@ exports.resolveAgentInfraCapabilities = resolveAgentInfraCapabilities;
  * The commit before this one gave that door the hub as its remote, so dropping
  * the engine leaves nothing stranded.
  *
- * Measured on `little-unraid` before the change: 17 tables, 33 objects, one
+ * Measured on `agent-a` before the change: 17 tables, 33 objects, one
  * page each. Every `*:addon-settings` table — `hub-forwarder`,
  * `metrics-native`, `platform-probe`, `storage-orchestrator`, and the shared
  * `addon-settings` — held **0 rows**. The only non-empty tables were

package/dist/agent/infra-boot-guard.js

@@ -10,7 +10,7 @@
  *   - the addon was NOT FOUND at all                    → `console.error`, continue.
  *
  * The second branch is strictly worse than the first and it was the quiet one.
- * On `little-unraid` the whole `@camstack/system` package was renamed out of
+ * On `agent-a` the whole `@camstack/system` package was renamed out of
  * `/data/addons/@camstack/` at 16:40 on 2026-08-07 (a builtin-shadow cleanup).
  * On an AGENT that directory is the SOLE source of the builtins — there is no
  * seed fallback — so the next boot came up with ZERO infra addons: no storage,
@@ -31,7 +31,7 @@
  *
  * It reports EVERY missing required capability in one throw, not just the
  * first — an operator staring at a crash-loop needs the whole list, and the
- * four that vanished together on little-unraid vanished for one single reason.
+ * four that vanished together on agent-a vanished for one single reason.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.assertRequiredInfraResolved = assertRequiredInfraResolved;

package/dist/agent/main.js

@@ -508,7 +508,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" [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`
+        // are: `agent-a` 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
         // through it.

package/dist/api/addon-upload.js

@@ -156,8 +156,8 @@ deliveryLedger) {
         // returned `undefined` for a large one.
         //
         // Cost, 2026-08-07: every `camstack deploy packages/addon-pipeline -n
-        // little-unraid` — a 4.9 MB tarball — read `nodeId = null` and took the HUB
-        // branch. The CLI printed `✓ little-unraid: @camstack/addon-pipeline@1.2.43`
+        // agent-a` — a 4.9 MB tarball — read `nodeId = null` and took the HUB
+        // branch. The CLI printed `✓ agent-a: @camstack/addon-pipeline@1.2.43`
         // (the label it INTENDED, never the target the hub used) and the named agent
         // was never addressed at all. It reproduced 4× and was diagnosed as a stale
         // dist. Reading the fields after the drain is the fix here; the CLI also

package/dist/api/agent-addon-delivery.js

@@ -14,7 +14,7 @@ exports.deliverAddonToAgent = deliverAddonToAgent;
  * every runner on that node keeps executing the PREVIOUS dist until something
  * else happens to restart it.
  *
- * Reproduced on little-unraid 2026-08-07 with a marker file inside `dist/`: the
+ * Reproduced on agent-a 2026-08-07 with a marker file inside `dist/`: the
  * marker was on disk 2 seconds after the `✓`, and not one of the 12 addon-runner
  * pids had been recycled. Four operators-hours were spent that day looking for a
  * stale tarball cache that does not exist — the bytes were always correct, they
@@ -31,7 +31,7 @@ exports.deliverAddonToAgent = deliverAddonToAgent;
  * `$agent.deploy` is the INSTALL, not a control call.
  *
  * This constant used to be 30 s and said "install work is bounded well inside
- * this". On 2026-09-11 that claim cost `little-unraid` an evening of running a
+ * this". On 2026-09-11 that claim cost `agent-a` an evening of running a
  * previous `addon-pipeline` dist: three deploys, three
  * `Request is timed out when call '$agent.deploy'` at exactly 30 s, while the
  * CLI printed `✓ Deployed to 1 target(s)` each time — true of the hub, silent

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

@@ -34,7 +34,7 @@
  *     dispatcher has no notion of a DEFAULT provider and never had one: a
  *     collection cap's binding set is derived and plural, so an absent pin
  *     left the fan-out un-narrowed and bought a union. The cap's docblock
- *     said otherwise for a day, and device 592 answered a `limit: 3` call
+ *     said otherwise for a day, and device 107 answered a `limit: 3` call
  *     with six rows because of it.
  *  2. **One failing source never empties the others.** Every source is called
  *     independently and a rejection removes only its own rows — and says so,
@@ -96,9 +96,9 @@ const DEVICE_MANAGER_CAP = 'device-manager';
  * framework's answer to "which providers does this device have".
  *
  * It used to enumerate REGISTRATIONS, and that is what put `analytics` in the
- * picker three times on the first live run (device 592, 2026-09-20): one addon
+ * picker three times on the first live run (device 107, 2026-09-20): one addon
  * reached here as the device's native provider, as the hub-local registration
- * and again as `pipeline-analytics@little-unraid`, with a fourth on the Mac
+ * and again as `pipeline-analytics@agent-a`, with a fourth on the Mac
  * node that `resolveCollectionForDevice` had already dropped. Three tick-boxes
  * for one thing, and `listClips` triplicating every row underneath them.
  *

package/dist/closure-patches/patch-reach.json

@@ -33,7 +33,7 @@
         "its whole tree — parser included — into `@camstack/system/dist`, and the",
         "patch travels inside the published tarball. Verified 2026-09-12 in the",
         "`@camstack/system@1.2.224` tarball and in the live closure on both the",
-        "hub and the little-unraid agent.",
+        "hub and the agent-a agent.",
         "",
         "The closure ALSO carries an unpatched `node_modules/moleculer` — npm",
         "installs it for `@camstack/system`'s dependency entry — and exactly one",
@@ -88,7 +88,7 @@
         "installer's closure-dedupe (D343) links all three at ONE copy. That copy",
         "is a plain npm tarball. The closure has no `patches/` directory and had",
         "no lifecycle step that could apply one, so production ran werift 0.22.9",
-        "UNPATCHED — verified 2026-09-12 on the hub, the little-unraid agent and",
+        "UNPATCHED — verified 2026-09-12 on the hub, the agent-a agent and",
         "the Mac-mini Electron agent, all three showing `RTP_HISTORY_SIZE = 128`",
         "and no forceTurn guard.",
         "",

package/dist/core/addon/addon-package.service.js

@@ -714,7 +714,7 @@ class AddonPackageService {
      * version string is not a build. `@camstack/addon-pipeline@1.2.43` deployed
      * from the workspace and `@camstack/addon-pipeline@1.2.43` on npm were two
      * different bundles all of 2026-08-07, and every `camstack deploy` to
-     * little-unraid was silently reverted ~1.5s later: the deploy's own
+     * agent-a was silently reverted ~1.5s later: the deploy's own
      * `$agent.reload` briefly emptied the node's reported addon list, the hub's
      * reconcile read it as "package missing", and the back-fill repaired the node
      * by installing the PUBLISHED 1.2.43 over the one just delivered. Nothing

package/dist/core/agent/agent-addon-backfill.js

@@ -9,7 +9,7 @@
  * "installed on the hub but missing on the node". A node whose `<dataDir>/addons`
  * had been wiped therefore came back with only its bootstrap packages
  * (`@camstack/system` + `camstack.agentBootstrapAddons`) and the hub never sent
- * the rest — measured live as 4 of 14 packages on `little-unraid`. Under the
+ * the rest — measured live as 4 of 14 packages on `agent-a`. Under the
  * volume-only image (no addons baked in) an empty addons dir is the ORDINARY
  * first-boot state of every new or rebuilt node, so that gap becomes the normal
  * case rather than an anomaly.

package/dist/core/agent/agent-delivery-ledger.js

@@ -10,7 +10,7 @@
  *   1. `$agent.deploy`'s `onApplied` evicts the package's declaration ids from
  *      the node's `loadedAddons`, so `$agent.status` stops reporting it;
  *   2. `$agent.reload` re-instantiates every runner, and a status read landing
- *      mid-reload sees a PARTIAL roster — measured on `little-unraid`
+ *      mid-reload sees a PARTIAL roster — measured on `agent-a`
  *      2026-08-07 as the same reconcile reporting "14 checked" and, seconds
  *      later, "20 checked";
  *   3. the reload re-registers the node, which fires the reconcile, which reads
@@ -41,7 +41,7 @@ exports.AgentDeliveryLedger = exports.DELIVERY_GRACE_MS = void 0;
  *
  * Sized for the re-registration storm: `$agent.reload` returns when the runners
  * have been asked to restart, and their `$hub.registerNode` calls (one per
- * group runner — 12 on `little-unraid`) land over the following seconds. Each
+ * group runner — 12 on `agent-a`) land over the following seconds. Each
  * one fires a reconcile.
  */
 exports.DELIVERY_GRACE_MS = 60_000;

package/dist/core/agent/agent-registry.service.js

@@ -626,7 +626,7 @@ class AgentRegistryService {
      * declared (`ClusterNodeHistoryStore.getPackages`), delivering whatever is
      * missing. Without it a node whose addons dir was wiped came back with only
      * its bootstrap packages and the hub never sent the rest — 4 of 14 on
-     * `little-unraid`, measured. Under the volume-only image that empty state is
+     * `agent-a`, measured. Under the volume-only image that empty state is
      * the ordinary first boot of every rebuilt node. See `agent-addon-backfill.ts`
      * for what defines the intended set and how retries are bounded.
      *

package/dist/core/moleculer/agent-registration-request.js

@@ -9,7 +9,7 @@
  * agent's own view of the hub never breaks, so nothing on the agent says "send
  * your manifest again". When the hub then sees the agent again
  * (`$node.connected`), it holds an online node with NO capabilities. On
- * 2026-10-14 little-unraid and the Mac sat that way for 50 minutes.
+ * 2026-10-14 agent-a and the Mac sat that way for 50 minutes.
  *
  * So on every `$node.connected` of an agent the hub calls
  * `$agent.requestRegistration`: one RPC, on the event, no timer (D3). The

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

@@ -624,7 +624,7 @@ class MoleculerService {
         // agent is authoritative for. Cross-node `system.ready-state` deltas
         // are telemetry (lossy) — a lost post-restart `ready` used to leave
         // this registry stuck on the synthesized `down` forever (2026-07-17:
-        // pipeline-executor@little-unraid, 3.5h dispatch outage). The
+        // pipeline-executor@agent-a, 3.5h dispatch outage). The
         // periodic sweep below repairs deltas lost while CONNECTED.
         this.broker.localBus.on('$node.connected', ({ node }) => {
             const nodeId = node.id;

package/dist/core/server-update/system-apply-closure-patches.js

@@ -47,7 +47,7 @@ exports.buildSystemApplyClosurePatches = buildSystemApplyClosurePatches;
  * thing that notices is `findUnappliedClosurePatches` refusing the swap.
  *
  * Measured 2026-09-13 on the Mac-mini agent, which had bootstrapped npm 12.0.1
- * while hub and little-unraid still ran npm 11. That node sat two versions
+ * while hub and agent-a still ran npm 11. That node sat two versions
  * behind with no other symptom, and the applier — run by hand in the very same
  * staging closure — reported `APPLIED werift@0.22.9` on three files. The code
  * was never wrong; it was never called.

package/dist/core/update-availability-emitter.js

@@ -9,12 +9,12 @@ const types_1 = require("@camstack/types");
  *
  * One event carries the entire currently-available list **of one node** — the
  * scope that changed, never the union across nodes. The Notification Center
- * turns that into "2 aggiornamenti addon disponibili su little-unraid" with
+ * turns that into "2 aggiornamenti addon disponibili su agent-a" with
  * that node's packages under it.
  *
  * The union was the shape until 2026-08-19, and on a three-node cluster one
  * 6-hourly sweep sent the operator THREE pushes that each listed hub +
- * MacMiniAgent + little-unraid and named no node: every scope's change
+ * MacMiniAgent + agent-a and named no node: every scope's change
  * re-emitted the whole held map, so the notifications differed by one line and
  * read as identical. A list is only actionable if it belongs to somebody.
  *

package/dist/manual-boot.js

@@ -184,7 +184,7 @@ async function bootManual(opts) {
     // calling `packPackage` — `npm pack <name>@<version>` — so the back-fill
     // repaired a node by installing the REGISTRY's build of a version over the
     // one an operator had just deployed. Same name, same version, different
-    // bundle: every `camstack deploy … -n little-unraid` on 2026-08-07 was
+    // bundle: every `camstack deploy … -n agent-a` on 2026-08-07 was
     // reverted ~1.5s later and read as a stale dist. See `packInstalledPackage`.
     // Delivery is an RPC pair, never an event (D8/D11).
     const backfillLogger = loggingService.createLogger('agent-backfill');

package/package.json

@@ -1,7 +1,16 @@
 {
   "name": "@camstack/server",
-  "version": "1.2.631",
+  "version": "1.2.633",
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/camstack/server.git",
+    "directory": "server/backend"
+  },
+  "homepage": "https://camstack-docs.zentik.app",
+  "bugs": {
+    "url": "https://github.com/camstack/server/issues"
+  },
   "private": false,
   "files": [
     "dist",
@@ -38,20 +47,20 @@
     ]
   },
   "dependencies": {
-    "@camstack/addon-admin-ui": "1.2.468",
-    "@camstack/addon-agent-ui": "1.2.267",
-    "@camstack/addon-auth": "1.2.166",
-    "@camstack/addon-benchmark": "1.2.266",
-    "@camstack/addon-decoder-nodeav": "1.2.141",
-    "@camstack/addon-notifiers": "1.2.619",
-    "@camstack/addon-pipeline": "1.2.625",
-    "@camstack/addon-pipeline-orchestrator": "1.2.627",
-    "@camstack/addon-post-analysis": "1.2.634",
-    "@camstack/develop": "0.1.34",
-    "@camstack/sdk": "1.2.151",
-    "@camstack/system": "1.2.482",
-    "@camstack/types": "1.2.414",
-    "@camstack/ui-library": "1.2.323",
+    "@camstack/addon-admin-ui": "1.2.470",
+    "@camstack/addon-agent-ui": "1.2.269",
+    "@camstack/addon-auth": "1.2.168",
+    "@camstack/addon-benchmark": "1.2.268",
+    "@camstack/addon-decoder-nodeav": "1.2.142",
+    "@camstack/addon-notifiers": "1.2.621",
+    "@camstack/addon-pipeline": "1.2.627",
+    "@camstack/addon-pipeline-orchestrator": "1.2.629",
+    "@camstack/addon-post-analysis": "1.2.636",
+    "@camstack/develop": "0.1.36",
+    "@camstack/sdk": "1.2.153",
+    "@camstack/system": "1.2.484",
+    "@camstack/types": "1.2.416",
+    "@camstack/ui-library": "1.2.325",
     "@fastify/compress": "^9.0.0",
     "@fastify/cookie": "^11.0.2",
     "@fastify/cors": "^11.2.0",