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

package/dist/lib/reporting/service/index.d.mts

@@ -1,22 +1,24 @@
 /**
- * Reliable Reporting service wiring, conformance runner and ledger maintenance.
+ * Reliable Reporting service wiring and conformance runner.
  *
- * Only the retention, compaction and change-feed maintenance exports (`./maintenance`) are `@experimental`.
- * The service factories and conformance runner follow normal semver.
+ * `createReliableReportingService` takes any `ReportingLedgerStore`. The PostgreSQL store, the production
+ * composition (`createPostgresReliableReportingProductionService`) and ledger maintenance
+ * (`reportingLedgerMaintenance`) live in `@adcp/reporting-storage`.
+ *
+ * The scheduler primitives (`reportingSchedulerDelay`, `rotateReportingRoster`, ...) and
+ * `REPORTING_MANAGED_DELIVERY_COMPOSITION_V1` are storage-facing building blocks for compositions such as
+ * `@adcp/reporting-storage/service`, covered by the experimental policy below; applications should not use them.
  *
  * Stability policy: https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
  *
  * @packageDocumentation
  */
-import type { Account, ResolveContext } from '../../server/decisioning/account.mjs';
+import type { Account } from '../../server/decisioning/account.mjs';
 import type { RequestContext } from '../../server/decisioning/context.mjs';
 import type { DecisioningPlatform } from '../../server/decisioning/platform.mjs';
 import type { ReliableReportingPlatform } from '../../server/decisioning/specialisms/reporting.mjs';
 import type { ReportingDeliveryCapabilities, ReportingDeliveryOffering } from '../../types/tools.generated.mjs';
-import { type CreatePostgresPersistentNotificationRuntimeOptions, type PostgresPersistentNotificationRuntime } from '../../server/notification-subscriptions/index.mjs';
-import { REPORTING_LEDGER_MIGRATION, PostgresReportingLedgerStore, PostgresReportingManagedDeliveryStore, type CreateReportingProducerOptionsV1, type ReportingConsumerMismatchEscalationV1, type ReportingLedgerConfigurationV1, type ReportingLedgerStore, type ReportingLegacyRevisionReaderV1, type ReportingProducerContactV1, type ReportingProducerV1, type ReportingManagedDeliveryAdapterV1, type ReportingManagedDeliveryRuntimeV1, type PostgresReportingManagedDeliveryStoreOptions, type PostgresReportingNotificationActivityOptions, type PostgresReportingNotificationActivityRuntime, type ReportingPgPool, type ReportingRowStorageOptionsV1, type ReportingSourceWithReaderV1 } from '../ledger/index.mjs';
-import { type PostgresReportingWebhookActivityV1 } from '../webhook-activity.mjs';
-import { type ReportingChangeFeedMaintenanceOptionsV1, type ReportingLedgerMaintenanceTaskResultV1, type ReportingCompactionOptionsV1, type ReportingRetentionOptionsV1 } from './maintenance.mjs';
+import { type CreateReportingProducerOptionsV1, type ReportingConsumerMismatchEscalationV1, type ReportingLedgerConfigurationV1, type ReportingLedgerStore, type ReportingLegacyRevisionReaderV1, type ReportingProducerContactV1, type ReportingProducerV1, type ReportingSourceWithReaderV1 } from '../ledger/index.mjs';
 import type { InlineReportingReplayRetentionV1 } from '../source/index.mjs';
 import { type InlineReportingDeliveryFetchV1, type ReportingSourceOfferingV1 } from '../source/index.mjs';
 /** The intentionally small provider boundary: one bounded slice fetch plus immutable metadata. */
@@ -161,20 +163,18 @@ export interface CreateReliableReportingServiceOptionsV1<TCtxMeta = Record<strin
     statusRetentionDays: number;
     subscribers?: CreateReportingProducerOptionsV1['subscribers'];
     /**
-     * Opt in to scheduled ledger maintenance for a Core-only deployment on a
-     * `PostgresReportingLedgerStore`. `start()` runs it at most once per
-     * `intervalMilliseconds`; `runMaintenance()` runs it on demand for a host
-     * with its own scheduler. The production service does this itself and does
-     * not take this option.
+     * Opt in to scheduled ledger maintenance (retention, compaction, change-feed pruning, abandoned-upload
+     * sweeps) for a Core-only deployment. `start()` runs it at most once per `intervalMilliseconds`;
+     * `runMaintenance()` runs it on demand for a host with its own scheduler.
      *
-     * Always swept: expired cursor snapshots and checkpoints, and abandoned row
-     * uploads. `retention` and `changeFeed` have the same shape and meaning as
-     * on `createPostgresReliableReportingProductionService`. Retention uses
-     * this service's `statusRetentionDays`, so it can never retire a period
-     * earlier than the retention advertised to buyers. `changeFeed` requires the
-     * store to be built with `changeFeed: true`.
+     * The SDK does not know what maintenance a store needs: the option takes a factory, called once at
+     * construction with the store and the retention and recovery-window commitments this service advertises
+     * to buyers, so maintenance can never retire a period earlier than that retention. For the PostgreSQL
+     * store, pass `reportingLedgerMaintenance({ ... })` from `@adcp/reporting-storage`. A factory that
+     * throws fails service construction, not the first scheduled pass. The production service in
+     * `@adcp/reporting-storage/service` runs maintenance itself and does not take this option.
      */
