@camstack/addon-tailscale 1.2.63 → 1.2.64

package/dist/client/tailscale.addon.js

@@ -24,7 +24,7 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
 	enumerable: true
 }) : target, mod));
 //#endregion
-const require_dist = require("../dist-CM8irv4g.js");
+const require_dist = require("../dist-C-HpGclR.js");
 let node_child_process = require("node:child_process");
 let node_util = require("node:util");
 let node_fs = require("node:fs");

package/dist/client/tailscale.addon.mjs

@@ -1,4 +1,4 @@
-import { a as EventCategory, i as BaseAddon, n as networkAccessCapability, r as BOOT_RECOVERY_BACKOFF_MS, t as meshNetworkCapability } from "../dist-BlLzjzzR.mjs";
+import { a as EventCategory, i as BaseAddon, n as networkAccessCapability, r as BOOT_RECOVERY_BACKOFF_MS, t as meshNetworkCapability } from "../dist-CwE5GhC9.mjs";
 import { execFile, spawn } from "node:child_process";
 import { promisify } from "node:util";
 import * as fs from "node:fs";

package/dist/{dist-CM8irv4g.js → dist-C-HpGclR.js}

@@ -12654,6 +12654,24 @@ method(_void(), _void(), { kind: "mutation" }), method(_void(), _void(), { kind:
 	kind: "mutation",
 	auth: "admin"
 });
+/**
+* Device Manager capability — hub-side singleton that unifies device persistence,
+* live registry access, and all management operations into a single tRPC surface.
+*
+* Replaces:
+*   - `device-persistence` capability (persistence methods absorbed here)
+*   - `device-management.router.ts` (deleted in Phase 2)
+*   - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
+*
+* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
+* fork into separate processes but never run on remote cluster agents. Therefore:
+*   - No nodeId routing needed — this is a pure hub singleton.
+*   - The hub's DeviceRegistry is the single source of truth for all live devices.
+*   - No shadow registry or cross-node aggregation required.
+*
+* Forked workers register devices back to the hub via `ctx.devices`
+* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
+*/
 /** One child-placement directive on a container's `childLayout`. Structurally
 *  identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
 *  shape for the same field. The child is identified by its re-sync-stable
@@ -18319,6 +18337,9 @@ var RetrainStatusSchema = _enum([
 *
 * `debug` does NOT pin; it is attention, not durability.
 *
+* `debugNote` is the operator's own words about WHAT should be checked on this
+* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
+*
 * `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
 * A favourited track is skipped by retention the same way `staging` is, but
 * it does not enter `none|staging|trained` and has no staging budget.
@@ -18329,6 +18350,21 @@ var TrackFlagFields = {
 	markForTrain: boolean().optional(),
 	/** Operator marked this track for diagnostic attention. */
 	debug: boolean().optional(),
+	/**
+	* What the operator wants CHECKED on this track, in their own words.
+	*
+	* The flag alone says "look at this" and nothing about what for; a debug set
+	* reviewed hours later is a list of tracks with no question attached. Bound
+	* to `debug` on the WRITE side — the body clears it when `debug` goes off,
+	* and refuses it on a track whose debug is off — so a note can never outlive
+	* the attention it belongs to.
+	*
+	* `''` is a real value ("marked, nothing to add"); the ABSENT key means
+	* "leave whatever is stored alone", which is what lets a surface turn debug
+	* on without a note (a cancelled prompt) and what lets it edit the note
+	* without touching the flag.
+	*/
+	debugNote: string().max(500).optional(),
 	/** Operator favourited this track. Pins it against pruning. */
 	favourited: boolean().optional()
 };
