@danypops/vehicle-core 0.19.1 → 0.19.2

package/dist/approvals/approval.d.ts

@@ -1,6 +1,6 @@
 import type { VehiclePrincipal } from "../operations/context.js";
 import type { VehicleEffect } from "../operations/effect.js";
-/** Set once at registry-configuration time (VehicleRegistry.configureApprovals()); never on a per-invoke basis. */
+/** Secure default applied when a registry configures approvals and when an unconfigured registry diagnoses risky operations. */
 export declare const DEFAULT_APPROVAL_EFFECTS: readonly VehicleEffect[];
 /**
  * The name VehicleRegistry.configureApprovals() registers its built-in

package/dist/approvals/approval.js

@@ -24,8 +24,8 @@ function isVehiclePrincipal(value) {
         return true;
     return typeof candidate["claims"] === "object" && candidate["claims"] !== null && !Array.isArray(candidate["claims"]);
 }
-/** Set once at registry-configuration time (VehicleRegistry.configureApprovals()); never on a per-invoke basis. */
-export const DEFAULT_APPROVAL_EFFECTS = ["destructive", "open-world"];
+/** Secure default applied when a registry configures approvals and when an unconfigured registry diagnoses risky operations. */
+export const DEFAULT_APPROVAL_EFFECTS = ["destructive", "open-world", "external-write"];
 /**
  * The name VehicleRegistry.configureApprovals() registers its built-in
  * grant/deny operation under. Shared so vehicle-client-pi can recognize and

package/dist/manifest/manifest.d.ts

@@ -1,4 +1,5 @@
 import type { VehicleManifestEvent } from "../events/event.js";
+import type { VehicleEffect } from "../operations/effect.js";
 import type { VehicleOperationDescriptor } from "../operations/operation.js";
 import type { VehicleProtocolSupport } from "../protocol/negotiation.js";
 export interface VehicleManifestIdentity {
@@ -25,8 +26,9 @@ export interface VehicleManifestOperation extends VehicleOperationDescriptor {
      * The registry's own, live, fully-resolved answer to "does invoking this operation right
      * now require approval" -- accounts for the registry's current approval policy being
      * enabled/disabled, this operation's own `requiresApproval` override when set, and the
-     * effect-derived default otherwise. A real VehicleRegistry.manifest() always sets this
-     * (false when the registry never called configureApprovals() at all) -- unlike
+     * effect-derived default otherwise. A real VehicleRegistry.manifest() always sets this;
+     * before configureApprovals(), risky operations report true and fail closed while the
+     * manifest's approvalPolicy diagnostic identifies the missing explicit decision. Unlike
      * `requiresApproval` (the static, author-declared override on the descriptor itself),
      * this always reflects the current instant, so a client re-fetching the manifest after a
      * live policy change (VehicleRegistry.updateApprovalPolicy) sees the new answer with no
@@ -40,13 +42,19 @@ export interface VehicleManifestOperation extends VehicleOperationDescriptor {
      */
     readonly approvalRequired?: boolean;
 }
