@danypops/vehicle-core 0.18.6 → 0.19.0

package/dist/approvals/approval.d.ts

@@ -13,6 +13,20 @@ export declare const DEFAULT_APPROVAL_EFFECTS: readonly VehicleEffect[];
  * loop point of the gate entirely.
  */
 export declare const VEHICLE_APPROVAL_RESOLVE_OPERATION_NAME = "vehicle.approval.resolve";
+/**
+ * The name VehicleRegistry.configureApprovals() registers its own read-only status-lookup
+ * operation under. Unlike vehicle.approval.resolve, this one is deliberately left projectable
+ * as an ordinary Pi/model-callable tool: reading a requestId's own already-made decision (who
+ * decided, when, and any comment) can never let a caller grant its own pending request -- it
+ * only ever surfaces a decision a human (or other authority) already recorded. Exists because a
+ * gated invoke()'s own local HITL prompt and the eventual human decision can genuinely happen on
+ * two different calls (a caller-side timeout, a UI presented asynchronously outside the
+ * originating call's own lifetime, a session restart in between) -- without this, a decision
+ * (and any comment explaining it) made after the originating call already gave up is
+ * unrecoverable, since vehicle.approval.resolve's own vehicleApprovalResolvedEvent is transient
+ * pub/sub with no replay for a caller that wasn't subscribed at that exact moment.
+ */
+export declare const VEHICLE_APPROVAL_STATUS_OPERATION_NAME = "vehicle.approval.status";
 /** How long a request stays resolvable before it lapses and must be re-requested. */
 export declare const DEFAULT_APPROVAL_TIMEOUT_MS: number;
 /** Emitted (as a Vehicle Event) the moment a gated-effect invoke() has no valid capability -- durable-first, before any interactive prompt is attempted. */

package/dist/approvals/approval.js

@@ -37,6 +37,20 @@ export const DEFAULT_APPROVAL_EFFECTS = ["destructive", "open-world"];
  * loop point of the gate entirely.
  */
 export const VEHICLE_APPROVAL_RESOLVE_OPERATION_NAME = "vehicle.approval.resolve";
+/**
+ * The name VehicleRegistry.configureApprovals() registers its own read-only status-lookup
+ * operation under. Unlike vehicle.approval.resolve, this one is deliberately left projectable
+ * as an ordinary Pi/model-callable tool: reading a requestId's own already-made decision (who
+ * decided, when, and any comment) can never let a caller grant its own pending request -- it
+ * only ever surfaces a decision a human (or other authority) already recorded. Exists because a
+ * gated invoke()'s own local HITL prompt and the eventual human decision can genuinely happen on
+ * two different calls (a caller-side timeout, a UI presented asynchronously outside the
+ * originating call's own lifetime, a session restart in between) -- without this, a decision
+ * (and any comment explaining it) made after the originating call already gave up is
+ * unrecoverable, since vehicle.approval.resolve's own vehicleApprovalResolvedEvent is transient
+ * pub/sub with no replay for a caller that wasn't subscribed at that exact moment.
+ */
+export const VEHICLE_APPROVAL_STATUS_OPERATION_NAME = "vehicle.approval.status";
 /** How long a request stays resolvable before it lapses and must be re-requested. */
 export const DEFAULT_APPROVAL_TIMEOUT_MS = 5 * 60_000;
 const requestedPayloadSchema = defineVehicleSchema({

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@danypops/vehicle-core",
-	"version": "0.18.6",
+	"version": "0.19.0",
 	"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

@@ -42,6 +42,21 @@ export const DEFAULT_APPROVAL_EFFECTS: readonly VehicleEffect[] = ["destructive"
  */
 export const VEHICLE_APPROVAL_RESOLVE_OPERATION_NAME = "vehicle.approval.resolve";
 
+/**
+ * The name VehicleRegistry.configureApprovals() registers its own read-only status-lookup
+ * operation under. Unlike vehicle.approval.resolve, this one is deliberately left projectable
+ * as an ordinary Pi/model-callable tool: reading a requestId's own already-made decision (who
+ * decided, when, and any comment) can never let a caller grant its own pending request -- it
+ * only ever surfaces a decision a human (or other authority) already recorded. Exists because a
+ * gated invoke()'s own local HITL prompt and the eventual human decision can genuinely happen on
+ * two different calls (a caller-side timeout, a UI presented asynchronously outside the
+ * originating call's own lifetime, a session restart in between) -- without this, a decision
+ * (and any comment explaining it) made after the originating call already gave up is
+ * unrecoverable, since vehicle.approval.resolve's own vehicleApprovalResolvedEvent is transient
+ * pub/sub with no replay for a caller that wasn't subscribed at that exact moment.
+ */
+export const VEHICLE_APPROVAL_STATUS_OPERATION_NAME = "vehicle.approval.status";
+
 /** How long a request stays resolvable before it lapses and must be re-requested. */
 export const DEFAULT_APPROVAL_TIMEOUT_MS = 5 * 60_000;