slotlock 0.2.0 → 0.5.0

package/agent-store-backend.d.ts

@@ -17,6 +17,12 @@ export interface SlotlockStoreAgentBackendOptions {
  * writes events through the store itself and shows them to agents beside the tools' own results.
  */
 export declare function projectSlotlockCalendarEvent(event: SlotlockCalendarEvent): Record<string, unknown>;
+/**
+ * The HTTP status a store refusal answers with on every agent surface: a missing or foreign
+ * record 404, a malformed request 400, a full agent quota 429, and any other conflict with what is
+ * stored 409. rest-api.ts declares the 404 and 409 each route can answer from this.
+ */
+export declare function slotlockAgentErrorStatus(code: string): 400 | 404 | 409 | 429;
 /** Bind the protocol server to the production store without giving a request control of tenancy. */
 export declare function createSlotlockStoreAgentBackend(store: SlotlockStore, options: SlotlockStoreAgentBackendOptions): SlotlockAgentCalendarBackend;
 export interface SlotlockStoreApplicationBackendOptions {
@@ -27,6 +33,12 @@ export interface SlotlockStoreApplicationBackendOptions {
     maxTenantResources?: number;
     /** Batches of each maintenance task one `slotlock_run_maintenance` call runs, 1-100 (default 10). */
     maintenanceBatches?: number;
+    /**
+     * Let an admin key erase its own tenant (`slotlock_erase_tenant`), everything it has and every
+     * key it holds, with its tenant reference as confirmation. Off unless true: erasure cannot be
+     * undone, and an operator may owe a tenant's data a retention or review first.
+     */
+    tenantErasure?: boolean;
 }
 /**
  * Serve the application API (application-api.ts) from the production store, in the principal's