@abloatai/ablo 0.34.1 → 0.36.0

package/dist/coordination/schema.d.ts

@@ -1,722 +0,0 @@
-import { z } from 'zod';
-/**
- * The wire schemas for coordination — the shapes that keep humans and agents
- * from overwriting each other on a shared row. Coordination works in three
- * layers, from outermost to innermost:
- *
- *   1. Presence (observation): who is working where. It reports, never blocks.
- *   2. Claims (pessimistic leases): `claim_begin` / `claim_abandon` grant one
- *      participant exclusive intent on a target while others wait.
- *   3. Stale-context (optimistic): a `readAt` watermark plus an `onStale` write
- *      guard that catches a lost update when the row moved after you read it.
- *
- * These Zod schemas are the single definition of each shape. Both the client
- * SDK and the server derive their TypeScript types from them with `z.infer`
- * rather than re-declaring the shapes, and the server validates inbound frames
- * against them at runtime.
- */
-/** A line/column span within a text-bearing field (slide body, doc, cell). */
-export declare const targetRangeSchema: z.ZodObject<{
-    startLine: z.ZodNumber;
-    endLine: z.ZodNumber;
-    startColumn: z.ZodOptional<z.ZodNumber>;
-    endColumn: z.ZodOptional<z.ZodNumber>;
-}, z.core.$strip>;
-export type TargetRange = z.infer<typeof targetRangeSchema>;
-export declare const participantKindSchema: z.ZodEnum<{
-    user: "user";
-    agent: "agent";
-    system: "system";
-}>;
-export type ParticipantKind = z.infer<typeof participantKindSchema>;
-/**
- * Parses a participant kind from an inbound frame, tolerating an older wire
- * dialect. Some presence and claim frames label a non-agent participant
- * `'human'`, while the rest of the surface uses `'user'` for the same
- * participant. This normalizes `'human'` to `'user'` on read so every consumer
- * switches on one vocabulary. Producers emit the canonical
- * {@link participantKindSchema} values, and the output union is never widened.
- */
-export declare const wireParticipantKindSchema: z.ZodPreprocess<z.ZodEnum<{
-    user: "user";
-    agent: "agent";
-    system: "system";
-}>>;
-/**
- * Resolves a peer's kind from an inbound presence or claim frame. It prefers
- * the server-stamped `participantKind` (normalized through
- * {@link wireParticipantKindSchema}). A frame from an older server that omits
- * that field falls back to the `isAgent` boolean, which can tell 'agent' from
- * 'user' but can never report 'system'.
- */
-export declare function participantKindFromWire(wireKind: unknown, isAgent: boolean | undefined): ParticipantKind;
-/**
- * Reads the peer-visible description a claim or presence frame carries in its
- * opaque `meta.description`. This is the single place that unpacks that field.
- * A caller that has an explicit `description` should prefer it
- * (`explicit ?? fromMeta`).
- */
-export declare function descriptionFromMeta(meta: Record<string, unknown> | undefined | null): string | undefined;
-/**
- * What a coordination event points at — the locator shared by all three
- * layers. It names an entity, optionally narrowed to a path, range, or field,
- * and carries opaque application metadata.
- */
-export declare const targetRefSchema: z.ZodObject<{
-    entityType: z.ZodString;
-    entityId: z.ZodString;
-    path: z.ZodOptional<z.ZodString>;
-    range: z.ZodOptional<z.ZodObject<{
-        startLine: z.ZodNumber;
-        endLine: z.ZodNumber;
-        startColumn: z.ZodOptional<z.ZodNumber>;
-        endColumn: z.ZodOptional<z.ZodNumber>;
-    }, z.core.$strip>>;
-    field: z.ZodOptional<z.ZodString>;
-    meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-}, z.core.$strip>;
-export type TargetRef = z.infer<typeof targetRefSchema>;
-/**
- * How the server treats a write whose snapshot watermark (`readAt`) is older
- * than the target row's latest change. There are three dispositions:
- *   • `notify`    — hold the write and return a {@link StaleNotification}
- *                   carrying the current value, so the actor (agent or human)
- *                   can resolve it.
- *   • `reject`    — throw `AbloStaleContextError`, the default when `readAt`
- *                   is present.
- *   • `overwrite` — apply the write blindly, last write wins, with no signal.
- */
-export declare const onStaleModeSchema: z.ZodEnum<{
-    reject: "reject";
-    overwrite: "overwrite";
-    notify: "notify";
-}>;
-export type OnStaleMode = z.infer<typeof onStaleModeSchema>;
-/**
- * The optimistic guard carried on a commit operation. `readAt` is the
- * snapshot watermark from `context.capture` (null/absent ⇒ unguarded write).
- * `bypass` is the explicit, recorded override of a *foreign* pessimistic
- * claim — see the claim layer below.
- */
-export declare const writeGuardSchema: z.ZodObject<{
-    readAt: z.ZodOptional<z.ZodNullable<z.ZodNumber>>;
-    onStale: z.ZodOptional<z.ZodNullable<z.ZodEnum<{
-        reject: "reject";
-        overwrite: "overwrite";
-        notify: "notify";
-    }>>>;
-    bypass: z.ZodOptional<z.ZodBoolean>;
-}, z.core.$strip>;
-export type WriteGuard = z.infer<typeof writeGuardSchema>;
-/**
- * The advisory returned to a committer whose write hit a stale-context
- * conflict under `onStale: 'notify'` — it reports that the value the committer
- * reasoned against changed while they were away. Rather than throwing, the
- * server hands back the conflicting field's current value as data so the
- * actor — an agent or a human — can reconcile and re-commit. A claim is the
- * prospective form of the same idea (coordinate before acting); this
- * notification is the in-flight form (here is what changed, you resolve). It
- * rides on the commit acknowledgement alongside `lastSyncId`; an empty or
- * absent array means nothing the committer depended on moved.
- *
- * Only `onStale: 'notify'` produces this. The conflicting operation was held,
- * not written, and the actor reconciles against `currentValues` and
- * re-commits. `reject` throws instead, and `overwrite` proceeds silently —
- * neither notifies.
- */
-export declare const staleNotificationSchema: z.ZodObject<{
-    object: z.ZodOptional<z.ZodLiteral<"stale_notification">>;
-    model: z.ZodString;
-    id: z.ZodString;
-    readAt: z.ZodNumber;
-    observedSyncId: z.ZodNumber;
-    conflictingFields: z.ZodArray<z.ZodString>;
-    currentValues: z.ZodRecord<z.ZodString, z.ZodUnknown>;
-    writtenBy: z.ZodObject<{
-        kind: z.ZodEnum<{
-            user: "user";
-            agent: "agent";
-            system: "system";
-        }>;
-        id: z.ZodString;
-    }, z.core.$strip>;
-    group: z.ZodOptional<z.ZodString>;
-}, z.core.$strip>;
-export type StaleNotification = z.infer<typeof staleNotificationSchema>;
-/**
- * A read that a commit declares it depended on, so the server can ask "did
- * anything I looked at change?" — broader than the write-target check, which
- * only validates the rows being written. The server re-runs stale detection
- * against each declared read at its `readAt`; a moved premise fires the entry's
- * `onStale` disposition (default `reject`) across the whole batch (`notify`
- * holds every write and notifies, `reject` aborts, `overwrite` proceeds
- * silently). A dependency comes at one of two granularities:
- *
- *   • Row   — `{ model, id, readAt, fields? }`: did this specific row, or these
- *             specific fields, change?
- *   • Group — `{ group, readAt }`: did anything in this sync group change?
- *             `group` is a sync-group key such as `deck:abc` or `slide:s1`, the
- *             same unit a participant watches and claims.
- *
- * See `packages/sync-engine/docs/concurrency-convention.md` (§4) for the
- * governing convention and the receive → reconcile loop.
- */
-export declare const readDependencySchema: z.ZodUnion<readonly [z.ZodObject<{
-    model: z.ZodString;
-    id: z.ZodString;
-    readAt: z.ZodNumber;
-    fields: z.ZodOptional<z.ZodArray<z.ZodString>>;
-    onStale: z.ZodOptional<z.ZodEnum<{
-        reject: "reject";
-        overwrite: "overwrite";
-        notify: "notify";
-    }>>;
-}, z.core.$strip>, z.ZodObject<{
-    group: z.ZodString;
-    readAt: z.ZodNumber;
-    onStale: z.ZodOptional<z.ZodEnum<{
-        reject: "reject";
-        overwrite: "overwrite";
-        notify: "notify";
-    }>>;
-}, z.core.$strip>]>;
-export type ReadDependency = z.infer<typeof readDependencySchema>;
-/**
- * A durable read-dependency — what a participant is watching so that a later
- * change to it opens a {@link StaleNotification}. It is the persisted sibling of
- * a {@link ReadDependency}: the same reference shape, minus the disposition (a
- * track always notifies — that is what tracking is), with an optional `readAt`
- * that defaults to the watermark of the commit that registered it. The row form
- * watches one object; the group form watches a whole sync group ("anything in
- * `deck:abc`"). Where a `ReadDependency` is checked once at commit and discarded,
- * a `TrackDependency` is kept and re-checked against every future delta. See
- * `packages/sync-engine/docs/groups.md` for how it drives change propagation.
- */
-export declare const trackDependencySchema: z.ZodUnion<readonly [z.ZodObject<{
-    model: z.ZodString;
-    id: z.ZodString;
-    readAt: z.ZodOptional<z.ZodNumber>;
-}, z.core.$strip>, z.ZodObject<{
-    group: z.ZodString;
-    readAt: z.ZodOptional<z.ZodNumber>;
-}, z.core.$strip>]>;
-export type TrackDependency = z.infer<typeof trackDependencySchema>;
-/**
- * The lifecycle of a claim. When absent on the wire it means `'active'` (an
- * additive back-compat default). The server stamps `'active'` on `claim_begin`
- * and emits one terminal frame — `committed`, `canceled`, or `expired` — as the
- * claim ends, so contenders learn how it resolved, not merely that it vanished.
- */
-export declare const claimStatusSchema: z.ZodEnum<{
-    active: "active";
-    committed: "committed";
-    expired: "expired";
-    canceled: "canceled";
-}>;
-export type ClaimStatus = z.infer<typeof claimStatusSchema>;
-export declare const wireClaimSummarySchema: z.ZodObject<{
-    field: z.ZodOptional<z.ZodString>;
-    description: z.ZodOptional<z.ZodString>;
-    entityType: z.ZodString;
-    entityId: z.ZodString;
-    meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    claimId: z.ZodString;
-    declaredAt: z.ZodNumber;
-    expiresAt: z.ZodNumber;
-}, z.core.$strip>;
-export type WireClaimSummary = z.infer<typeof wireClaimSummarySchema>;
-/** Why a claim ended in a non-success terminal state. */
-export declare const claimErrorSchema: z.ZodObject<{
-    code: z.ZodString;
-    message: z.ZodOptional<z.ZodString>;
-    heldBy: z.ZodOptional<z.ZodString>;
-    heldByClaimId: z.ZodOptional<z.ZodString>;
-    heldByExpiresAt: z.ZodOptional<z.ZodNumber>;
-    heldByClaim: z.ZodOptional<z.ZodObject<{
-        field: z.ZodOptional<z.ZodString>;
-        description: z.ZodOptional<z.ZodString>;
-        entityType: z.ZodString;
-        entityId: z.ZodString;
-        meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-        claimId: z.ZodString;
-        declaredAt: z.ZodNumber;
-        expiresAt: z.ZodNumber;
-    }, z.core.$strip>>;
-    policyReason: z.ZodOptional<z.ZodString>;
-}, z.core.$strip>;
-export type ClaimError = z.infer<typeof claimErrorSchema>;
-/**
- * A declared, pending-mutation claim — the unit broadcast inside a presence
- * frame's `activeClaims`. The client supplies the descriptive `targetRef`
- * fields, a `description` of the work, and a chosen `claimId`; the server stamps
- * `declaredAt` and `expiresAt` and may set `status` and `error`. Those last
- * two are optional, so one shape serves both the server, which sets them, and
- * the leaner SDK view, which reads a claim without them.
- */
-export declare const wireClaimSchema: z.ZodObject<{
-    entityType: z.ZodString;
-    entityId: z.ZodString;
-    path: z.ZodOptional<z.ZodString>;
-    range: z.ZodOptional<z.ZodObject<{
-        startLine: z.ZodNumber;
-        endLine: z.ZodNumber;
-        startColumn: z.ZodOptional<z.ZodNumber>;
-        endColumn: z.ZodOptional<z.ZodNumber>;
-    }, z.core.$strip>>;
-    field: z.ZodOptional<z.ZodString>;
-    meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    fenceToken: z.ZodOptional<z.ZodNumber>;
-    acquiredAt: z.ZodOptional<z.ZodNumber>;
-    claimId: z.ZodString;
-    description: z.ZodOptional<z.ZodString>;
-    declaredAt: z.ZodNumber;
-    expiresAt: z.ZodNumber;
-    status: z.ZodOptional<z.ZodEnum<{
-        active: "active";
-        committed: "committed";
-        expired: "expired";
-        canceled: "canceled";
-    }>>;
-    error: z.ZodOptional<z.ZodObject<{
-        code: z.ZodString;
-        message: z.ZodOptional<z.ZodString>;
-        heldBy: z.ZodOptional<z.ZodString>;
-        heldByClaimId: z.ZodOptional<z.ZodString>;
-        heldByExpiresAt: z.ZodOptional<z.ZodNumber>;
-        heldByClaim: z.ZodOptional<z.ZodObject<{
-            field: z.ZodOptional<z.ZodString>;
-            description: z.ZodOptional<z.ZodString>;
-            entityType: z.ZodString;
-            entityId: z.ZodString;
-            meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-            claimId: z.ZodString;
-            declaredAt: z.ZodNumber;
-            expiresAt: z.ZodNumber;
-        }, z.core.$strip>>;
-        policyReason: z.ZodOptional<z.ZodString>;
-    }, z.core.$strip>>;
-}, z.core.$strip>;
-export type WireClaim = z.infer<typeof wireClaimSchema>;
-export declare const claimRejectionSchema: z.ZodObject<{
-    claimId: z.ZodString;
-    reason: z.ZodString;
-    target: z.ZodOptional<z.ZodObject<{
-        entityType: z.ZodString;
-        entityId: z.ZodString;
-        path: z.ZodOptional<z.ZodString>;
-        range: z.ZodOptional<z.ZodObject<{
-            startLine: z.ZodNumber;
-            endLine: z.ZodNumber;
-            startColumn: z.ZodOptional<z.ZodNumber>;
-            endColumn: z.ZodOptional<z.ZodNumber>;
-        }, z.core.$strip>>;
-        field: z.ZodOptional<z.ZodString>;
-        meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    }, z.core.$strip>>;
-    heldBy: z.ZodOptional<z.ZodString>;
-    heldByClaimId: z.ZodOptional<z.ZodString>;
-    heldByExpiresAt: z.ZodOptional<z.ZodNumber>;
-    heldByClaim: z.ZodOptional<z.ZodObject<{
-        field: z.ZodOptional<z.ZodString>;
-        description: z.ZodOptional<z.ZodString>;
-        entityType: z.ZodString;
-        entityId: z.ZodString;
-        meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-        claimId: z.ZodString;
-        declaredAt: z.ZodNumber;
-        expiresAt: z.ZodNumber;
-    }, z.core.$strip>>;
-    policyReason: z.ZodOptional<z.ZodString>;
-}, z.core.$strip>;
-export type ClaimRejection = z.infer<typeof claimRejectionSchema>;
-/**
- * The point-to-point notification sent to a holder whose lease ended without
- * a successful commit. This remains a wire-shaped target because it arrives
- * directly from the WebSocket; the schema is the single validation boundary
- * before the event reaches public `claims.onLost` listeners.
- */
-export declare const claimLostSchema: z.ZodObject<{
-    claimId: z.ZodString;
-    reason: z.ZodEnum<{
-        expired: "expired";
-        preempted: "preempted";
-    }>;
-    target: z.ZodObject<{
-        entityType: z.ZodString;
-        entityId: z.ZodString;
-        path: z.ZodOptional<z.ZodString>;
-        range: z.ZodOptional<z.ZodObject<{
-            startLine: z.ZodNumber;
-            endLine: z.ZodNumber;
-            startColumn: z.ZodOptional<z.ZodNumber>;
-            endColumn: z.ZodOptional<z.ZodNumber>;
-        }, z.core.$strip>>;
-        field: z.ZodOptional<z.ZodString>;
-        meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    }, z.core.$strip>;
-}, z.core.$strip>;
-export type ClaimLost = z.infer<typeof claimLostSchema>;
-/**
- * What a {@link ModelClaim} points at — the target locator as SDK callers see
- * it, keyed by `model` and `id` rather than the wire schema's `entityType` and
- * `entityId`. This is the public `ModelTarget` shape.
- */
-export declare const modelTargetSchema: z.ZodReadonly<z.ZodObject<{
-    model: z.ZodString;
-    id: z.ZodString;
-    path: z.ZodOptional<z.ZodString>;
-    range: z.ZodOptional<z.ZodObject<{
-        startLine: z.ZodNumber;
-        endLine: z.ZodNumber;
-        startColumn: z.ZodOptional<z.ZodNumber>;
-        endColumn: z.ZodOptional<z.ZodNumber>;
-    }, z.core.$strip>>;
-    field: z.ZodOptional<z.ZodString>;
-    meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-}, z.core.$strip>>;
-export type ModelTarget = z.infer<typeof modelTargetSchema>;
-/**
- * A claim as SDK callers and the HTTP claim routes see it
- * (`ablo.<model>.claim.state`, `/v1/claims`) — the resolved, peer-readable view
- * of one active or queued claim. The client's `ModelClaim` type derives from
- * this shape.
- *
- * `expiresAt` is epoch milliseconds (a number), the same encoding as the
- * WebSocket {@link WireClaim}, so one timestamp representation spans the wire,
- * the SDK, HTTP, and errors — there is no ISO string anywhere.
- * `participantKind` is parsed through {@link wireParticipantKindSchema}, so a
- * legacy `'human'` frame normalizes to `'user'`.
- */
-export declare const modelClaimSchema: z.ZodReadonly<z.ZodObject<{
-    id: z.ZodString;
-    actor: z.ZodString;
-    participantKind: z.ZodPreprocess<z.ZodEnum<{
-        user: "user";
-        agent: "agent";
-        system: "system";
-    }>>;
-    description: z.ZodOptional<z.ZodString>;
-    field: z.ZodOptional<z.ZodString>;
-    status: z.ZodOptional<z.ZodEnum<{
-        active: "active";
-        queued: "queued";
-    }>>;
-    position: z.ZodOptional<z.ZodNumber>;
-    expiresAt: z.ZodNumber;
-    fenceToken: z.ZodOptional<z.ZodNumber>;
-    target: z.ZodReadonly<z.ZodObject<{
-        model: z.ZodString;
-        id: z.ZodString;
-        path: z.ZodOptional<z.ZodString>;
-        range: z.ZodOptional<z.ZodObject<{
-            startLine: z.ZodNumber;
-            endLine: z.ZodNumber;
-            startColumn: z.ZodOptional<z.ZodNumber>;
-            endColumn: z.ZodOptional<z.ZodNumber>;
-        }, z.core.$strip>>;
-        field: z.ZodOptional<z.ZodString>;
-        meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    }, z.core.$strip>>;
-}, z.core.$strip>>;
-export type ModelClaim = z.infer<typeof modelClaimSchema>;
-/**
- * The `claim_begin` payload a client sends. It carries the descriptive target
- * and a `description` of the work, an optional duration hint, and the opt-in
- * fair-queue flag. The server stamps the lifecycle and timestamp fields, so they
- * are not part of this inbound shape — this is exactly what the server validates
- * on ingest.
- */
-export declare const claimBeginPayloadSchema: z.ZodObject<{
-    entityType: z.ZodString;
-    entityId: z.ZodString;
-    path: z.ZodOptional<z.ZodString>;
-    range: z.ZodOptional<z.ZodObject<{
-        startLine: z.ZodNumber;
-        endLine: z.ZodNumber;
-        startColumn: z.ZodOptional<z.ZodNumber>;
-        endColumn: z.ZodOptional<z.ZodNumber>;
-    }, z.core.$strip>>;
-    field: z.ZodOptional<z.ZodString>;
-    meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    claimId: z.ZodString;
-    description: z.ZodOptional<z.ZodString>;
-    estimatedMs: z.ZodOptional<z.ZodNumber>;
-    queue: z.ZodOptional<z.ZodBoolean>;
-}, z.core.$strip>;
-export type ClaimBeginPayload = z.infer<typeof claimBeginPayloadSchema>;
-/**
- * The `claim_abandon` payload a client sends. `entityType` and `entityId` let
- * the server dequeue a claim that is still waiting (not yet held) from the FIFO
- * line; abandoning a claim that is already held needs only `claimId`.
- */
-export declare const claimAbandonPayloadSchema: z.ZodObject<{
-    claimId: z.ZodString;
-    entityType: z.ZodOptional<z.ZodString>;
-    entityId: z.ZodOptional<z.ZodString>;
-}, z.core.$strip>;
-export type ClaimAbandonPayload = z.infer<typeof claimAbandonPayloadSchema>;
-/**
- * The `claim_reorder` payload a client sends. A privileged participant, such as
- * a supervisor over its sub-agents, re-ranks the FIFO wait queue for an entity:
- * `order` lists waiters by `heldBy` and `claimId` in the desired priority, and
- * any waiter not listed keeps its relative order behind those that are. The
- * server gates who may call this and drops an unauthorized sender. Where
- * `claim_abandon` acts on the caller's own entry, a reorder acts on other
- * participants' queue positions — which is why it is gated.
- */
-export declare const claimReorderPayloadSchema: z.ZodObject<{
-    entityType: z.ZodString;
-    entityId: z.ZodString;
-    order: z.ZodArray<z.ZodObject<{
-        heldBy: z.ZodString;
-        claimId: z.ZodString;
-    }, z.core.$strip>>;
-}, z.core.$strip>;
-export type ClaimReorderPayload = z.infer<typeof claimReorderPayloadSchema>;
-/**
- * The `claim_heartbeat` payload a client sends to extend a lease it holds (or
- * refresh its slot in the wait queue) past the liveness window — the
- * work-duration signal for long-running holders, distinct from the connection
- * keepalive.
- *
- * The claim is identified either way: by `claimId`, or — since a claim is
- * singular per (actor, entity) — by the full `entityType`/`entityId` target
- * ("my claim on this row"). At least one of the two must be present. The
- * target also lets the server resolve without a scan and is required to
- * refresh a *queued* claim (a waiter is not in the holder set the server
- * would otherwise search).
- */
-export declare const claimHeartbeatPayloadSchema: z.ZodObject<{
-    claimId: z.ZodOptional<z.ZodString>;
-    entityType: z.ZodOptional<z.ZodString>;
-    entityId: z.ZodOptional<z.ZodString>;
-    ttlMs: z.ZodOptional<z.ZodNumber>;
-    details: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-}, z.core.$strip>;
-export type ClaimHeartbeatPayload = z.infer<typeof claimHeartbeatPayloadSchema>;
-/**
- * The server's reply to a `claim_heartbeat`. For a socketless worker the
- * heartbeat reply is the only inbound signal path, so it carries the lease's
- * fate rather than a bare ok: `held` (extended to `expiresAt`), `queued`
- * (slot refreshed; `position` is the current place in line), or `lost` (the
- * lease expired and the queue moved on — the worker should abandon or
- * re-queue, and any write it still attempts is caught by its `readAt` guard).
- */
-export declare const claimHeartbeatAckPayloadSchema: z.ZodObject<{
-    claimId: z.ZodString;
-    status: z.ZodEnum<{
-        queued: "queued";
-        held: "held";
-        lost: "lost";
-    }>;
-    expiresAt: z.ZodOptional<z.ZodNumber>;
-    position: z.ZodOptional<z.ZodNumber>;
-    queueDepth: z.ZodOptional<z.ZodNumber>;
-}, z.core.$strip>;
-export type ClaimHeartbeatAckPayload = z.infer<typeof claimHeartbeatAckPayloadSchema>;
-/**
- * The batched heartbeat — one request extends every lease the caller holds
- * on its plane (the socketless twin of the WebSocket keepalive, which renews
- * all held leases on every ping). For a worker holding many rows this is one
- * round trip per cadence instead of one per claim. Queued slots are not
- * batch-refreshed: a waiter knows its target and beats it directly.
- */
-export declare const claimHeartbeatBatchPayloadSchema: z.ZodObject<{
-    ttlMs: z.ZodOptional<z.ZodNumber>;
-}, z.core.$strip>;
-export type ClaimHeartbeatBatchPayload = z.infer<typeof claimHeartbeatBatchPayloadSchema>;
-/** Reply to a batched heartbeat: one ack entry per lease that was extended. */
-export declare const claimHeartbeatBatchAckPayloadSchema: z.ZodObject<{
-    results: z.ZodArray<z.ZodObject<{
-        claimId: z.ZodString;
-        status: z.ZodEnum<{
-            queued: "queued";
-            held: "held";
-            lost: "lost";
-        }>;
-        expiresAt: z.ZodOptional<z.ZodNumber>;
-        position: z.ZodOptional<z.ZodNumber>;
-        queueDepth: z.ZodOptional<z.ZodNumber>;
-    }, z.core.$strip>>;
-}, z.core.$strip>;
-export type ClaimHeartbeatBatchAckPayload = z.infer<typeof claimHeartbeatBatchAckPayloadSchema>;
-/**
- * The `update_subscription` payload a client sends. It replaces the
- * connection's read interest with the complete set of sync groups — the read
- * counterpart to a claim, with no write lock and no TTL. Each entry is a
- * {@link syncGroupInputSchema} (`'default'` or a branded `kind:id`), so a
- * malformed group is rejected on ingest rather than silently indexed. The
- * element type is strict because this is untrusted client input.
- */
-export declare const updateSubscriptionPayloadSchema: z.ZodObject<{
-    syncGroups: z.ZodArray<z.ZodUnion<readonly [z.ZodLiteral<"default">, z.core.$ZodBranded<z.ZodTemplateLiteral<`${string}:${string}`>, "SyncGroup", "out">]>>;
-}, z.core.$strip>;
-export type UpdateSubscriptionPayload = z.infer<typeof updateSubscriptionPayloadSchema>;
-/**
- * `subscription_ack` payload (server → client). Echoes the connection's
- * effective read set after the update (unchanged on rejection — the update is
- * atomic). `error` is present iff `success` is false (e.g. a scoped key
- * requesting a group outside its grant). `syncGroups` is lenient
- * (`z.string()`) here, not branded: it is the server's own echo for display,
- * not untrusted input, and includes base anchors like `org:<id>`.
- */
-export declare const subscriptionAckPayloadSchema: z.ZodObject<{
-    success: z.ZodBoolean;
-    syncGroups: z.ZodArray<z.ZodString>;
-    error: z.ZodOptional<z.ZodObject<{
-        code: z.ZodString;
-        message: z.ZodString;
-    }, z.core.$strip>>;
-}, z.core.$strip>;
-export type SubscriptionAckPayload = z.infer<typeof subscriptionAckPayloadSchema>;
-export declare const commitOperationTypeSchema: z.ZodEnum<{
-    CREATE: "CREATE";
-    UPDATE: "UPDATE";
-    DELETE: "DELETE";
-    ARCHIVE: "ARCHIVE";
-    UNARCHIVE: "UNARCHIVE";
-}>;
-export type CommitOperationType = z.infer<typeof commitOperationTypeSchema>;
-/**
- * A single mutation in a commit batch, as it arrives on the wire. Extends the
- * optimistic `writeGuard` (`readAt`/`onStale`/`bypass`) — the structural link
- * that makes "every write is stale-guarded" legible in the type, not just in
- * prose.
- */
-export declare const commitOperationSchema: z.ZodObject<{
-    readAt: z.ZodOptional<z.ZodNullable<z.ZodNumber>>;
-    onStale: z.ZodOptional<z.ZodNullable<z.ZodEnum<{
-        reject: "reject";
-        overwrite: "overwrite";
-        notify: "notify";
-    }>>>;
-    bypass: z.ZodOptional<z.ZodBoolean>;
-    type: z.ZodEnum<{
-        CREATE: "CREATE";
-        UPDATE: "UPDATE";
-        DELETE: "DELETE";
-        ARCHIVE: "ARCHIVE";
-        UNARCHIVE: "UNARCHIVE";
-    }>;
-    model: z.ZodString;
-    id: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-    input: z.ZodOptional<z.ZodNullable<z.ZodRecord<z.ZodString, z.ZodUnknown>>>;
-    transactionId: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-    fenceToken: z.ZodOptional<z.ZodNullable<z.ZodNumber>>;
-}, z.core.$strip>;
-export type CommitOperation = z.infer<typeof commitOperationSchema>;
-/**
- * Any commit operation on the wire — the runtime-validated ingest contract.
- * Commit operations carry replace (last-write-wins) semantics, guarded by the
- * optimistic write guard. It is a distinct alias from {@link CommitOperation}
- * so the server's ingest boundary reads as "any op on the wire", even though
- * the two shapes are identical.
- */
-export type AnyCommitOperation = CommitOperation;
-export declare const presenceKindSchema: z.ZodEnum<{
-    enter: "enter";
-    update: "update";
-    leave: "leave";
-}>;
-export type PresenceKind = z.infer<typeof presenceKindSchema>;
-/** What a participant is actively working on (agents fill this in). */
-export declare const presenceActivitySchema: z.ZodObject<{
-    entityType: z.ZodString;
-    entityId: z.ZodString;
-    path: z.ZodOptional<z.ZodString>;
-    range: z.ZodOptional<z.ZodObject<{
-        startLine: z.ZodNumber;
-        endLine: z.ZodNumber;
-        startColumn: z.ZodOptional<z.ZodNumber>;
-        endColumn: z.ZodOptional<z.ZodNumber>;
-    }, z.core.$strip>>;
-    field: z.ZodOptional<z.ZodString>;
-    meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    action: z.ZodString;
-    detail: z.ZodOptional<z.ZodString>;
-}, z.core.$strip>;
-export type PresenceActivity = z.infer<typeof presenceActivitySchema>;
-/**
- * Full `presence_update` frame as the server broadcasts it. The activity +
- * `activeClaims` are the observation surface for the other two layers —
- * rendered, never acted on as enforcement.
- */
-export declare const presenceUpdateFrameSchema: z.ZodObject<{
-    kind: z.ZodEnum<{
-        enter: "enter";
-        update: "update";
-        leave: "leave";
-    }>;
-    userId: z.ZodOptional<z.ZodString>;
-    syncGroups: z.ZodOptional<z.ZodArray<z.ZodString>>;
-    timestamp: z.ZodOptional<z.ZodNumber>;
-    status: z.ZodString;
-    timezone: z.ZodOptional<z.ZodString>;
-    customStatus: z.ZodOptional<z.ZodString>;
-    activity: z.ZodOptional<z.ZodObject<{
-        entityType: z.ZodString;
-        entityId: z.ZodString;
-        path: z.ZodOptional<z.ZodString>;
-        range: z.ZodOptional<z.ZodObject<{
-            startLine: z.ZodNumber;
-            endLine: z.ZodNumber;
-            startColumn: z.ZodOptional<z.ZodNumber>;
-            endColumn: z.ZodOptional<z.ZodNumber>;
-        }, z.core.$strip>>;
-        field: z.ZodOptional<z.ZodString>;
-        meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-        action: z.ZodString;
-        detail: z.ZodOptional<z.ZodString>;
-    }, z.core.$strip>>;
-    isAgent: z.ZodOptional<z.ZodBoolean>;
-    participantKind: z.ZodOptional<z.ZodPreprocess<z.ZodEnum<{
-        user: "user";
-        agent: "agent";
-        system: "system";
-    }>>>;
-    activeClaims: z.ZodOptional<z.ZodArray<z.ZodObject<{
-        entityType: z.ZodString;
-        entityId: z.ZodString;
-        path: z.ZodOptional<z.ZodString>;
-        range: z.ZodOptional<z.ZodObject<{
-            startLine: z.ZodNumber;
-            endLine: z.ZodNumber;
-            startColumn: z.ZodOptional<z.ZodNumber>;
-            endColumn: z.ZodOptional<z.ZodNumber>;
-        }, z.core.$strip>>;
-        field: z.ZodOptional<z.ZodString>;
-        meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-        fenceToken: z.ZodOptional<z.ZodNumber>;
-        acquiredAt: z.ZodOptional<z.ZodNumber>;
-        claimId: z.ZodString;
-        description: z.ZodOptional<z.ZodString>;
-        declaredAt: z.ZodNumber;
-        expiresAt: z.ZodNumber;
-        status: z.ZodOptional<z.ZodEnum<{
-            active: "active";
-            committed: "committed";
-            expired: "expired";
-            canceled: "canceled";
-        }>>;
-        error: z.ZodOptional<z.ZodObject<{
-            code: z.ZodString;
-            message: z.ZodOptional<z.ZodString>;
-            heldBy: z.ZodOptional<z.ZodString>;
-            heldByClaimId: z.ZodOptional<z.ZodString>;
-            heldByExpiresAt: z.ZodOptional<z.ZodNumber>;
-            heldByClaim: z.ZodOptional<z.ZodObject<{
-                field: z.ZodOptional<z.ZodString>;
-                description: z.ZodOptional<z.ZodString>;
-                entityType: z.ZodString;
-                entityId: z.ZodString;
-                meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-                claimId: z.ZodString;
-                declaredAt: z.ZodNumber;
-                expiresAt: z.ZodNumber;
-            }, z.core.$strip>>;
-            policyReason: z.ZodOptional<z.ZodString>;
-        }, z.core.$strip>>;
-    }, z.core.$strip>>>;
-    delegatedFrom: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-}, z.core.$strip>;
-export type PresenceUpdateFrame = z.infer<typeof presenceUpdateFrameSchema>;