@abloatai/ablo 0.35.0 → 0.37.0

package/dist/transaction/wire/auth.js

@@ -1,57 +0,0 @@
-/**
- * The request body for minting a session credential.
- *
- * `POST /v1/ephemeral_keys` is the first call any caller makes — nothing else in
- * the API is reachable without the credential it returns. That makes it the one
- * route a published contract cannot omit, so its shape lives here beside the
- * rest of the boundary rather than being read field-by-field out of the handler.
- *
- * The response side already had a home: `EphemeralKeyResponseSchema` in
- * `auth/schemas.ts`.
- */
-import { z } from 'zod';
-/** The participant this session acts as. */
-export const ephemeralKeyUserSchema = z.object({
-    id: z.string().min(1),
-    teamIds: z.array(z.string()).optional(),
-});
-/**
- * `POST /v1/ephemeral_keys` — mint a short-lived session credential.
- *
- * Only a secret key (`sk_`) may call this: a session cannot mint itself. By
- * default the key mints into the caller's own organization; naming a different
- * `organizationId` is the multi-tenant case and requires the
- * `ephemeral:mint-any-org` scope, which is the same privilege that allows
- * binding the session's schema to another organization's project.
- */
-export const ephemeralKeyRequestSchema = z.object({
-    /** The participant this session acts as. `userId` is the older spelling. */
-    user: ephemeralKeyUserSchema.optional(),
-    userId: z.string().min(1).optional(),
-    /**
-     * Mint into this organization instead of the caller's own. Requires the
-     * `ephemeral:mint-any-org` scope — without it a secret key can never mint a
-     * session into another tenant.
-     */
-    organizationId: z.string().min(1).optional(),
-    /**
-     * Resolve this session's schema from a shared project rather than from the
-     * target organization, while its data stays scoped to that organization.
-     * Both fields are set together, and both require `ephemeral:mint-any-org`.
-     */
-    schemaProjectId: z.string().min(1).optional(),
-    schemaOwnerOrgId: z.string().min(1).optional(),
-    /** Narrow the session to these sync groups. */
-    syncGroups: z.array(z.string()).optional(),
-    /** Lifetime in seconds. Capped by the server's maximum. */
-    ttlSeconds: z.number().int().positive().optional(),
-    /** A human-readable tag recorded with the key, for debugging. */
-    label: z.string().optional(),
-});
-/**
- * The capability mint body lives with the rest of the capability vocabulary in
- * `auth/capability.ts` — the grant is one structure, and its request form is a
- * face of it rather than a separate shape. Re-exported here so the wire barrel
- * stays the single import path for the boundary.
- */
-export { capabilityRequestSchema, grantedOperationSchema, capabilityOperationSchema, } from '../auth/capability.js';

package/dist/transaction/wire/bootstrapReason.d.ts

@@ -1,9 +0,0 @@
-import { z } from 'zod';
-/** Machine-readable reasons a live delta stream must resume via catch-up. */
-export declare const bootstrapReasonSchema: z.ZodEnum<{
-    too_far_behind: "too_far_behind";
-    too_many_deltas: "too_many_deltas";
-    missing_entities: "missing_entities";
-    stream_gap: "stream_gap";
-}>;
-export type BootstrapReason = z.infer<typeof bootstrapReasonSchema>;

package/dist/transaction/wire/bootstrapReason.js

@@ -1,8 +0,0 @@
-import { z } from 'zod';
-/** Machine-readable reasons a live delta stream must resume via catch-up. */
-export const bootstrapReasonSchema = z.enum([
-    'too_far_behind',
-    'too_many_deltas',
-    'missing_entities',
-    'stream_gap',
-]);

package/dist/transaction/wire/claimEvent.d.ts

