@vess-id/ai-identity 0.16.0 → 0.17.0

package/dist/registry/__tests__/action-registry-freebusy.spec.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Tests for the calendar.freebusy action in ACTION_REGISTRY.
+ *
+ * calendar.freebusy is a read-only availability probe used to check whether a
+ * calendar is busy over a time window before proposing meeting slots. It never
+ * returns event details (only busy/free intervals), so it stays in the
+ * low-risk `calendar.read.basic` capability alongside calendar.event.list /
+ * calendar.event.read.
+ *
+ * Spec: docs/specs/2026-07-03-scheduling-wow-phase1-design.md §4.1
+ */
+export {};
+//# sourceMappingURL=action-registry-freebusy.spec.d.ts.map

package/dist/registry/__tests__/action-registry-freebusy.spec.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"action-registry-freebusy.spec.d.ts","sourceRoot":"","sources":["../../../src/registry/__tests__/action-registry-freebusy.spec.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG"}

package/dist/registry/__tests__/high-risk-resource-binding-invariant.spec.d.ts

@@ -0,0 +1,30 @@
+/**
+ * Registry invariant — every HIGH-risk action must have a RESOLVABLE
+ * resource_id binding (#883 class-killer).
+ *
+ * Why this exists (2026-07-04): Gate-2 enforcement
+ * (`ToolExecutorService.validateVCResourceConstraint`, strict for high risk
+ * post-#886) fail-closes any high-risk invocation whose runtime resource
+ * cannot be canonicalized (`RESOURCE_UNRESOLVED`) — and issuance pins VC
+ * delegates through the SAME function (`canonicalResourceId`, INV-1). An
+ * action that is high-risk but has no resolvable binding is therefore
+ * IMPOSSIBLE to execute end-to-end: approval succeeds, the VC is pinned, and
+ * the invoke still dies at Gate-2. That failure mode shipped at least twice
+ * (#883 github write actions; g7.6/7.7/7.13 gmail.message.send unpinned
+ * permit-path issuance). This spec turns the class into a test failure at the
+ * moment the registry entry is added.
+ *
+ * Contract per high-risk action:
+ *   (a) `canonicalResourceId(action, <schema-faithful params>)` resolves to a
+ *       non-empty string — i.e. the binding exists AND its param(s) actually
+ *       exist in the action's input_schema (a binding pointing at a param the
+ *       schema doesn't carry can never resolve at runtime), OR
+ *   (b) the action is on the explicit allowlist below, each entry justified.
+ *
+ * Adding a high-risk action? Give it `target_bindings.resource_id` bound to a
+ * param that exists in `input_schema.properties` (for CREATE actions: the
+ * container/parent that exists pre-execution — see the registry header
+ * comment), or consciously extend the allowlist with a justification.
+ */
+export {};
+//# sourceMappingURL=high-risk-resource-binding-invariant.spec.d.ts.map

package/dist/registry/__tests__/high-risk-resource-binding-invariant.spec.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"high-risk-resource-binding-invariant.spec.d.ts","sourceRoot":"","sources":["../../../src/registry/__tests__/high-risk-resource-binding-invariant.spec.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG"}