+/** Reports whether a registry made an explicit approval-policy decision and names risky operations that still need one. */
+export interface VehicleManifestApprovalPolicy {
+    readonly status: "unconfigured" | "enabled" | "disabled";
+    readonly requireApprovalForEffects: readonly VehicleEffect[];
+    readonly unconfiguredRiskyOperations: readonly string[];
+}
 /**
- * `events` is optional purely for backward compatibility with every
- * hand-authored VehicleManifest test fixture across the ecosystem that
- * predates this field -- a real VehicleRegistry.manifest() always
- * populates it (as [] when no events are declared), never omits it.
+ * `events` and `approvalPolicy` are optional for backward compatibility with
+ * hand-authored and older manifests. A current VehicleRegistry always emits
+ * both fields.
  */
 export interface VehicleManifest extends VehicleManifestIdentity {
     readonly operations: readonly VehicleManifestOperation[];
     readonly events?: readonly VehicleManifestEvent[];
+    readonly approvalPolicy?: VehicleManifestApprovalPolicy;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@danypops/vehicle-core",
-	"version": "0.19.1",
+	"version": "0.19.2",
 	"description": "Vehicle's runtime-neutral wire contract: operation descriptors, schema codecs, failure shapes. Zero runtime dependencies, zero Bun-specific code -- the one thing every Vehicle client and server package depends on.",
 	"license": "MIT",
 	"type": "module",

package/src/approvals/approval.ts

@@ -27,8 +27,8 @@ function isVehiclePrincipal(value: unknown): value is VehiclePrincipal {
 	return typeof candidate["claims"] === "object" && candidate["claims"] !== null && !Array.isArray(candidate["claims"]);
 }
 
-/** Set once at registry-configuration time (VehicleRegistry.configureApprovals()); never on a per-invoke basis. */
-export const DEFAULT_APPROVAL_EFFECTS: readonly VehicleEffect[] = ["destructive", "open-world"];
+/** Secure default applied when a registry configures approvals and when an unconfigured registry diagnoses risky operations. */
+export const DEFAULT_APPROVAL_EFFECTS: readonly VehicleEffect[] = ["destructive", "open-world", "external-write"];
 
 /**
  * The name VehicleRegistry.configureApprovals() registers its built-in

package/src/manifest/manifest.ts

@@ -1,4 +1,5 @@
 import type { VehicleManifestEvent } from "../events/event.js";
+import type { VehicleEffect } from "../operations/effect.js";
 import type { VehicleOperationDescriptor } from "../operations/operation.js";
 import type { VehicleProtocolSupport } from "../protocol/negotiation.js";
 
@@ -27,8 +28,9 @@ export interface VehicleManifestOperation extends VehicleOperationDescriptor {
 	 * The registry's own, live, fully-resolved answer to "does invoking this operation right
 	 * now require approval" -- accounts for the registry's current approval policy being
 	 * enabled/disabled, this operation's own `requiresApproval` override when set, and the
-	 * effect-derived default otherwise. A real VehicleRegistry.manifest() always sets this
-	 * (false when the registry never called configureApprovals() at all) -- unlike
+	 * effect-derived default otherwise. A real VehicleRegistry.manifest() always sets this;
+	 * before configureApprovals(), risky operations report true and fail closed while the
+	 * manifest's approvalPolicy diagnostic identifies the missing explicit decision. Unlike
 	 * `requiresApproval` (the static, author-declared override on the descriptor itself),
 	 * this always reflects the current instant, so a client re-fetching the manifest after a
 	 * live policy change (VehicleRegistry.updateApprovalPolicy) sees the new answer with no
@@ -43,13 +45,20 @@ export interface VehicleManifestOperation extends VehicleOperationDescriptor {
 	readonly approvalRequired?: boolean;
 }
 
+/** Reports whether a registry made an explicit approval-policy decision and names risky operations that still need one. */
+export interface VehicleManifestApprovalPolicy {
+	readonly status: "unconfigured" | "enabled" | "disabled";
+	readonly requireApprovalForEffects: readonly VehicleEffect[];
+	readonly unconfiguredRiskyOperations: readonly string[];
+}
+
 /**
- * `events` is optional purely for backward compatibility with every
- * hand-authored VehicleManifest test fixture across the ecosystem that
- * predates this field -- a real VehicleRegistry.manifest() always
- * populates it (as [] when no events are declared), never omits it.
+ * `events` and `approvalPolicy` are optional for backward compatibility with
+ * hand-authored and older manifests. A current VehicleRegistry always emits
+ * both fields.
  */
 export interface VehicleManifest extends VehicleManifestIdentity {
 	readonly operations: readonly VehicleManifestOperation[];
 	readonly events?: readonly VehicleManifestEvent[];
+	readonly approvalPolicy?: VehicleManifestApprovalPolicy;
 }