@camstack/addon-advanced-notifier 0.1.25 → 0.1.26

package/dist/addon.js

@@ -8499,10 +8499,30 @@ const StatusSchema = object({
   }
 });
 const LinkStateSchema = _enum(["unlinked", "linked", "error"]);
+const ExportSetupFieldSchema = object({
+  label: string(),
+  value: string(),
+  /** Mask the value by default + render a reveal toggle (client id, secrets). */
+  secret: boolean().optional()
+});
+const ExportSetupSchema = object({
+  /** A string to render as a scannable QR — HAP `X-HM://…` URI, a pairing URL, etc. Omitted when there's nothing to scan. */
+  qr: string().optional(),
+  /** Label/value rows shown with a copy button (HAP setup code, OAuth URLs, client id, linked-account count, …). */
+  fields: array(ExportSetupFieldSchema).readonly().optional(),
+  /** Free-form operator instructions rendered above the fields. */
+  note: string().optional()
+});
 const DeviceExportStatusSchema = object({
   linkState: LinkStateSchema,
   exposedDeviceCount: number(),
-  error: string().optional()
+  error: string().optional(),
+  /**
+   * Optional pairing/account info the panel renders in a generic
+   * "Setup" section. Addon-agnostic — the addon id identifies the
+   * export target, never an `ecosystem` key here.
+   */
+  setup: ExportSetupSchema.optional()
 });
 const DeviceKindSchema = string();
 const ExposedDeviceSchema = object({
@@ -11935,7 +11955,25 @@ const MeshStatusSchema = object({
    * doesn't rotate keys for the bound host. Operator-facing surface
    * for "your access expires on …" banners.
    */
-  keyExpiry: number().nullable()
+  keyExpiry: number().nullable(),
+  // ── Onboard-daemon handoff (Tailscale, generic slot) ────────────
+  /**
+   * When the provider runs its OWN mesh daemon (e.g. the Tailscale
+   * client addon in `onboard` mode spawns a private `tailscaled`),
+   * this carries the local control-socket path. Companion addons that
+   * must drive the SAME daemon — chiefly `tailscale-ingress` for
+   * Serve/Funnel — read it to point their CLI at the right socket
+   * instead of the system default. Empty when the provider uses the
+   * host's system daemon (or doesn't have the concept).
+   */
+  daemonSocket: string().optional(),
+  /**
+   * Path to the mesh CLI binary the provider downloaded for onboard
+   * mode. Companion addons reuse it so they don't need a system
+   * install when the operator chose a fully self-contained mesh.
+   * Empty in host mode.
+   */
+  daemonCliPath: string().optional()
 });
 ({
   methods: {
@@ -12821,6 +12859,21 @@ const AddonAutoUpdateSchema = ChannelWithInheritSchema;
 const RestartAddonResultSchema = unknown();
 const InstallPackageResultSchema = unknown();
 const ReloadPackagesResultSchema = unknown();
+const UpdateFrameworkPackageResultSchema = object({
+  packageName: string(),
+  fromVersion: string(),
+  toVersion: string(),
+  /** Ms-epoch the server scheduled its self-restart. */
+  restartingAt: number()
+});
+const FrameworkPackageStatusSchema = object({
+  packageName: string(),
+  currentVersion: string(),
+  latestVersion: string().nullable(),
+  hasUpdate: boolean(),
+  /** Optional manifest description for the row tooltip. */
+  description: string().optional()
+});
 const LogStreamEntrySchema = object({
   timestamp: string(),
   level: string(),
@@ -12880,13 +12933,29 @@ const CustomActionInputSchema = object({
       object({ query: string().optional() }),
       array(SearchResultSchema)
     ),
+    /**
+     * Available package updates for a node. `nodeId` omitted (or
+     * `'hub'`) checks the hub's own installed packages; an agent
+     * `nodeId` checks that agent's installed roster against npm
+     * (the hub does the npm lookups + diff — agents stay npm-free).
+     */
     listUpdates: method(
-      _void(),
+      object({ nodeId: string().optional() }),
       array(PackageUpdateSchema).readonly(),
       { auth: "admin" }
     ),
+    /**
+     * Update one package on a node. `nodeId` omitted (or `'hub'`)
+     * installs on the hub via npm; an agent `nodeId` makes the hub
+     * pack the resolved version and push the tarball to that agent
+     * (`$agent.deploy` + `$agent.reload`) — agents need no npm runtime.
+     */
     updatePackage: method(
-      object({ name: string().min(1), version: string().optional() }),
+      object({
+        name: string().min(1),
+        version: string().optional(),
+        nodeId: string().optional()
+      }),
       unknown(),
       { kind: "mutation", auth: "admin" }
     ),
@@ -12907,12 +12976,105 @@ const CustomActionInputSchema = object({
       object({ rolledBackTo: string().nullable() }),
       { kind: "mutation", auth: "admin" }
     ),
-    forceRefresh: method(_void(), unknown(), { kind: "mutation", auth: "admin" }),
+    /** Re-check updates for a node, bypassing any cache. `nodeId`
+     *  omitted (or `'hub'`) refreshes the hub; an agent `nodeId`
+     *  re-checks that agent's roster. */
+    forceRefresh: method(
+      object({ nodeId: string().optional() }),
+      unknown(),
+      { kind: "mutation", auth: "admin" }
+    ),
     restartServer: method(
       object({ confirm: literal(true) }),
       unknown(),
       { kind: "mutation", auth: "admin" }
     ),
+    /**
+     * Most-recent restart marker (kind / packageName / from→to versions
+     * / requestedBy / requestedAt). Returns `null` when this process
+     * didn't boot from a tracked restart, or when the
+     * post-boot retention window (5 min) has elapsed.
+     *
+     * Drives the admin-UI reconnect overlay's success toast — the
+     * `system.restart-completed` event itself is fired before the
+     * client has time to re-subscribe, so the client queries this on
+     * first reconnect instead.
+     */
+    getLastRestart: method(
+      _void(),
+      object({
+        kind: _enum(["framework-update", "manual", "system"]),
+        packageName: string().optional(),
+        fromVersion: string().optional(),
+        toVersion: string().optional(),
+        requestedBy: string().optional(),
+        requestedAt: number()
+      }).nullable(),
+      { auth: "admin" }
+    ),
+    /**
+     * Snapshot of the framework packages installed under the hub's
+     * `<appRoot>/node_modules/`. Each row carries the currently
+     * installed version and (best-effort) the latest version
+     * available on npm. Drives the admin-UI "System packages" panel.
+     *
+     * Spec: docs/superpowers/specs/2026-05-14-framework-live-update-design.md
+     */
+    listFrameworkPackages: method(
+      _void(),
+      array(FrameworkPackageStatusSchema).readonly(),
+      { auth: "admin" }
+    ),
+    /**
+     * Cluster-wide capability-provider discovery. Returns the list of
+     * `{ addonId, mode, isActive }` tuples for whatever addon(s)
+     * currently provide the requested capability across the cluster.
+     *
+     * Why this lives on `addons` (and not on a `capabilities` cap of
+     * its own): the hub's main-process `CapabilityRegistry` already
+     * aggregates registrations from every forked group-runner and
+     * remote agent via Moleculer event propagation — there's no
+     * cross-process registry mirror to build, just an introspection
+     * shim.
+     *
+     * Use this from addon code when you need to know whether another
+     * addon has registered a specific cap (e.g. `tailscale-ingress`
+     * checking `tailscale-client` is up before calling `tailscale
+     * serve`). Don't reach for `ctx.capabilities.getCollectionEntries`
+     * — that reads the LOCAL registry of the calling addon's group
+     * runner and never sees providers in other processes. See
+     * `CLAUDE.md` → Critical rules → ctx.api vs ctx.capabilities.
+     */
+    listCapabilityProviders: method(
+      object({ capName: string().min(1) }),
+      array(object({
+        addonId: string(),
+        mode: _enum(["singleton", "collection"]),
+        isActive: boolean()
+      })).readonly()
+    ),
+    /**
+     * Live-update one of the framework packages marked
+     * `camstack.system: true` (`@camstack/types|kernel|core|sdk|ui-library`).
+     * Runs `npm install --prefix <appRoot> <name>@<version> --no-save`,
+     * writes a `.restart-pending` marker, emits `system.restarting`
+     * and schedules a graceful process exit. The supervisor (Docker /
+     * Electron / systemd) brings the hub back up; on first boot after
+     * the restart the marker fires `system.restart-completed`.
+     *
+     * `version` defaults to `'latest'`. The allow-list of valid
+     * `packageName` values is enforced server-side.
+     *
+     * Spec: docs/superpowers/specs/2026-05-14-framework-live-update-design.md
+     */
+    updateFrameworkPackage: method(
+      object({
+        packageName: string().min(1),
+        version: string().optional()
+      }),
+      UpdateFrameworkPackageResultSchema,
+      { kind: "mutation", auth: "admin" }
+    ),
     getVersions: method(
       object({ name: string() }),
       array(PackageVersionInfoSchema).readonly()
@@ -12983,6 +13145,7 @@ var EventCategory = /* @__PURE__ */ ((EventCategory2) => {
   EventCategory2["SystemBoot"] = "system.boot";
   EventCategory2["SystemAddonsReady"] = "system.addons-ready";
   EventCategory2["SystemRestarting"] = "system.restarting";
+  EventCategory2["SystemRestartCompleted"] = "system.restart-completed";
   EventCategory2["SystemReadyState"] = "system.ready-state";
   EventCategory2["AddonStarted"] = "addon.started";
   EventCategory2["AddonStopped"] = "addon.stopped";