-    maintenance?: ReliableReportingMaintenanceOptionsV1;
+    maintenance?: ReliableReportingMaintenanceFactoryV1;
     /**
      * Serve exact revision reads (`get_media_buy_delivery`) for revisions this
      * ledger does not hold, such as a seller's pre-cutover ledger tables. The
@@ -192,19 +192,66 @@ export interface CreateReliableReportingServiceOptionsV1<TCtxMeta = Record<strin
      */
     legacyRevisionReader?: ReportingLegacyRevisionReaderV1;
 }
-export interface ReliableReportingMaintenanceOptionsV1 {
-    /** Minimum time between scheduled maintenance passes. Defaults to 300000 (5 minutes). */
-    intervalMilliseconds?: number;
-    /** Period-aligned retention; see the production service's `retention`. */
-    retention?: ReportingRetentionOptionsV1;
-    /** Opt-in snapshot compaction; see the production service's `compaction`. */
-    compaction?: ReportingCompactionOptionsV1;
-    /** Change-feed pruning and consumer hold; see the production service's `changeFeed`. */
-    changeFeed?: ReportingChangeFeedMaintenanceOptionsV1;
+/**
+ * Outcome of one maintenance task. A task that resolved but could not process some items is `completed`
+ * with `partialFailure` set; the pass resumes those items next time.
+ */
+export type ReliableReportingMaintenanceTaskResultV1 = {
+    readonly task: string;
+    readonly status: 'completed';
+    readonly result: unknown;
+    readonly partialFailure?: Error;
+} | {
+    readonly task: string;
+    readonly status: 'failed';
+    readonly error: unknown;
+};
+/** One scheduled maintenance pass, as built by a {@link ReliableReportingMaintenanceFactoryV1}. */
+export interface ReliableReportingMaintenanceV1 {
+    /** Minimum time between scheduled passes. A positive safe integer. */
+    readonly intervalMilliseconds: number;
+    /**
+     * Run one pass. Tasks are isolated: a task failure is reported in its result, never thrown. `report`
+     * is awaited, in task order, for every task that rejected or partially failed, unless `signal` has
+     * aborted (an abort is shutdown, not a fault).
+     */
+    run(input: {
+        signal?: AbortSignal | undefined;
+        report?: (error: unknown) => Promise<void>;
+    }): Promise<readonly ReliableReportingMaintenanceTaskResultV1[]>;
+}
+/** What the service tells a maintenance factory about the store it will maintain. */
+export interface ReliableReportingMaintenanceContextV1 {
+    readonly store: ReportingLedgerStore;
+    /** The `statusRetentionDays` this service advertises. */
+    readonly statusRetentionDays: number;
+    /** The `automatedRecoveryWindowSeconds` this service advertises. */
+    readonly automatedRecoveryWindowSeconds: number;
 }
+/**
+ * Builds the maintenance for one service. Throw from it to refuse a configuration the store cannot
+ * serve; the service lets the error reach the caller of `createReliableReportingService`.
+ */
+export type ReliableReportingMaintenanceFactoryV1 = (context: ReliableReportingMaintenanceContextV1) => ReliableReportingMaintenanceV1;
+/**
+ * Composition token, for packages that compose this service with a managed-delivery runtime (such as
+ * `createPostgresReliableReportingProductionService` in `@adcp/reporting-storage/service`). Such a
+ * composition passes `{ [REPORTING_MANAGED_DELIVERY_COMPOSITION_V1]: store }`, naming the very `store` it passes
+ * as `store`, so the Core service accepts the managed-delivery and reconciled-billing offerings that only that
+ * composition can serve. A plain Core service refuses them.
+ *
+ * It is an assertion by the composer, not an authentication boundary: it keeps a Core-only service from
+ * advertising capabilities it has no runtime for by accident (the value must be the store itself, so a copied
+ * `true` does nothing). It is a `Symbol.for` key so it holds across duplicate copies of the SDK. Applications
+ * should not use it.
+ *
+ * @experimental Storage-facing building block: 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_MANAGED_DELIVERY_COMPOSITION_V1: unique symbol;
 export interface ReliableReportingSetupV1 {
     readonly component: 'reliable-reporting-core';
-    readonly migrations: readonly [typeof REPORTING_LEDGER_MIGRATION];
+    /** The store's own `migrations`: what to apply before first use. Empty for a store that needs none. */
+    readonly migrations: readonly string[];
     readonly requiresIsolatedLedgerDatabaseAcknowledgement: true;
 }
 export interface ReliableReportingServiceV1<TCtxMeta = Record<string, unknown>> {
@@ -238,7 +285,7 @@ export interface ReliableReportingServiceV1<TCtxMeta = Record<string, unknown>>
      */
     runMaintenance(options?: {
         signal?: AbortSignal;
-    }): Promise<ReportingLedgerMaintenanceTaskResultV1[]>;
+    }): Promise<readonly ReliableReportingMaintenanceTaskResultV1[]>;
     start(options: ReliableReportingSchedulerOptionsV1): void;
     stop(): Promise<void>;
 }
