@adcp/sdk 16.0.0-beta.3 → 16.0.0-beta.5

package/dist/lib/reporting/ledger/managed.d.mts

@@ -1,535 +0,0 @@
-import type { ReportingAdjustmentReceipt, ReportingDeliveryCapabilities, ReportingMaterialization, ReportingReceipt, ReportingResource, ReportingVerification, SyncReportingReceiptsResponse } from '../../types/index.mjs';
-import type { AdcpToolMap } from '../../server/create-adcp-server.mjs';
-import { createReportingDeliveryHandler, createReportingStatusHandler } from './handler.mjs';
-import type { ReportingStatusConsumerScopeOptionsV1 } from './handler.mjs';
-import type { ReportingLedgerAdjustmentV1, ReportingLegacyRevisionReaderV1, ReportingLedgerObligationV1, ReportingLedgerRevisionV1, ReportingLedgerStore, ReportingManagedDeliveryBindingV1 } from './types.mjs';
-/**
- * Upper bound on an adapter's startup probe, so a hung provider cannot hang startup.
- * A router's per-route probe budget must stay under it, or this deadline fires
- * first and the failing route's id never reaches the startup error.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare const REPORTING_ADAPTER_PROBE_DEADLINE_MILLISECONDS_V1 = 30000;
-/**
- * The delivery pattern a destination authorization generation serves.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export type ReportingDestinationPatternV1 = ReportingManagedDeliveryBindingV1['method'];
-/**
- * Delivery patterns, in the order the protocol lists them.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare const REPORTING_DESTINATION_PATTERNS_V1: readonly ReportingDestinationPatternV1[];
-/**
- * Same constraint the protocol puts on `method.transport`.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare const REPORTING_DESTINATION_TRANSPORT_PATTERN_V1: RegExp;
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingDestinationAuthorizationV1 {
-    account_id: string;
-    destination_ref: string;
-    generation: number;
-    authorized_at: string;
-    /**
-     * Delivery pattern this generation serves, recorded when the generation is
-     * created. A destination has exactly one pattern, and a change to its
-     * delivery contract mints a new `destination_ref` generation, so this never
-     * changes for a generation. Absent on generations recorded before it
-     * existed (and on ones whose bindings did not agree when backfilled).
-     */
-    pattern?: ReportingDestinationPatternV1;
-    /**
-     * Transport (`s3`, `gcs`, ...) that holds this generation's provider grant,
-     * recorded and immutable like `pattern`. This is what lets `revoke()` be
-     * routed to the transport that holds the grant. Absent for the same legacy
-     * reasons as `pattern`.
-     */
-    transport?: string;
-    revoked_at?: string;
-    cleanup_completed_at?: string;
-}
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingManagedDeliveryLeaseV1 {
-    materialization: ReportingMaterialization;
-    binding: ReportingManagedDeliveryBindingV1;
-    obligation: ReportingLedgerObligationV1;
-    revision: ReportingLedgerRevisionV1;
-    owner: string;
-    generation: number;
-    expires_at: string;
-}
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingDestinationRevocationLeaseV1 {
-    authorization: ReportingDestinationAuthorizationV1;
-    owner: string;
-    generation: number;
-    expires_at: string;
-    /**
-     * SLA facts as the ledger's own clock sees them.
-     *
-     * The advertised window is measured from the instant the revocation was
-     * committed, so deciding whether a grant is still inside it on the worker's
-     * host clock lets skew silently extend or collapse the promise. A store
-     * that can compute them reports them here; `overdue` is true at the exact
-     * boundary, because the window is elapsed once it has been reached.
-     */
-    revoked_at?: string;
-    overdue?: boolean;
-    remaining_milliseconds?: number;
-}
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export type ReportingReceiptBatchEntryV1 = {
-    kind: 'revision';
-    receipt: ReportingReceipt;
-} | {
-    kind: 'adjustment';
-    receipt: ReportingAdjustmentReceipt;
-};
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingReceiptBatchInputV1 {
-    account_id: string;
-    consumer_id: string;
-    idempotency_key: string;
-    request_fingerprint: string;
-    entries: ReportingReceiptBatchEntryV1[];
-    received_at: string;
-}
-/**
- * Agent-wide Managed Delivery promises durably shared by every replica.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingManagedDeliveryAdvertisedPoliciesV1 {
-    automatedRecoveryWindowSeconds: number;
-    statusRetentionDays: number;
-    resourceRetentionDays: number;
-    authorizationRevocationSeconds: number;
-}
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingManagedDeliveryStore {
-    /**
-     * Prove that this store shares the supplied Core authority and has its
-     * durable schema installed. Throw an actionable configuration error when
-     * either condition is false; return true only after an operational probe.
-     */
-    probe(coreStore: ReportingLedgerStore): Promise<boolean>;
-    /**
-     * Direct-store introspection of installed Core recovery windows.
-     *
-     * This is optional and non-authoritative for capability publication. Runtime
-     * factories use `adoptAdvertisedPolicies`, whose store-side transaction must
-     * validate binding compatibility while holding the policy fence.
-     */
-    listInstalledRecoveryWindowSeconds?(): Promise<number[]>;
-    /**
-     * Records the agent-wide advertised recovery window so the store can hold
-     * later binding installs to it.
-     *
-     * Optional on the structural interface for source compatibility with
-     * direct-store integrations. The runtime factory uses the combined atomic
-     * hook below; this separate hook remains useful when bindings are installed
-     * without a runtime.
-     */
-    adoptAdvertisedRecoveryWindowSeconds?(seconds: number): Promise<void>;
-    /**
-     * Durably registers the advertised `status_retention_days`.
-     *
-     * Direct-store integrations can use this separate hook when no runtime is
-     * publishing the full capability policy. The runtime factory uses the
-     * combined atomic hook below so a failed startup cannot partially register
-     * its promises.
-     */
-    adoptAdvertisedStatusRetentionDays?(days: number): Promise<void>;
-    /**
-     * Atomically adopts every policy advertised by a Managed Delivery runtime
-     * and returns the strongest values enforced across all replicas.
-     *
-     * Recovery and authorization-revocation windows are maximum-delay promises,
-     * so the adopted value may only decrease. Status and resource retention are
-     * minimum-duration promises, so the adopted value may only increase. The
-     * operation must serialize with `installBinding`, validate every installed
-     * binding against the adopted recovery bound while holding that fence, and
-     * leave all four values unchanged if any validation or write fails. The
-     * store must enforce the adopted resource and revocation values at its
-     * settlement and revocation-claim boundaries.
-     *
-     * Optional on the base interface so direct-store integrations that use the
-     * separate hooks remain source-compatible. Capability publication requires
-     * this combined hook because two independent writes cannot prevent a failed
-     * startup from leaving only one promise registered.
-     */
-    adoptAdvertisedPolicies?(policy: ReportingManagedDeliveryAdvertisedPoliciesV1): Promise<ReportingManagedDeliveryAdvertisedPoliciesV1>;
-    authorizeDestination(input: Omit<ReportingDestinationAuthorizationV1, 'revoked_at' | 'cleanup_completed_at'>): Promise<void>;
-    revokeDestination(input: {
-        account_id: string;
-        destination_ref: string;
-        generation: number;
-        revoked_at: string;
-    }): Promise<boolean>;
-    installBinding(binding: ReportingManagedDeliveryBindingV1): Promise<{
-        inserted: boolean;
-    }>;
-    /**
-     * Installs the check `installBinding` applies to every new binding before it
-     * writes anything. A thrown error refuses the install and reaches the caller
-     * as-is. Pass `undefined` to remove it.
-     *
-     * The runtime registers the adapter's `admitBinding` here, so a binding no
-     * installed delivery route can serve is refused at install instead of
-     * failing at its first delivery. Optional on the structural interface so
-     * existing custom stores stay source-compatible; a runtime whose adapter
-     * supplies `admitBinding` refuses a store that cannot enforce it.
-     */
-    setBindingAdmission?(admit: ((binding: ReportingManagedDeliveryBindingV1) => void) | undefined): void;
-    planMaterializations(input?: {
-        account_id?: string;
-        limit?: number;
-    }): Promise<number>;
-    /**
-     * Fails materializations that have used every delivery attempt.
-     *
-     * The claim predicate stops handing them out, so without a sweep they stay
-     * `pending` forever — and the planner skips any obligation with a pending
-     * row, so the revision is never retried or replanned either.
-     */
-    failExhaustedMaterializations?(input?: {
-        account_id?: string;
-        limit?: number;
-    }): Promise<number>;
-    claimMaterialization(input: {
-        owner: string;
-        now: string;
-        lease_milliseconds: number;
-        account_id?: string;
-    }): Promise<ReportingManagedDeliveryLeaseV1 | null>;
-    settleMaterialization(input: {
-        lease: ReportingManagedDeliveryLeaseV1;
-        now: string;
-        /**
-         * Retention the store must see satisfied on its own clock.
-         *
-         * The worker checks it too, but a worker running behind would otherwise
-         * accept a resource the database already considers under-retained.
-         */
-        minimum_resource_retention_days?: number;
-        outcome: {
-            status: 'available' | 'delivered';
-            resource: ReportingResource;
-            verification: ReportingVerification;
-        } | {
-            status: 'failed';
-            failure_code: string;
-        };
-    }): Promise<boolean>;
-    claimRevocation(input: {
-        owner: string;
-        now: string;
-        lease_milliseconds: number;
-        account_id?: string;
-        /** Advertised window, so the store can compute SLA facts on its own clock. */
-        authorization_revocation_seconds?: number;
-    }): Promise<ReportingDestinationRevocationLeaseV1 | null>;
-    completeRevocation(input: {
-        lease: ReportingDestinationRevocationLeaseV1;
-        completed_at: string;
-    }): Promise<boolean>;
-    /**
-     * Releases a cleanup lease after a failed attempt so the grant is
-     * immediately reclaimable.
-     *
-     * Required, not optional: without it a failed attempt keeps its lease as
-     * the retry delay, which defers the next attempt and hides an overdue grant
-     * behind a lease that has not expired. `claimRevocation` orders by
-     * `cleanup_lease_generation`, and a failed attempt has already incremented
-     * it, so releasing cannot let one broken grant starve the queue.
-     */
-    releaseRevocation(input: {
-        lease: ReportingDestinationRevocationLeaseV1;
-        /** Holds the grant out of selection briefly so a retry is not a tight loop. */
-        backoff_milliseconds?: number;
-    }): Promise<boolean>;
-    getReadableResource(input: {
-        account_id: string;
-        resource_ref: string;
-    }): Promise<{
-        materialization: ReportingMaterialization;
-        binding: ReportingManagedDeliveryBindingV1;
-    } | null>;
-    isAuthorizationCurrent(input: {
-        account_id: string;
-        destination_ref: string;
-        generation: number;
-    }): Promise<boolean>;
-    syncReceiptBatch(input: ReportingReceiptBatchInputV1): Promise<SyncReportingReceiptsResponse['results']>;
-}
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingManagedDeliveryAdapterV1 {
-    /** Profiles this installed adapter can actually verify through its consumer/destination path. */
-    readonly verificationProfiles: readonly ReportingVerification['verification_profile'][];
-    /** Provider revoke installs a generation tombstone that fences late writes. */
-    readonly revocationFencesDeliveryGenerations: true;
-    deliver(input: Readonly<{
-        materialization: ReportingMaterialization;
-        binding: ReportingManagedDeliveryBindingV1;
-        obligation: ReportingLedgerObligationV1;
-        revision: ReportingLedgerRevisionV1;
-        maxBytes: number;
-    }>, context: {
-        signal: AbortSignal;
-    }): Promise<{
-        status: 'available' | 'delivered';
-        resource: ReportingResource;
-        verification: ReportingVerification;
-    }>;
-    read(input: Readonly<{
-        materialization: ReportingMaterialization;
-        binding: ReportingManagedDeliveryBindingV1;
-        resource: ReportingResource;
-        maxBytes: number;
-    }>, context: {
-        signal: AbortSignal;
-    }): Promise<Uint8Array>;
-    /** Remove seller-controlled provider grants. The durable deny is committed before this call. */
-    revoke(input: Readonly<{
-        authorization: ReportingDestinationAuthorizationV1;
-    }>, context: {
-        signal: AbortSignal;
-    }): Promise<void>;
-    /**
-     * Optional startup check that the adapter can reach what it delivers to.
-     * The runtime calls it once, before it adopts any durable policy, and
-     * refuses to start if it rejects. It must not mutate provider state.
-     */
-    probe?(context: {
-        signal: AbortSignal;
-    }): Promise<void>;
-    /**
-     * Optional install-time admission. Throw to refuse a binding this adapter
-     * could not deliver. The runtime wires it into the store's `installBinding`.
-     * A single adapter has no reason to define it; the delivery router does.
-     */
-    admitBinding?(binding: ReportingManagedDeliveryBindingV1): void;
-    /**
-     * Optional startup admission for an advertised managed offering. Throw if
-     * the adapter has no way to serve it. Called once per offering at runtime
-     * construction.
-     */
-    admitOffering?(offering: {
-        method: {
-            pattern: string;
-            transport: string;
-        };
-        reconciliation_mode?: string;
-    }): void;
-    /**
-     * Optional observability hook: the id of the route a binding or an
-     * authorization is dispatched to, or `undefined` if none. Only the id may be
-     * returned. The worker keys its per-route counts on it, so it must never
-     * carry credentials, locations or any other provider detail.
-     */
-    routeIdFor?(target: Readonly<{
-        binding: ReportingManagedDeliveryBindingV1;
-    } | {
-        authorization: ReportingDestinationAuthorizationV1;
-    }>): string | undefined;
-}
-/**
- * Per-route counts keyed by delivery route id. Present on a worker result only
- * when the installed adapter is a router, so a single-adapter runtime's result
- * shape is unchanged. Work that no route could take is counted under
- * `UNROUTED_REPORTING_ROUTE_KEY_V1`, which no route id can equal.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingManagedDeliveryRouteCountsV1 {
-    /** Materializations settled as delivered, by the route that delivered them. */
-    deliveriesByRoute: Record<string, number>;
-    /** Materializations that failed (including an unroutable binding), by route. */
-    deliveryFailuresByRoute: Record<string, number>;
-    /** Provider revocations completed, by the route that performed them. */
-    revocationsByRoute: Record<string, number>;
-    /** Revocation attempts that failed and were released for retry, by route. */
-    revocationFailuresByRoute: Record<string, number>;
-    /** Revocations that had already outlived the advertised window when claimed, by route. */
-    overdueByRoute: Record<string, number>;
-}
-/**
- * Key for work no delivery route could take. Not a valid route id.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare const UNROUTED_REPORTING_ROUTE_KEY_V1 = "~unrouted";
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingManagedDeliveryWorkerResultV1 extends Partial<ReportingManagedDeliveryRouteCountsV1> {
-    planned: number;
-    claimed: number;
-    delivered: number;
-    failed: number;
-    revocationsCompleted: number;
-    revocationsOverdue: number;
-    /** Materializations failed for using every delivery attempt. */
-    exhausted: number;
-}
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingManagedDeliveryWorkerOptionsV1 {
-    signal?: AbortSignal;
-    now?: () => Date;
-    maxIterations?: number;
-    leaseMilliseconds?: number;
-    deliveryDeadlineMilliseconds?: number;
-    resourceMaxBytes?: number;
-    /** Capability minimum enforced in addition to each immutable binding. */
-    minimumResourceRetentionDays?: number;
-    /**
-     * Mirror of the advertised `authorization_revocation_seconds`. Supplying it
-     * makes the scheduler honour the promise instead of merely printing it: a
-     * cleanup attempt is never given a budget that would run past
-     * `revoked_at + authorizationRevocationSeconds`, a failed attempt never holds
-     * a retry lease longer than the whole promised window, and a grant that has
-     * already outlived the window is counted in `revocationsOverdue` so the
-     * breach is observable rather than silent. Omit it only for a worker that is
-     * not backing an advertised capability.
-     */
-    authorizationRevocationSeconds?: number;
-    account_id?: string;
-    /**
-     * Loads verified rows for a claimed revision whose rows live in row storage
-     * rather than in the ledger document. `createReportingManagedDeliveryRuntime`
-     * supplies one backed by its Core store. PostgreSQL-kind chunks are
-     * hydrated by the managed store's claim itself; a direct caller whose rows
-     * live in an external binding must supply this, or the adapter receives a
-     * revision without rows.
-     */
-    hydrateRevision?: (revision: ReportingManagedDeliveryLeaseV1['revision'], account_id: string, signal: AbortSignal | undefined) => Promise<ReportingManagedDeliveryLeaseV1['revision']>;
-}
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface CreateReportingManagedDeliveryRuntimeOptionsV1<TContext extends {
-    account?: unknown;
-} = {
-    account?: unknown;
-}> {
-    coreStore: ReportingLedgerStore;
-    /** Exact-revision fallback for revisions the SDK ledger does not hold. */
-    legacyRevisionReader?: ReportingLegacyRevisionReaderV1;
-    store: ReportingManagedDeliveryStore & Required<Pick<ReportingManagedDeliveryStore, 'adoptAdvertisedPolicies'>>;
-    adapter: ReportingManagedDeliveryAdapterV1;
-    offerings: ReportingDeliveryCapabilities['offerings'];
-    automatedRecoveryWindowSeconds: number;
-    statusRetentionDays: number;
-    resourceRetentionDays: number;
-    authorizationRevocationSeconds: number;
-    resolveConsumerId?: (context: TContext) => string | Promise<string>;
-    consumerMismatchEscalation?: ReportingStatusConsumerScopeOptionsV1<TContext>['consumerMismatchEscalation'];
-}
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export interface ReportingManagedDeliveryRuntimeV1<TContext extends {
-    account?: unknown;
-} = {
-    account?: unknown;
-}> {
-    reportingDeliveryCapabilities: ReportingDeliveryCapabilities;
-    getReportingStatus: ReturnType<typeof createReportingStatusHandler<TContext>>;
-    getMediaBuyDelivery: ReturnType<typeof createReportingDeliveryHandler>;
-    syncReportingReceipts?: (request: AdcpToolMap['sync_reporting_receipts']['params'], context: TContext & {
-        account?: unknown;
-    }) => Promise<SyncReportingReceiptsResponse>;
-    runWorker(options?: ReportingManagedDeliveryWorkerOptionsV1): Promise<ReportingManagedDeliveryWorkerResultV1>;
-    readResource(input: {
-        account_id: string;
-        resource_ref: string;
-        signal?: AbortSignal;
-        maxBytes?: number;
-        deadlineMilliseconds?: number;
-    }): Promise<Uint8Array | null>;
-}
-/**
- * Wires all operational components before returning any Managed Delivery
- * capability claim. A missing receipt principal resolver limits the runtime to
- * Managed Delivery even if a consumer-receipt offering was supplied.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare function createReportingManagedDeliveryRuntime<TContext extends {
-    account?: unknown;
-} = {
-    account?: unknown;
-}>(options: CreateReportingManagedDeliveryRuntimeOptionsV1<TContext>): Promise<ReportingManagedDeliveryRuntimeV1<TContext>>;
-export declare function createSyncReportingReceiptsHandler<TContext extends {
-    account?: unknown;
-}>(store: ReportingManagedDeliveryStore, resolveConsumerId: (context: TContext) => string | Promise<string>, now?: () => Date): (request: AdcpToolMap["sync_reporting_receipts"]["params"], context: TContext) => Promise<SyncReportingReceiptsResponse>;
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare function runManagedDeliveryWorker(store: ReportingManagedDeliveryStore, adapter: ReportingManagedDeliveryAdapterV1, options?: ReportingManagedDeliveryWorkerOptionsV1): Promise<ReportingManagedDeliveryWorkerResultV1>;
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare function readManagedReportingResource(store: ReportingManagedDeliveryStore, adapter: ReportingManagedDeliveryAdapterV1, input: {
-    account_id: string;
-    resource_ref: string;
-    signal?: AbortSignal;
-    maxBytes?: number;
-    deadlineMilliseconds?: number;
-}): Promise<Uint8Array | null>;
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare function assertMaterializationOutcome(lease: ReportingManagedDeliveryLeaseV1, outcome: {
-    status: 'available' | 'delivered';
-    resource: ReportingResource;
-    verification: ReportingVerification;
-}, now: string, minimumResourceRetentionDays?: number): void;
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare function receiptEvidenceMatches(receipt: ReportingReceipt, materialization: ReportingMaterialization): boolean;
-/**
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare function adjustmentReceiptEvidenceMatches(receipt: ReportingAdjustmentReceipt, adjustment: ReportingLedgerAdjustmentV1): boolean;
-/**
- * Refuses a retained resource location that carries credential syntax.
- *
- * Exported because the worker is not the only way a resource reaches
- * storage: a caller driving `settleMaterialization` directly must be held to
- * the same rule, or a presigned location is persisted and then published in
- * `get_reporting_status`.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare function assertCredentialFreeReportingResourceLocationV1(location: string): void;
-/**
- * Stable helper for immutable binding creation.
- *
- * @experimental Reliable Reporting storage surface: breaking changes may ship in minor releases. See https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
- */
-export declare function reportingManagedDeliveryBindingV1(input: Omit<ReportingManagedDeliveryBindingV1, 'created_at' | 'semantic_fingerprint'> & {
-    created_at?: string;
-}): ReportingManagedDeliveryBindingV1;