wire-mesh-core 3.0.0 → 3.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -13,7 +13,7 @@ export declare function buildCapabilityGrantCommand(capability: string, grantedT
|
|
|
13
13
|
*
|
|
14
14
|
* scope and targetDevice forward directly to MeshSession.sendManageRequest's own identically-named parameters (the request's own top-level scope obligation 4 checks the token against, and relay routing respectively).
|
|
15
15
|
*/
|
|
16
|
-
export declare function sendCapabilityGrant(session: Readonly<MeshSession
|
|
16
|
+
export declare function sendCapabilityGrant(session: Readonly<Pick<MeshSession, "sendManageRequest">>, capability: string, grantedToken: CapabilityToken, scope: Readonly<CapabilityScope>, targetDevice?: DeviceId): Promise<ManageOutcome>;
|
|
17
17
|
/** One incoming, fully-verified capability-grant, surfaced for the domain to react to (store the token, notify a human, etc.) -- there is no decide() here because management.cddl specifies no protocol-level approval round trip for this primitive; by the time onGrant fires, the wire response has already been sent. */
|
|
18
18
|
export interface CapabilityGrantEvent {
|
|
19
19
|
/** The capability granted -- equals both the outer manage-command.verb and the verified token's own capability claim (obligation 2 already enforced this before onGrant fires). */
|
|
@@ -13,7 +13,7 @@ export declare function buildCapabilityGrantCommand(capability: string, grantedT
|
|
|
13
13
|
*
|
|
14
14
|
* scope and targetDevice forward directly to MeshSession.sendManageRequest's own identically-named parameters (the request's own top-level scope obligation 4 checks the token against, and relay routing respectively).
|
|
15
15
|
*/
|
|
16
|
-
export declare function sendCapabilityGrant(session: Readonly<MeshSession
|
|
16
|
+
export declare function sendCapabilityGrant(session: Readonly<Pick<MeshSession, "sendManageRequest">>, capability: string, grantedToken: CapabilityToken, scope: Readonly<CapabilityScope>, targetDevice?: DeviceId): Promise<ManageOutcome>;
|
|
17
17
|
/** One incoming, fully-verified capability-grant, surfaced for the domain to react to (store the token, notify a human, etc.) -- there is no decide() here because management.cddl specifies no protocol-level approval round trip for this primitive; by the time onGrant fires, the wire response has already been sent. */
|
|
18
18
|
export interface CapabilityGrantEvent {
|
|
19
19
|
/** The capability granted -- equals both the outer manage-command.verb and the verified token's own capability claim (obligation 2 already enforced this before onGrant fires). */
|
|
@@ -12,7 +12,7 @@ export declare function buildCapabilityRequestCommand(capability: string, validU
|
|
|
12
12
|
*
|
|
13
13
|
* targetDevice and timeoutMs forward directly to MeshSession.sendManageRequest's own identically-named parameters (relay routing and a requester-side give-up bound respectively -- wire-mesh#80 is already implemented there, not duplicated here). validUntil, when given, is attached to the request itself (wire-mesh#82) so a slow-to-answer receiver -- or a relay/facilitator forwarding this request on the caller's behalf -- can refuse or drop a now-stale ask outright rather than holding or forwarding it.
|
|
14
14
|
*/
|
|
15
|
-
export declare function requestCapability(session: Readonly<MeshSession
|
|
15
|
+
export declare function requestCapability(session: Readonly<Pick<MeshSession, "sendManageRequest">>, capability: string, scope: Readonly<CapabilityScope>, targetDevice?: DeviceId, timeoutMs?: number, validUntil?: number): Promise<CapabilityGrantOk>;
|
|
16
16
|
/**
|
|
17
17
|
* A receiver's decision on one incoming capability-request, mirroring room-client.ts's own (now capability-specific) RoomJoinDecision, generalized to any capability: "accept" mints and returns a fresh token; "reject" sends an ordinary manage-error carrying an optional human-readable reason.
|
|
18
18
|
*/
|
|
@@ -12,7 +12,7 @@ export declare function buildCapabilityRequestCommand(capability: string, validU
|
|
|
12
12
|
*
|
|
13
13
|
* targetDevice and timeoutMs forward directly to MeshSession.sendManageRequest's own identically-named parameters (relay routing and a requester-side give-up bound respectively -- wire-mesh#80 is already implemented there, not duplicated here). validUntil, when given, is attached to the request itself (wire-mesh#82) so a slow-to-answer receiver -- or a relay/facilitator forwarding this request on the caller's behalf -- can refuse or drop a now-stale ask outright rather than holding or forwarding it.
|
|
14
14
|
*/
|
|
15
|
-
export declare function requestCapability(session: Readonly<MeshSession
|
|
15
|
+
export declare function requestCapability(session: Readonly<Pick<MeshSession, "sendManageRequest">>, capability: string, scope: Readonly<CapabilityScope>, targetDevice?: DeviceId, timeoutMs?: number, validUntil?: number): Promise<CapabilityGrantOk>;
|
|
16
16
|
/**
|
|
17
17
|
* A receiver's decision on one incoming capability-request, mirroring room-client.ts's own (now capability-specific) RoomJoinDecision, generalized to any capability: "accept" mints and returns a fresh token; "reject" sends an ordinary manage-error carrying an optional human-readable reason.
|
|
18
18
|
*/
|