@@ -247,126 +294,5 @@ export interface ReliableReportingServiceV1<TCtxMeta = Record<string, unknown>>
  * and scheduler into one Reliable Reporting Core lifecycle owner.
  */
 export declare function createReliableReportingService<TCtxMeta = Record<string, unknown>>(options: CreateReliableReportingServiceOptionsV1<TCtxMeta>): ReliableReportingServiceV1<TCtxMeta>;
-type ProductionNotificationOptions = Omit<CreatePostgresPersistentNotificationRuntimeOptions, 'db' | 'publisherScope' | 'checkpointDeliveryAttempt' | 'supportedAccountEventTypes'>;
-export type CreatePostgresReliableReportingProductionServiceOptionsV1<TCtxMeta = Record<string, unknown>> = Omit<CreateReliableReportingServiceOptionsV1<TCtxMeta>, 'store' | 'subscribers' | 'maintenance'> & {
-    db: ReportingPgPool;
-    /** Stable, non-secret deployment namespace shared by reporting workers. */
-    namespace: string;
-    /** Stable webhook publisher identity; credentials must never be used here. */
-    publisherScope: string;
-    /** Explicit acknowledgement required by the authoritative Core store. */
-    acknowledgeIsolatedDatabase: true;
-    /**
-     * Store new revision rows as verified canonical JSONL chunks. Adds
-     * `REPORTING_ROW_STORAGE_MIGRATION` (PostgreSQL 13+) to `setup.migrations`
-     * and probes it before publishing capabilities.
-     */
-    rowStorage?: boolean | ReportingRowStorageOptionsV1;
-    /**
-     * Opt in to period-aligned retention. Each scheduler pass retires whole
-     * periods once `max(statusRetentionDays, recordRetentionDays)` has elapsed
-     * since both the period end and its latest publication, deleting their
-     * rows and ledger records and leaving a tombstone. Abandoned row uploads
-     * and expired cursor snapshots are always swept. With `changeFeed`, a
-     * period is also held until every live registered feed consumer (updated
-     * within `changeFeed.maxFeedHoldDays`, default 7) has read its changes.
-     */
-    retention?: ReportingRetentionOptionsV1;
-    /**
-     * Opt in to compacting superseded snapshot revisions to metadata only, as
-     * adcontextprotocol/adcp#8100 permits. Off by default. Each scheduler pass
-     * drops the row content of snapshots that are superseded, past their
-     * recovery grace and not owed to any caller (receipts, current
-     * `received` / `unreadable` / `content_mismatch` statements), while every
-     * revision's metadata stays. Official revisions are never compacted. Uses
-     * this service's `statusRetentionDays` and `automatedRecoveryWindowSeconds`.
-     * The protocol takes compaction into effect only in the next eligible minor
-     * after November 20, 2026: do not enable this in production before then.
-     */
-    compaction?: ReportingCompactionOptionsV1;
-    /**
-     * Maintain the host change feed (`changesAfter`, `getCurrentRevision`,
-     * `listCurrentRevisions` on `stores.core`). Adds
-     * `REPORTING_LEDGER_CHANGES_MIGRATION` (PostgreSQL 13+); the scheduler prunes
-     * changes older than `changeRetentionDays` (default 30) unless a registered
-     * consumer updated within `maxFeedHoldDays` (default 7) still needs them.
-     */
-    changeFeed?: ReportingChangeFeedMaintenanceOptionsV1;
-    notifications: ProductionNotificationOptions;
-    managedDelivery: {
-        adapter: ReportingManagedDeliveryAdapterV1;
-        resourceRetentionDays: number;
-        authorizationRevocationSeconds: number;
-        store?: Omit<PostgresReportingManagedDeliveryStoreOptions, 'notificationActivityPort'>;
-    };
-    activity: Omit<PostgresReportingNotificationActivityOptions, 'db' | 'notifications' | 'namespace' | 'attemptCheckpoint' | 'tenantScopeForAccount'> & {
-        tenantScopeForAccount(accountId: string): string;
-    };
-    webhookActivity?: {
-        tableName?: string;
-        retentionDays?: number;
-    };
-    /** Resolve activity visibility from verified auth/registry state, never request fields. */
-    resolveWebhookActivityScope(context: ResolveContext): {
-        tenantId: string;
-        principalId: string;
-    } | Promise<{
-        tenantId: string;
-        principalId: string;
-    }>;
-    /** Trusted complete roster of consumers that owe receipts for an obligation. */
-    obligatedConsumers?: (input: {
-        reporting_obligation_id: string;
-        account_id: string;
-    }) => Promise<{
-        ids: readonly string[];
-        complete: boolean;
-        version?: string;
-    }>;
-    /** Optional migration-system bridge. Called before any capability probe. */
-    applyMigrations?: (migrations: readonly string[]) => Promise<void>;
-};
-export interface PostgresReliableReportingProductionServiceV1<TCtxMeta = Record<string, unknown>> {
-    readonly setup: {
-        readonly component: 'reliable-reporting-production';
-        readonly migrations: readonly string[];
-    };
-    readonly capabilities: ReportingDeliveryCapabilities;
-    readonly platform: ReliableReportingPlatform<TCtxMeta>;
-    readonly core: ReliableReportingServiceV1<TCtxMeta>;
-    readonly managed: ReportingManagedDeliveryRuntimeV1<RequestContext<Account<TCtxMeta>>>;
-    readonly notifications: PostgresPersistentNotificationRuntime;
-    readonly notificationActivity: PostgresReportingNotificationActivityRuntime;
-    readonly webhookActivity: PostgresReportingWebhookActivityV1;
-    readonly stores: {
-        core: PostgresReportingLedgerStore;
-        managed: PostgresReportingManagedDeliveryStore;
-    };
-    readonly running: boolean;
-    installConfiguration: ReliableReportingServiceV1<TCtxMeta>['installConfiguration'];
-    install<TPlatform extends DecisioningPlatform<unknown, TCtxMeta>>(platform: TPlatform): TPlatform & {
-        reporting: ReliableReportingPlatform<TCtxMeta>;
-    };
-    runCycle(options: ReliableReportingCycleOptionsV1): Promise<{
-        core: Awaited<ReturnType<ReliableReportingServiceV1<TCtxMeta>['runCycle']>>;
-        managed: Awaited<ReturnType<ReportingManagedDeliveryRuntimeV1['runWorker']>>;
-    }>;
-    recoverOnce(options: {
-        deploymentWide: true;
-    }): Promise<{
-        activity: Awaited<ReturnType<PostgresReportingNotificationActivityRuntime['recoverOnce']>>;
-        webhookOutbox: Awaited<ReturnType<PostgresPersistentNotificationRuntime['recoverOnce']>>;
-    }>;
-    start(options: ReliableReportingSchedulerOptionsV1 & {
-        deploymentWide: true;
-    }): void;
-    stop(): Promise<void>;
-}
-/**
- * Assemble and probe the complete seller-side Reliable Reporting production
- * chain. Capability publication happens only after every durable component is
- * present and the managed policy has been adopted.
- */
-export declare function createPostgresReliableReportingProductionService<TCtxMeta = Record<string, unknown>>(options: CreatePostgresReliableReportingProductionServiceOptionsV1<TCtxMeta>): Promise<PostgresReliableReportingProductionServiceV1<TCtxMeta>>;
 export * from './conformance.mjs';