@@ -1,76 +0,0 @@
-/**
- * A claim transition, as an entry in the log feed.
- *
- * `claimRecordSchema` answers "what is true about this lease right now"; this
- * answers "what happened to it, and when". It is the fourth projection of that
- * record and is built like the other three — a `.pick` off the record, never a
- * second object — so a field added to a claim reaches this feed or fails to
- * compile.
- *
- * The transition IS the state entered, so the vocabulary is
- * {@link publicClaimStatusSchema} rather than a parallel set of verbs. An event
- * saying `active` means exactly what `active` means to a caller polling
- * `GET /v1/claims/{claimId}` — the same five states, widened from the record's
- * two for the same reason the polling shape widens them: an observer can arrive
- * after the claim ended, and `committed`, `expired`, and `canceled` are answers
- * this feed must be able to give. A claim that vanishes without one of them is
- * indistinguishable from a claim that was never made.
- *
- * Two fields are deliberately dropped from the projection, and the coverage
- * assertion below names both so neither can be dropped by forgetting:
- *
- * **`id`** — spelled `claimId` here, because this event names a claim it is not
- * itself. The same distinction the record's own comment draws.
- *
- * **`meta`** — the record calls it "presence, not a checkpoint: it dies with
- * the lease." A heartbeat's last-beat-wins progress is a live reading, and
- * writing it into a durable event would preserve, forever, whichever beat
- * happened to land last. The feed records that the lease ended, not what its
- * holder was mid-sentence about when it did.
- */
-import { z } from 'zod';
-export declare const claimEventSchema: z.ZodReadonly<z.ZodObject<{
-    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>;
-        fields: z.ZodOptional<z.ZodReadonly<z.ZodArray<z.ZodString>>>;
-        meta: z.ZodOptional<z.ZodRecord<z.ZodString, z.ZodUnknown>>;
-    }, z.core.$strip>>;
-    description: z.ZodString;
-    expiresAt: z.ZodNumber;
-    onBehalfOfId: z.ZodNullable<z.ZodString>;
-    onBehalfOfKind: z.ZodNullable<z.ZodPreprocess<z.ZodEnum<{
-        user: "user";
-        agent: "agent";
-        system: "system";
-    }>>>;
-    capabilityId: z.ZodNullable<z.ZodString>;
-    fenceToken: z.ZodOptional<z.ZodNumber>;
-    position: z.ZodOptional<z.ZodNumber>;
-    participantKind: z.ZodPreprocess<z.ZodEnum<{
-        user: "user";
-        agent: "agent";
-        system: "system";
-    }>>;
-    actor: z.ZodString;
-    object: z.ZodLiteral<"claim_event">;
-    seq: z.ZodNumber;
-    at: z.ZodString;
-    claimId: z.ZodString;
-    status: z.ZodEnum<{
-        active: "active";
-        committed: "committed";
-        expired: "expired";
-        canceled: "canceled";
-        queued: "queued";
-    }>;
-}, z.core.$strip>>;
-export type ClaimEvent = z.infer<typeof claimEventSchema>;

package/dist/transaction/wire/claimEvent.js

@@ -1,73 +0,0 @@
-/**
- * A claim transition, as an entry in the log feed.
- *
- * `claimRecordSchema` answers "what is true about this lease right now"; this
- * answers "what happened to it, and when". It is the fourth projection of that
- * record and is built like the other three — a `.pick` off the record, never a
- * second object — so a field added to a claim reaches this feed or fails to
- * compile.
- *
- * The transition IS the state entered, so the vocabulary is
- * {@link publicClaimStatusSchema} rather than a parallel set of verbs. An event
- * saying `active` means exactly what `active` means to a caller polling
- * `GET /v1/claims/{claimId}` — the same five states, widened from the record's
- * two for the same reason the polling shape widens them: an observer can arrive
- * after the claim ended, and `committed`, `expired`, and `canceled` are answers
- * this feed must be able to give. A claim that vanishes without one of them is
- * indistinguishable from a claim that was never made.
- *
- * Two fields are deliberately dropped from the projection, and the coverage
- * assertion below names both so neither can be dropped by forgetting:
- *
- * **`id`** — spelled `claimId` here, because this event names a claim it is not
- * itself. The same distinction the record's own comment draws.
- *
- * **`meta`** — the record calls it "presence, not a checkpoint: it dies with
- * the lease." A heartbeat's last-beat-wins progress is a live reading, and
- * writing it into a durable event would preserve, forever, whichever beat
- * happened to land last. The feed records that the lease ended, not what its
- * holder was mid-sentence about when it did.
- */
-import { z } from 'zod';
-import { claimRecordSchema, publicClaimStatusSchema, } from '../coordination/schema.js';
-export const claimEventSchema = claimRecordSchema
-    .omit({ id: true, meta: true })
-    .partial({
-    /** Absent while queued — the token is minted at grant, never at enqueue. */
-    fenceToken: true,
-    /** Absent once held — a holder has no place in the line. */
-    position: true,
-})
-    .extend({
-    object: z.literal('claim_event'),
-    /**
-     * Position in the claim-event sequence. NOT a fence token: fence tokens
-     * order by acquisition and are minted only at grant, so they cannot
-     * position an enqueue, a release, or an expiry. Conflating the two would
-     * break the monotonicity `claim_fence_watermark` depends on.
-     */
-    seq: z.number().int().nonnegative(),
-    /**
-     * When the transition happened, ISO-8601.
-     *
-     * The claim family carries epoch milliseconds everywhere else and says so
-     * emphatically. This one field breaks with that on purpose: it shares an
-     * envelope with {@link logEventSchema}, whose `at` is ISO, and a consumer
-     * sorting the merged `data` array by `at` must not be comparing two
-     * encodings. Uniformity within the envelope beats uniformity within the
-     * family, because the envelope is what gets iterated.
-     */
-    at: z.string(),
-    /** The claim named, rather than the claim as a resource. */
-    claimId: z.string(),
-    /** The state entered. Widened from the record's two — see the preamble. */
-    status: publicClaimStatusSchema,
-})
-    .readonly();
-/**
- * The feed's view covers the record. A field added to a claim is either carried
- * into the feed or deliberately dropped by the `.omit` above — never missing
- * because nobody remembered the fourth projection.
- */
-const _claimEventCoversRecord = true;
-void _claimEventCoversRecord;