@camstack/system 1.2.313 → 1.2.315

package/dist/kernel/transport/local-child-registry.d.ts

@@ -2,6 +2,7 @@ import { IReadinessRegistryRecord, SystemEvent } from '@camstack/types';
 import { CapUsageCallRecord } from '../moleculer/cap-usage-registry.js';
 import { CapActionReading } from './cap-action-census.js';
 import { CapRoutingHints } from './cap-routing-hints.js';
+import { ClaimedStatusResolver } from '../status-overlay.js';
 import { AddonCallInput, CapCallInput, ChildLogMessage, RegisteredChild } from './child-cap-protocol.js';
 import { LocalTransportServer } from './local-transport.js';
 import { SocketTrafficSample } from './socket-traffic.js';
@@ -180,6 +181,26 @@ export interface LocalChildRegistryOptions {
      * performs the routing — a rule implemented twice is a rule that drifts.
      */
     readonly isAddonPinnedCall?: (capName: string, method: string, hints: CapRoutingHints) => boolean;
+    /**
+     * The hub's claim authority for a device-scoped `getStatus` (D663, ruling
+     * S3) — fifth member of the "an explicit intent must win over a co-located
+     * provider" family. A `getStatus` about a device whose cap is CLAIMED is
+     * answered HERE, from the hub mirror's merged slice, before `resolveChildId`
+     * is consulted: the sibling short-circuit would dispatch it straight to the
+     * owning child, whose `getStatus` is the NATIVE slice — an HA-MQTT / HomeKit
+     * exporter or the notification center (hub-local forked children) asking
+     * `battery.getStatus({ deviceId })` of a device owned by the hub-local
+     * `provider-homeassistant` child read the native value while the UI showed
+     * the merged one. The parent's `onUnownedCall` had the same answer, on a path
+     * this call never took. Same shared function (`answerClaimedGetStatus`) as
+     * that handler and the hub's `callCapabilityOnNode`, so the three entries
+     * cannot drift; a device whose claims are not yet known has them resolved
+     * first and is never answered native.
+     *
+     * Omitted (the agent has no claim authority) ⇒ prior behaviour exactly. The
+     * kernel has no cap registry, so the wiring side injects it.
+     */
+    readonly claimedStatus?: ClaimedStatusResolver;
     /**
      * Per-cap-method bound for UDS cap calls, in ms — read from the cap
      * definition's declared `timeoutMs`. The SAME resolver the remote plane uses
@@ -274,6 +295,8 @@ export declare class LocalChildRegistry {
     private readonly actionCensus;
     /** See {@link LocalChildRegistryOptions.capTimeoutMs}. */
     private readonly capTimeoutMs?;
+    /** See {@link LocalChildRegistryOptions.claimedStatus}. */
+    private readonly claimedStatus?;
     /** See {@link LocalChildRegistryOptions.capUsageObserver}. */
     private readonly capUsageObserver?;
     /** Tracks capNames already logged as UDS-routed; one INFO line per capName per process. */

package/dist/kernel/transport/parent-unowned-call.d.ts

@@ -1,6 +1,7 @@
 import { CapCallInput } from './child-cap-protocol.js';
 import { CapRouteResolver, HubLocalChildDispatcher } from './cap-route-resolver.js';
 import { HubNodeRegistry } from '../moleculer/node-registry.js';
+import { ClaimedStatusResolver } from '../status-overlay.js';
 import { ServiceBroker } from 'moleculer';
 /**
  * Minimal logger surface accepted by the unowned-call handler. Matches the
@@ -202,6 +203,30 @@ export interface ParentUnownedCallDeps {
      * rejected (no forwarder) — never silently downgraded to wrapper routing.
      */
     readonly resolveNative?: (capName: string, deviceId: number) => Record<string, (input: unknown) => Promise<unknown>> | null;
+    /**
+     * The hub's claim authority for a device-scoped `getStatus` (D663, ruling
+     * S3). Wired to `CapabilityRegistry.resolveClaimedStatus` — the SAME question
+     * the registry's own wrappers and the other two transport entries ask, through
+     * the one shared `answerClaimedGetStatus` (`claimed-get-status.ts`).
+     *
+     * Why here: every capName-based route below dispatches STRAIGHT to the owning
+     * runner (`hub-local-uds`, `remote-moleculer`), whose `getStatus` answers the
+     * NATIVE slice. This handler is the entry for a call no co-resident sibling
+     * owns (a remote agent's device, a hub-in-process cap, the agent's forward);
+     * the sibling short-circuit in `LocalChildRegistry` and the hub's
+     * `callCapabilityOnNode` are the other two, and each asks first. When the
+     * answer is `claimed` the merged slice IS the answer (`null` for a held claim,
+     * and for a device whose claims cannot be known) and the resolver is never
+     * consulted; a node pin does not bypass it — the hub is the one claim
+     * authority wherever the device runs. `unclaimed` routes exactly as before.
+     *
+     * Omitted (the agent has no claim authority; its handler forwards to the hub
+     * for hub-hosted caps, which answer through THIS hook on the hub) ⇒ legacy
+     * routing exactly. Known gap: an agent-resident child calling `getStatus` of
+     * an agent-resident device is answered by the agent's local dispatcher with
+     * no hub round-trip, so a claim is not honoured there (D663 open item).
+     */
+    readonly claimedStatus?: ClaimedStatusResolver;
     /** Optional logger for the broker-fallback diagnostic line. */
     readonly logger?: ParentUnownedCallLogger;
 }

package/dist/{retired-settings-keys-C1duPikd.mjs → retired-settings-keys-8yY2sTc-.mjs}

@@ -1,4 +1,4 @@
-import { Vn as asJsonObject } from "./dist-Cj7pJmXq.mjs";
+import { Qn as asJsonObject } from "./dist-MzYJVCLE.mjs";
 //#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-CGSuXhP8.js → retired-settings-keys-iY5I0nKM.js}

@@ -1,4 +1,4 @@
-const require_dist = require("./dist-CkRwnhbo.js");
+const require_dist = require("./dist-DVKv5i-e.js");
 //#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.313",
+  "version": "1.2.315",
   "description": "Core addon for CamStack — builtins, pipeline, process management, auth, logging, events",
   "keywords": [
     "camstack",