-export { ReportingMaintenancePartialFailureError, type ReportingChangeFeedMaintenanceOptionsV1, type ReportingCompactionOptionsV1, type ReportingLedgerMaintenanceStoreV1, type ReportingLedgerMaintenanceTaskNameV1, type ReportingLedgerMaintenanceTaskResultV1, type ReportingRetentionOptionsV1, } from './maintenance.mjs';
+export * from './scheduler-support.mjs';

package/dist/lib/reporting/service/index.d.ts

@@ -1,22 +1,24 @@
 /**
- * Reliable Reporting service wiring, conformance runner and ledger maintenance.
+ * Reliable Reporting service wiring and conformance runner.
  *
- * Only the retention, compaction and change-feed maintenance exports (`./maintenance`) are `@experimental`.
- * The service factories and conformance runner follow normal semver.
+ * `createReliableReportingService` takes any `ReportingLedgerStore`. The PostgreSQL store, the production
+ * composition (`createPostgresReliableReportingProductionService`) and ledger maintenance
+ * (`reportingLedgerMaintenance`) live in `@adcp/reporting-storage`.
+ *
+ * The scheduler primitives (`reportingSchedulerDelay`, `rotateReportingRoster`, ...) and
+ * `REPORTING_MANAGED_DELIVERY_COMPOSITION_V1` are storage-facing building blocks for compositions such as
+ * `@adcp/reporting-storage/service`, covered by the experimental policy below; applications should not use them.
  *
  * Stability policy: https://github.com/adcontextprotocol/adcp-client/blob/main/docs/guides/REPORTING-STABILITY.md
  *
  * @packageDocumentation
  */
