@cursor/july 0.1.75 → 0.1.78

package/src/storage.ts

@@ -7,9 +7,8 @@
  * only, and eval/A/B history stays in process memory.
  *
  * The sink is a plain key-value store — put/get/delete/list, no schema —
- * plus a conditional-write group ({@link StorageConfig.cas}, the substrate
- * for framework coordination; optional for plain storage, required by
- * coordination features). Implementing that small KV core is enough for
+ * plus a conditional-write group ({@link StorageConfig.cas}; optional).
+ * Implementing that small KV core is enough for
  * FULL functionality: eval-run and A/B history are derived over the core
  * when the optional dedicated tables ({@link StorageConfig.evals} and
  * {@link StorageConfig.abs}) are not authored — those groups exist as
@@ -178,10 +177,7 @@ export interface StorageABTable {
 /**
  * Conditional writes (CAS) — the coordination tier of the storage backend
  * contract. Plain storage works without it, so existing backends keep
- * working across a platform upgrade; framework coordination (the upcoming
- * session ledger — see `@cursor/july/kv` for the backend-agnostic
- * interface) requires it and fails at startup, with an actionable
- * message, when the backend lacks it. The built-in backends all include
+ * working across a platform upgrade. The built-in backends all include
  * it, so implementing this group yourself only comes up for BYO storage.
  *
  * Grouped under {@link StorageConfig.cas} rather than as loose methods —
@@ -243,10 +239,8 @@ export interface StorageConfig {
   abs?: StorageABTable;
   /**
    * Conditional writes (CAS). Optional for plain storage — existing
-   * backends keep working without it — but required by coordination
-   * features (the session ledger), which fail fast when it is absent.
-   * The built-in backends (`fileKv`, `cursorHostedStorage`) both include
-   * it. See {@link StorageCasTable}.
+   * backends keep working without it. The built-in backends (`fileKv`,
+   * `cursorHostedStorage`) both include it. See {@link StorageCasTable}.
    */
   cas?: StorageCasTable;
   /**
@@ -321,7 +315,7 @@ export function defineStorage(config: StorageConfig): StorageDefinition {
     ] as const;
     const cas = config.cas;
     // A partial group is a bug, not a legacy config: half-implemented CAS
-    // would pass the capability probe and corrupt coordination.
+    // would pass the capability probe.
     const missingCasHooks = casHooks.filter(
       (hook) => typeof cas[hook] !== "function"
     );

package/src/types.ts

@@ -240,31 +240,8 @@ export interface AgentConfig {
    * it only shapes what the model can call.
    */
   tools?: ToolName[];
-  /**
-   * How the serve host coordinates event delivery and turn execution. See
-   * {@link AgentServingMode}. Defaults to `"resident"`; opt in to
-   * `"ledger"` per agent — rollback is flipping the value back.
-   */
-  serving?: AgentServingMode;
 }
 
-/**
- * Serving coordination mode on {@link AgentConfig.serving}.
- *
- * - `"resident"` (default): the in-process session engine owns delivery —
- *   today's behavior, unchanged.
- * - `"ledger"`: every delivery coordinates through the KV session ledger
- *   before its turn runs: session identity, a one-writer-per-session
- *   lease with generation fencing, and a fenced commit sequence.
- *   Requires a store with conditional writes (the `cas` group on
- *   `defineStorage`, or an explicit CAS-capable override); startup fails
- *   fast otherwise. This stage is coordination only — there is no
- *   durable inbox yet, so an event arriving while the lease is held
- *   waits in-process and a crash loses it exactly as resident serving
- *   does. The durable mailbox lands in a follow-up.
- */
-export type AgentServingMode = "resident" | "ledger";
-
 /**
  * Built-in tools on {@link AgentConfig.builtinTools}. Each enabled
  * capability materializes as ordinary server tools at discovery time, so
@@ -596,14 +573,12 @@ export type KvCasResult =
   | { ok: false; current: KvVersionedEntry | undefined };
 
 /**
- * Conditional-write superset of {@link HostKvApi} for coordination
- * protocols (the upcoming session ledger). Version-token CAS was chosen
- * over compare-value: every candidate backend can mint a cheap opaque
- * token (counter, UUID, row version), while compare-value would force
- * deep JSON equality with key-order pitfalls on each of them. The
+ * Conditional-write superset of {@link HostKvApi}. Version-token CAS was
+ * chosen over compare-value: every candidate backend can mint a cheap
+ * opaque token (counter, UUID, row version), while compare-value would
+ * force deep JSON equality with key-order pitfalls on each of them. The
  * agent-facing `host.kv` stays plain {@link HostKvApi}; storage backends
- * supply CAS via the optional `cas` group on `defineStorage`, and
- * coordination features fail fast when the backend lacks it.
+ * supply CAS via the optional `cas` group on `defineStorage`.
  */
 export interface HostKvCasApi extends HostKvApi {
   /** Read one value with its version token. Miss → `undefined`. */
@@ -2574,11 +2549,6 @@ export interface ResolvedAgent {
   hosting?: AgentHostingOptions;
   /** Validated turn admission limits from {@link AgentConfig.concurrency}. */
   concurrency?: AgentConcurrencyOptions;
-  /**
-   * Validated serving mode from {@link AgentConfig.serving}. Undefined
-   * means `"resident"` (the default path).
-   */
-  serving?: AgentServingMode;
   tools: DiscoveredTool[];
   skills: DiscoveredSkill[];
   connections: DiscoveredConnection[];