@@ -18355,6 +18391,12 @@ var TrackFlagsSchema = object({
 	trackId: string(),
 	markForTrain: boolean(),
 	debug: boolean(),
+	/** The note as it STANDS after the write — never absent here (a track with no
+	*  note reports `''`), for the same reason the booleans are required: a
+	*  surface that has just written must be able to render the note it now owns
+	*  without a re-fetch, and an absent key would read as "unchanged" on a
+	*  screen that has no previous value to keep. */
+	debugNote: string(),
 	favourited: boolean(),
 	/** The lifecycle state the boolean was derived from. Required here (unlike on
 	*  a track row) because this shape is only ever produced by the write body,

package/dist/{dist-BlLzjzzR.mjs → dist-CwE5GhC9.mjs}

@@ -12654,6 +12654,24 @@ method(_void(), _void(), { kind: "mutation" }), method(_void(), _void(), { kind:
 	kind: "mutation",
 	auth: "admin"
 });
+/**
+* Device Manager capability — hub-side singleton that unifies device persistence,
+* live registry access, and all management operations into a single tRPC surface.
+*
+* Replaces:
+*   - `device-persistence` capability (persistence methods absorbed here)
+*   - `device-management.router.ts` (deleted in Phase 2)
+*   - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
+*
+* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
+* fork into separate processes but never run on remote cluster agents. Therefore:
+*   - No nodeId routing needed — this is a pure hub singleton.
+*   - The hub's DeviceRegistry is the single source of truth for all live devices.
+*   - No shadow registry or cross-node aggregation required.
+*
+* Forked workers register devices back to the hub via `ctx.devices`
+* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
+*/
 /** One child-placement directive on a container's `childLayout`. Structurally
 *  identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
 *  shape for the same field. The child is identified by its re-sync-stable
@@ -18319,6 +18337,9 @@ var RetrainStatusSchema = _enum([
 *
 * `debug` does NOT pin; it is attention, not durability.
 *
+* `debugNote` is the operator's own words about WHAT should be checked on this
+* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
+*
 * `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
 * A favourited track is skipped by retention the same way `staging` is, but
 * it does not enter `none|staging|trained` and has no staging budget.
@@ -18329,6 +18350,21 @@ var TrackFlagFields = {
 	markForTrain: boolean().optional(),
 	/** Operator marked this track for diagnostic attention. */
 	debug: boolean().optional(),
+	/**
+	* What the operator wants CHECKED on this track, in their own words.
+	*
+	* The flag alone says "look at this" and nothing about what for; a debug set
+	* reviewed hours later is a list of tracks with no question attached. Bound
+	* to `debug` on the WRITE side — the body clears it when `debug` goes off,
+	* and refuses it on a track whose debug is off — so a note can never outlive
+	* the attention it belongs to.
+	*
+	* `''` is a real value ("marked, nothing to add"); the ABSENT key means
+	* "leave whatever is stored alone", which is what lets a surface turn debug
+	* on without a note (a cancelled prompt) and what lets it edit the note
+	* without touching the flag.
+	*/
+	debugNote: string().max(500).optional(),
 	/** Operator favourited this track. Pins it against pruning. */
 	favourited: boolean().optional()
 };
@@ -18355,6 +18391,12 @@ var TrackFlagsSchema = object({
 	trackId: string(),
 	markForTrain: boolean(),
 	debug: boolean(),
+	/** The note as it STANDS after the write — never absent here (a track with no
+	*  note reports `''`), for the same reason the booleans are required: a
+	*  surface that has just written must be able to render the note it now owns
+	*  without a re-fetch, and an absent key would read as "unchanged" on a
+	*  screen that has no previous value to keep. */
+	debugNote: string(),
 	favourited: boolean(),
 	/** The lifecycle state the boolean was derived from. Required here (unlike on
 	*  a track row) because this shape is only ever produced by the write body,

package/dist/ingress/tailscale-ingress.addon.js

@@ -2,7 +2,7 @@ Object.defineProperties(exports, {
 	__esModule: { value: true },
 	[Symbol.toStringTag]: { value: "Module" }
 });
-const require_dist = require("../dist-CM8irv4g.js");
+const require_dist = require("../dist-C-HpGclR.js");
 let node_crypto = require("node:crypto");
 let node_child_process = require("node:child_process");
 //#region src/ingress/tailscale-cli.ts

package/dist/ingress/tailscale-ingress.addon.mjs

@@ -1,4 +1,4 @@
-import { a as EventCategory, i as BaseAddon, n as networkAccessCapability } from "../dist-BlLzjzzR.mjs";
+import { a as EventCategory, i as BaseAddon, n as networkAccessCapability } from "../dist-CwE5GhC9.mjs";
 import { randomUUID } from "node:crypto";
 import { execFile } from "node:child_process";
 import { promisify } from "node:util";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-tailscale",
-  "version": "1.2.63",
+  "version": "1.2.64",
   "description": "Tailscale bundle for CamStack — joins the host to a tailnet (client) and exposes the hub via Serve/Funnel (ingress). Multi-entry npm package shipping 2 addons under a single bundle.",
   "keywords": [
     "camstack",