-import type { Account, ResolveContext } from '../../server/decisioning/account';
+import type { Account } from '../../server/decisioning/account';
 import type { RequestContext } from '../../server/decisioning/context';
 import type { DecisioningPlatform } from '../../server/decisioning/platform';
 import type { ReliableReportingPlatform } from '../../server/decisioning/specialisms/reporting';
 import type { ReportingDeliveryCapabilities, ReportingDeliveryOffering } from '../../types/tools.generated';
-import { type CreatePostgresPersistentNotificationRuntimeOptions, type PostgresPersistentNotificationRuntime } from '../../server/notification-subscriptions';
-import { REPORTING_LEDGER_MIGRATION, PostgresReportingLedgerStore, PostgresReportingManagedDeliveryStore, type CreateReportingProducerOptionsV1, type ReportingConsumerMismatchEscalationV1, type ReportingLedgerConfigurationV1, type ReportingLedgerStore, type ReportingLegacyRevisionReaderV1, type ReportingProducerContactV1, type ReportingProducerV1, type ReportingManagedDeliveryAdapterV1, type ReportingManagedDeliveryRuntimeV1, type PostgresReportingManagedDeliveryStoreOptions, type PostgresReportingNotificationActivityOptions, type PostgresReportingNotificationActivityRuntime, type ReportingPgPool, type ReportingRowStorageOptionsV1, type ReportingSourceWithReaderV1 } from '../ledger';
-import { type PostgresReportingWebhookActivityV1 } from '../webhook-activity';
-import { type ReportingChangeFeedMaintenanceOptionsV1, type ReportingLedgerMaintenanceTaskResultV1, type ReportingCompactionOptionsV1, type ReportingRetentionOptionsV1 } from './maintenance';
+import { type CreateReportingProducerOptionsV1, type ReportingConsumerMismatchEscalationV1, type ReportingLedgerConfigurationV1, type ReportingLedgerStore, type ReportingLegacyRevisionReaderV1, type ReportingProducerContactV1, type ReportingProducerV1, type ReportingSourceWithReaderV1 } from '../ledger';
 import type { InlineReportingReplayRetentionV1 } from '../source';
 import { type InlineReportingDeliveryFetchV1, type ReportingSourceOfferingV1 } from '../source';
 /** The intentionally small provider boundary: one bounded slice fetch plus immutable metadata. */
@@ -161,20 +163,18 @@ export interface CreateReliableReportingServiceOptionsV1<TCtxMeta = Record<strin
     statusRetentionDays: number;
     subscribers?: CreateReportingProducerOptionsV1['subscribers'];
     /**
-     * Opt in to scheduled ledger maintenance for a Core-only deployment on a
-     * `PostgresReportingLedgerStore`. `start()` runs it at most once per
-     * `intervalMilliseconds`; `runMaintenance()` runs it on demand for a host
-     * with its own scheduler. The production service does this itself and does
-     * not take this option.
+     * Opt in to scheduled ledger maintenance (retention, compaction, change-feed pruning, abandoned-upload
+     * sweeps) for a Core-only deployment. `start()` runs it at most once per `intervalMilliseconds`;
+     * `runMaintenance()` runs it on demand for a host with its own scheduler.
      *
-     * Always swept: expired cursor snapshots and checkpoints, and abandoned row
-     * uploads. `retention` and `changeFeed` have the same shape and meaning as
-     * on `createPostgresReliableReportingProductionService`. Retention uses
-     * this service's `statusRetentionDays`, so it can never retire a period
-     * earlier than the retention advertised to buyers. `changeFeed` requires the
-     * store to be built with `changeFeed: true`.
+     * The SDK does not know what maintenance a store needs: the option takes a factory, called once at
+     * construction with the store and the retention and recovery-window commitments this service advertises
+     * to buyers, so maintenance can never retire a period earlier than that retention. For the PostgreSQL
+     * store, pass `reportingLedgerMaintenance({ ... })` from `@adcp/reporting-storage`. A factory that
+     * throws fails service construction, not the first scheduled pass. The production service in
+     * `@adcp/reporting-storage/service` runs maintenance itself and does not take this option.
      */
-    maintenance?: ReliableReportingMaintenanceOptionsV1;
+    maintenance?: ReliableReportingMaintenanceFactoryV1;
     /**
      * Serve exact revision reads (`get_media_buy_delivery`) for revisions this
      * ledger does not hold, such as a seller's pre-cutover ledger tables. The
@@ -192,19 +192,66 @@ export interface CreateReliableReportingServiceOptionsV1<TCtxMeta = Record<strin
      */
     legacyRevisionReader?: ReportingLegacyRevisionReaderV1;
 }
-export interface ReliableReportingMaintenanceOptionsV1 {
-    /** Minimum time between scheduled maintenance passes. Defaults to 300000 (5 minutes). */
-    intervalMilliseconds?: number;
-    /** Period-aligned retention; see the production service's `retention`. */
-    retention?: ReportingRetentionOptionsV1;
-    /** Opt-in snapshot compaction; see the production service's `compaction`. */
-    compaction?: ReportingCompactionOptionsV1;
-    /** Change-feed pruning and consumer hold; see the production service's `changeFeed`. */
-    changeFeed?: ReportingChangeFeedMaintenanceOptionsV1;
+/**
+ * Outcome of one maintenance task. A task that resolved but could not process some items is `completed`
+ * with `partialFailure` set; the pass resumes those items next time.
+ */
+export type ReliableReportingMaintenanceTaskResultV1 = {
+    readonly task: string;
+    readonly status: 'completed';
+    readonly result: unknown;
+    readonly partialFailure?: Error;
+} | {
+    readonly task: string;
+    readonly status: 'failed';
+    readonly error: unknown;
+};
+/** One scheduled maintenance pass, as built by a {@link ReliableReportingMaintenanceFactoryV1}. */
+export interface ReliableReportingMaintenanceV1 {
+    /** Minimum time between scheduled passes. A positive safe integer. */
+    readonly intervalMilliseconds: number;
+    /**
+     * Run one pass. Tasks are isolated: a task failure is reported in its result, never thrown. `report`
+     * is awaited, in task order, for every task that rejected or partially failed, unless `signal` has
+     * aborted (an abort is shutdown, not a fault).
+     */
+    run(input: {
+        signal?: AbortSignal | undefined;
+        report?: (error: unknown) => Promise<void>;
+    }): Promise<readonly ReliableReportingMaintenanceTaskResultV1[]>;
+}
+/** What the service tells a maintenance factory about the store it will maintain. */
+export interface ReliableReportingMaintenanceContextV1 {
+    readonly store: ReportingLedgerStore;
+    /** The `statusRetentionDays` this service advertises. */
+    readonly statusRetentionDays: number;
+    /** The `automatedRecoveryWindowSeconds` this service advertises. */
+    readonly automatedRecoveryWindowSeconds: number;
 }
+/**
+ * Builds the maintenance for one service. Throw from it to refuse a configuration the store cannot
+ * serve; the service lets the error reach the caller of `createReliableReportingService`.
+ */
+export type ReliableReportingMaintenanceFactoryV1 = (context: ReliableReportingMaintenanceContextV1) => ReliableReportingMaintenanceV1;
+/**
+ * Composition token, for packages that compose this service with a managed-delivery runtime (such as
+ * `createPostgresReliableReportingProductionService` in `@adcp/reporting-storage/service`). Such a
+ * composition passes `{ [REPORTING_MANAGED_DELIVERY_COMPOSITION_V1]: store }`, naming the very `store` it passes
+ * as `store`, so the Core service accepts the managed-delivery and reconciled-billing offerings that only that
+ * composition can serve. A plain Core service refuses them.
+ *
+ * It is an assertion by the composer, not an authentication boundary: it keeps a Core-only service from
+ * advertising capabilities it has no runtime for by accident (the value must be the store itself, so a copied
+ * `true` does nothing). It is a `Symbol.for` key so it holds across duplicate copies of the SDK. Applications
+ * should not use it.
+ *
+ * @experimental Storage-facing building block: 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_MANAGED_DELIVERY_COMPOSITION_V1: unique symbol;
 export interface ReliableReportingSetupV1 {
     readonly component: 'reliable-reporting-core';
-    readonly migrations: readonly [typeof REPORTING_LEDGER_MIGRATION];
+    /** The store's own `migrations`: what to apply before first use. Empty for a store that needs none. */
+    readonly migrations: readonly string[];
     readonly requiresIsolatedLedgerDatabaseAcknowledgement: true;
 }
 export interface ReliableReportingServiceV1<TCtxMeta = Record<string, unknown>> {
@@ -238,7 +285,7 @@ export interface ReliableReportingServiceV1<TCtxMeta = Record<string, unknown>>
      */
     runMaintenance(options?: {
         signal?: AbortSignal;
-    }): Promise<ReportingLedgerMaintenanceTaskResultV1[]>;
+    }): Promise<readonly ReliableReportingMaintenanceTaskResultV1[]>;
     start(options: ReliableReportingSchedulerOptionsV1): void;
     stop(): Promise<void>;
 }
@@ -247,126 +294,5 @@ export interface ReliableReportingServiceV1<TCtxMeta = Record<string, unknown>>
  * and scheduler into one Reliable Reporting Core lifecycle owner.
  */
 export declare function createReliableReportingService<TCtxMeta = Record<string, unknown>>(options: CreateReliableReportingServiceOptionsV1<TCtxMeta>): ReliableReportingServiceV1<TCtxMeta>;
-type ProductionNotificationOptions = Omit<CreatePostgresPersistentNotificationRuntimeOptions, 'db' | 'publisherScope' | 'checkpointDeliveryAttempt' | 'supportedAccountEventTypes'>;
-export type CreatePostgresReliableReportingProductionServiceOptionsV1<TCtxMeta = Record<string, unknown>> = Omit<CreateReliableReportingServiceOptionsV1<TCtxMeta>, 'store' | 'subscribers' | 'maintenance'> & {
-    db: ReportingPgPool;
-    /** Stable, non-secret deployment namespace shared by reporting workers. */
-    namespace: string;
-    /** Stable webhook publisher identity; credentials must never be used here. */
-    publisherScope: string;
-    /** Explicit acknowledgement required by the authoritative Core store. */
-    acknowledgeIsolatedDatabase: true;
-    /**
-     * Store new revision rows as verified canonical JSONL chunks. Adds
-     * `REPORTING_ROW_STORAGE_MIGRATION` (PostgreSQL 13+) to `setup.migrations`
-     * and probes it before publishing capabilities.
-     */
-    rowStorage?: boolean | ReportingRowStorageOptionsV1;
-    /**
-     * Opt in to period-aligned retention. Each scheduler pass retires whole
-     * periods once `max(statusRetentionDays, recordRetentionDays)` has elapsed
-     * since both the period end and its latest publication, deleting their
-     * rows and ledger records and leaving a tombstone. Abandoned row uploads
-     * and expired cursor snapshots are always swept. With `changeFeed`, a
-     * period is also held until every live registered feed consumer (updated
-     * within `changeFeed.maxFeedHoldDays`, default 7) has read its changes.
-     */
-    retention?: ReportingRetentionOptionsV1;
-    /**
-     * Opt in to compacting superseded snapshot revisions to metadata only, as
-     * adcontextprotocol/adcp#8100 permits. Off by default. Each scheduler pass
-     * drops the row content of snapshots that are superseded, past their
-     * recovery grace and not owed to any caller (receipts, current
-     * `received` / `unreadable` / `content_mismatch` statements), while every
-     * revision's metadata stays. Official revisions are never compacted. Uses
-     * this service's `statusRetentionDays` and `automatedRecoveryWindowSeconds`.
-     * The protocol takes compaction into effect only in the next eligible minor
-     * after November 20, 2026: do not enable this in production before then.
-     */
-    compaction?: ReportingCompactionOptionsV1;
-    /**
-     * Maintain the host change feed (`changesAfter`, `getCurrentRevision`,
-     * `listCurrentRevisions` on `stores.core`). Adds
-     * `REPORTING_LEDGER_CHANGES_MIGRATION` (PostgreSQL 13+); the scheduler prunes
-     * changes older than `changeRetentionDays` (default 30) unless a registered
-     * consumer updated within `maxFeedHoldDays` (default 7) still needs them.
-     */
-    changeFeed?: ReportingChangeFeedMaintenanceOptionsV1;
-    notifications: ProductionNotificationOptions;
-    managedDelivery: {
-        adapter: ReportingManagedDeliveryAdapterV1;
-        resourceRetentionDays: number;
-        authorizationRevocationSeconds: number;
-        store?: Omit<PostgresReportingManagedDeliveryStoreOptions, 'notificationActivityPort'>;
-    };
-    activity: Omit<PostgresReportingNotificationActivityOptions, 'db' | 'notifications' | 'namespace' | 'attemptCheckpoint' | 'tenantScopeForAccount'> & {
-        tenantScopeForAccount(accountId: string): string;
-    };
-    webhookActivity?: {
-        tableName?: string;
-        retentionDays?: number;
-    };
-    /** Resolve activity visibility from verified auth/registry state, never request fields. */
-    resolveWebhookActivityScope(context: ResolveContext): {
-        tenantId: string;
-        principalId: string;
-    } | Promise<{
-        tenantId: string;
-        principalId: string;
-    }>;
-    /** Trusted complete roster of consumers that owe receipts for an obligation. */
-    obligatedConsumers?: (input: {
-        reporting_obligation_id: string;
-        account_id: string;
-    }) => Promise<{
-        ids: readonly string[];
-        complete: boolean;
-        version?: string;
-    }>;
-    /** Optional migration-system bridge. Called before any capability probe. */
-    applyMigrations?: (migrations: readonly string[]) => Promise<void>;
-};
-export interface PostgresReliableReportingProductionServiceV1<TCtxMeta = Record<string, unknown>> {
-    readonly setup: {
-        readonly component: 'reliable-reporting-production';
-        readonly migrations: readonly string[];
-    };
-    readonly capabilities: ReportingDeliveryCapabilities;
-    readonly platform: ReliableReportingPlatform<TCtxMeta>;
-    readonly core: ReliableReportingServiceV1<TCtxMeta>;
-    readonly managed: ReportingManagedDeliveryRuntimeV1<RequestContext<Account<TCtxMeta>>>;
-    readonly notifications: PostgresPersistentNotificationRuntime;
-    readonly notificationActivity: PostgresReportingNotificationActivityRuntime;
-    readonly webhookActivity: PostgresReportingWebhookActivityV1;
-    readonly stores: {
-        core: PostgresReportingLedgerStore;
-        managed: PostgresReportingManagedDeliveryStore;
-    };
-    readonly running: boolean;
-    installConfiguration: ReliableReportingServiceV1<TCtxMeta>['installConfiguration'];
-    install<TPlatform extends DecisioningPlatform<unknown, TCtxMeta>>(platform: TPlatform): TPlatform & {
-        reporting: ReliableReportingPlatform<TCtxMeta>;
-    };
-    runCycle(options: ReliableReportingCycleOptionsV1): Promise<{
-        core: Awaited<ReturnType<ReliableReportingServiceV1<TCtxMeta>['runCycle']>>;
-        managed: Awaited<ReturnType<ReportingManagedDeliveryRuntimeV1['runWorker']>>;
-    }>;
-    recoverOnce(options: {
-        deploymentWide: true;
-    }): Promise<{
-        activity: Awaited<ReturnType<PostgresReportingNotificationActivityRuntime['recoverOnce']>>;
-        webhookOutbox: Awaited<ReturnType<PostgresPersistentNotificationRuntime['recoverOnce']>>;
-    }>;
-    start(options: ReliableReportingSchedulerOptionsV1 & {
-        deploymentWide: true;
-    }): void;
-    stop(): Promise<void>;
-}
-/**
- * Assemble and probe the complete seller-side Reliable Reporting production
- * chain. Capability publication happens only after every durable component is
- * present and the managed policy has been adopted.
- */
-export declare function createPostgresReliableReportingProductionService<TCtxMeta = Record<string, unknown>>(options: CreatePostgresReliableReportingProductionServiceOptionsV1<TCtxMeta>): Promise<PostgresReliableReportingProductionServiceV1<TCtxMeta>>;
 export * from './conformance';
-export { ReportingMaintenancePartialFailureError, type ReportingChangeFeedMaintenanceOptionsV1, type ReportingCompactionOptionsV1, type ReportingLedgerMaintenanceStoreV1, type ReportingLedgerMaintenanceTaskNameV1, type ReportingLedgerMaintenanceTaskResultV1, type ReportingRetentionOptionsV1, } from './maintenance';
+export * from './scheduler-support';