@creatornader/agent-bridge 0.4.0 → 0.5.1

package/CHANGELOG.md

@@ -6,6 +6,88 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
 
 ## [Unreleased]
 
+## [0.5.1] - 2026-07-20
+
+### Fixed
+
+- Let a production gateway receive its PostgreSQL CA bundle through the separate
+  `AGENT_BRIDGE_RUNTIME_DATABASE_CA_BASE64` secret. The gateway decodes the bundle in
+  memory, forces certificate and hostname verification, and removes file-based TLS
+  CA parameters from the runtime URL. It rejects the ambiguous `ssl` parameter and
+  client-certificate file parameters instead of discarding them. The Fly preflight now
+  requires both runtime secrets.
+
+## [0.5.0] - 2026-07-20
+
+### Added
+
+- Add migration 020 to converge databases released through migration 019 on the managed-authority
+  function and attestation contract. Migration readiness accepts only the exact
+  released checksums or the current checksums for changed migrations, so existing
+  databases can advance without allowing arbitrary ledger drift.
+
+- Add migration 021 with an attested, database-derived backup-reader role. The role is
+  `NOLOGIN`, receives read-only access to Agent Bridge tables and sequences, and is
+  granted only to the schema owner so managed PostgreSQL can produce complete native
+  backups without exposing backup access to runtime or control principals. Migrations
+  accept `CREATEROLE`, while source native backups require a true superuser or
+  `BYPASSRLS`. A restore target superuser can validate a suspended restored schema owner.
+
+- Add a PostgreSQL 15 through 18 integration path that applies every migration as a
+  non-superuser with `CREATEROLE` and `BYPASSRLS`, matching the authority available on
+  managed providers such as Supabase.
+
+- Add a read-only production PostgreSQL preflight. It rejects unsupported server
+  majors, insufficient migration authority, migration-ledger drift, derived-role
+  collisions, and incompatible legacy import tables before any schema change runs.
+  It reports migration authority separately from native DR authority. Reports omit
+  connection URLs and database identities.
+
+- Add a manual production proof workflow for an existing Agent Bridge gateway. It
+  uses separate sender, receiver, Fly machine-cycle, and verifier jobs behind the
+  `agent-bridge-production-proof` environment. A versioned, phase-specific receipt
+  contract records offline queue replay, exact idempotency, cross-host claim and
+  acknowledgment, a changed Fly runtime instance ID, and fresh-edge verification without
+  storing credentials, message content, database URLs, or SQLite files.
+- Add an optional `messageId` filter to HTTP 2.1, MCP, and CLI delivery claims. It
+  atomically selects and maintains only that eligible recipient delivery. Omitting the
+  filter preserves claim-next behavior, and HTTP 2.0 rejects the new field.
+
+- Add a maintained Fly.io reference config with one always-running shared VM, HTTPS
+  ingress, `/readyz` checks, and a 30-second SIGTERM budget. Add a read-only preflight
+  that checks the local contract and, when an app is supplied, reports value-safe Fly
+  account and app observations. The deployment docs keep migration, restricted-runtime
+  bootstrap, secret changes, deployment, and cross-machine proof behind operator gates.
+
+### Fixed
+
+- Support managed PostgreSQL role administration without restating protected role
+  attributes. PostgreSQL 16 and newer may split one schema-owner membership across an
+  administrator grant and a separate inherit-and-set grant. Readiness and native DR
+  now validate and preserve the effective authority while rejecting unexpected grant
+  shapes. Ownership transfers receive schema `CREATE` only for the transaction that
+  needs it, and runtime bootstrap verifies an existing login before changing its
+  password or membership.
+
+- Make runtime bootstrap transactional and reject derived authority names, object
+  owners, unexpected memberships, and reverse membership edges before changing an
+  existing login.
+
+- Suspend restored runtime, control, and archive principals as `NOLOGIN` roles without
+  authority memberships. Control and archive registration histories receive explicit
+  revocation events. Restore may reuse one preexisting role only when it is the source
+  schema owner, the target session user, and a true superuser.
+
+- Resolve the Fly Dockerfile from the deployment config directory and reject missing
+  configured build files during the production preflight.
+
+- Check the client TLS socket during the production PostgreSQL preflight when a
+  session pooler terminates TLS before opening its database connection.
+
+- Fix the legacy Supabase setup script's column comment so PostgreSQL accepts the
+  checked-in schema without manual editing. The PostgreSQL integration suite now runs
+  that script before testing the v2 legacy import.
+
 ## [0.4.0] - 2026-07-19
 
 ### Added
@@ -284,7 +366,9 @@ First tagged release. Marks the point where agent-bridge has shipped its initial
 - Narrative-leak detection in CI + on commit via `creatornader/textleaks@v0.2.0` (renamed from leakguard).
 
 [0.1.0]: https://github.com/creatornader/agent-bridge/releases/tag/v0.1.0
-[Unreleased]: https://github.com/creatornader/agent-bridge/compare/v0.4.0...HEAD
+[Unreleased]: https://github.com/creatornader/agent-bridge/compare/v0.5.1...HEAD
+[0.5.1]: https://github.com/creatornader/agent-bridge/compare/v0.5.0...v0.5.1
+[0.5.0]: https://github.com/creatornader/agent-bridge/compare/v0.4.0...v0.5.0
 [0.4.0]: https://github.com/creatornader/agent-bridge/compare/v0.3.1...v0.4.0
 [0.3.1]: https://github.com/creatornader/agent-bridge/compare/v0.3.0...v0.3.1
 [0.3.0]: https://github.com/creatornader/agent-bridge/compare/v0.2.0...v0.3.0

package/README.md

@@ -63,6 +63,54 @@ a production TLS deployment. Read [the deployment guide](docs/deployment.md) bef
 exposing a gateway, changing network bindings, upgrading the schema, or relying on the
 named volume for persistent data.
 
+The repository also maintains a provider-neutral Fly.io reference at
+[`deploy/fly.toml`](deploy/fly.toml). It deliberately omits an app name and release
+command. Check the local contract before creating or changing any Fly resource:
+
+```bash
+npm run preflight:fly -- --json
+```
+
+Before migrating an existing PostgreSQL database, run the read-only production
+preflight with schema-owner authority:
+
+```bash
+AGENT_BRIDGE_DATABASE_URL="..." npm run preflight:postgres:production -- --json --require-ssl
+```
+
+The command checks the PostgreSQL major, database and role authority, existing
+migration ledger, derived-role collisions, and the legacy `shared_context` import
+shape inside a read-only transaction. `authority.roles` reports migration capability:
+the schema owner may be a true superuser or a managed-provider administrator with
+`CREATEROLE`. `authority.native_dr` reports source-backup capability. The source normally
+connects as the schema owner, which must be a true superuser or hold `BYPASSRLS`, so
+`CREATEROLE` alone can run migrations but cannot create a native backup. A restore target
+uses its superuser session to validate a suspended restored schema-owner shell. The
+migration suite tests both authority forms on PostgreSQL 15 through
+18. The command does not print the connection URL or apply DDL. `--require-ssl` rejects
+an unencrypted public database connection. Passing the preflight does not replace a
+backup or authorize migration. When a session pooler terminates TLS, the check inspects
+the client socket instead of the pooler's separate database connection.
+
+After an operator supplies an existing app, `npm run preflight:fly -- --app <app>
+--json` adds read-only account, app, machine, config, and secret-name observations.
+The command does not deploy, migrate, scale, restart, or print environment-variable
+values. The [Fly production procedure](docs/deployment.md#flyio-reference-hosting)
+keeps database migration and runtime-role bootstrap outside the gateway process.
+The Fly gateway expects two secrets: the restricted runtime database URL and a
+base64-encoded PostgreSQL CA bundle. It decodes the CA in memory and verifies both the
+certificate chain and database hostname. It never needs a CA file inside the image.
+
+The manual `gateway production proof` workflow tests an existing gateway after its
+deployment gate has passed. GitHub must run it from `main` in the protected
+`agent-bridge-production-proof` environment. Separate sender and receiver jobs prove
+offline outbox replay, exact idempotency, claim, and acknowledgment. The workflow then
+restarts the single Fly machine, requires a new runtime instance ID, and verifies the
+message and settled delivery with a fresh receiver instance and a new SQLite edge file.
+Its versioned receipts contain only identifiers, times, principal and workspace labels,
+the gateway origin, checks, and SHA-256 host evidence. They omit credentials, database
+URLs, message content, and SQLite files.
+
 ## What v2 provides
 
 - Immutable messages with UUIDv7 IDs and opaque server cursors.
@@ -364,10 +412,15 @@ PostgreSQL restore executes SQL from the dump, so use `--accept-source-sql-risk`
 for a bundle from a source you trust. The target must be a dedicated fresh database
 with the same database name and PostgreSQL major as the backup. Restore requires a
 superuser because it recreates object owners, role shells, memberships, and default
-privileges. It never enables login on restored external principals. If a restore fails
-after mutation begins, Agent Bridge disables new target connections and reports any
-residual roles or recovery paths. Inspect and clean those artifacts before retrying.
-Never run the source and restored target as active authorities at the same time.
+privileges. It never enables login on restored external principals. Runtime principals
+lose their runtime membership. Active control and archive registrations receive a new
+revocation event, and their principals lose those memberships. Re-enable a principal
+and register it again only after inspecting the restored target. A restore may reuse a
+preexisting role only when it is the source schema owner, the target session user, and
+a true superuser. Every other role collision fails. If a restore fails after mutation
+begins, Agent Bridge disables new target connections and reports any residual roles or
+recovery paths. Inspect and clean those artifacts before retrying. Never run the source
+and restored target as active authorities at the same time.
 
 Backup publication never replaces an existing output. Deterministic adjacent staging
 paths use the backup or request UUID. A retry with the same UUID reports retained
@@ -785,9 +838,18 @@ followed by capability locks in operator-before-auditor order. Registration and
 revocation use the same order. A stale session that remains in a revoked role cannot
 continue operating. The schema owner is the only bootstrap holder of all three control
 roles and the only role with ordinary execution authority on the registration
-functions. PostgreSQL superusers remain inside this trusted database-administration
-boundary. Readiness checks the running PostgreSQL major on every call, so upgrading an
-already-migrated database to an uncertified major disables the runtime.
+functions. PostgreSQL 16 and newer may represent its effective admin, inherit, and set
+authority with a bootstrap administrator row plus a schema-owner row. A native DR
+restore may recreate the same authority as one combined bootstrap-superuser grant.
+Readiness validates either physical form and its effective authority. True superusers
+and managed-provider schema owners remain inside this trusted database-administration
+boundary. A separate `NOLOGIN` backup-reader role grants only table and sequence read
+access to the schema owner. Runtime, control, archive, and external principals cannot
+inherit it. Native backups require the schema owner to be a true superuser or hold
+`BYPASSRLS`. A target restore superuser can validate the intentionally suspended
+schema-owner shell. `CREATEROLE` alone remains sufficient for migrations. Readiness checks the
+running PostgreSQL major on every call, so upgrading an already-migrated database to an
+uncertified major disables the runtime.
 
 Direct credential inserts default to empty scopes rather than full access. Issued
 identity, scope, label, expiry, and lineage fields cannot be edited directly. Existing
@@ -858,6 +920,7 @@ agent-bridge get --since 24h --unacked-by codex
 agent-bridge history --thread-id release-1
 agent-bridge acknowledge --ids <message-uuid>
 agent-bridge claim --lease-ms 30000
+agent-bridge claim --message-id <message-uuid> --lease-ms 30000
 agent-bridge send --target worker --delivery-policy '{"mode":"leased","maxAttempts":3,"retryBaseDelayMs":1000,"retryMaxDelayMs":60000,"retryJitterRatio":0.2}' "work"
 agent-bridge deliveries --state dead
 agent-bridge delivery-events --delivery-id <uuid>
@@ -882,6 +945,12 @@ History defaults to mailbox `inbox`: broadcasts plus messages targeted to the co
 
 Publishers set `deliveryPolicy` on the message. Leased policy uses `maxAttempts`, `retryBaseDelayMs`, `retryMaxDelayMs`, `retryJitterRatio`, and optional `notBefore`. Consumers cannot override those values. Consumer-side `maxAttempts` on claim and `retryPolicy` on nack remain validated but ignored for one compatibility release. New code should omit both fields.
 
+Claims normally select the next due delivery by priority. HTTP 2.1, MCP, and CLI
+callers may supply `messageId` or `--message-id` to atomically select only that due,
+recipient-visible delivery. The filter also scopes lease-expiry and exhaustion
+maintenance performed by that claim. Released HTTP 2.0 request shapes remain frozen
+and reject the field.
+
 The legacy Supabase adapter applies mailbox and receipt rules cooperatively. A holder of the legacy publishable key can bypass the adapter through PostgREST or its receipt RPC. Use the authenticated v2 gateway when the authorization boundary must be enforced.
 
 `agent-bridge pending` is a cheap shell gate for agent startup. It exits 0 when unread candidates or due delivery work are visible, 1 only for an authoritative empty result, and 2 when an empty remote state cannot be confirmed. Its JSON result separates unread context from executable delivery work and labels the state as `available`, `empty`, or `unknown`.

package/ROADMAP.md

@@ -88,6 +88,32 @@ The published npm version is the authority for whether this package line has shi
 - A production deployment guide covering TLS, network exposure, secret separation,
   backups, upgrade order, and schema rollback limits.
 
+### 0.5.0 package contents
+
+- Read-only PostgreSQL and Fly production preflights. The database preflight reports
+  migration authority separately from native DR authority. The Fly preflight checks
+  the maintained deployment contract and existing app state without exposing secret
+  values.
+- A maintained Fly.io reference config. The repository contract keeps schema-owner
+  and operator authority out of the gateway, but creating an app, provisioning
+  PostgreSQL, setting secrets, migrating, and deploying still require an operator
+  gate.
+- A manual, approval-protected production proof harness for an existing Fly gateway.
+  It separates sender, receiver, machine restart, and fresh-edge verification,
+  and publishes versioned receipts that exclude credentials and message content.
+- Managed PostgreSQL schema-owner and native-backup compatibility across PostgreSQL 15
+  through 18. Migrations accept either a true superuser or a non-superuser with the
+  required role-administration authority. Native DR separately requires the schema
+  owner to be a true superuser or hold `BYPASSRLS`. A restore target superuser can
+  validate the intentionally suspended restored schema-owner shell. PostgreSQL 16 and
+  newer split grants are normalized to one effective membership for readiness and native DR. A
+  dedicated read-only role lets the schema owner back up protected tables without
+  granting that access to the gateway or control principals. Exact released migration
+  checksums remain accepted during upgrade, while unrelated checksum drift still fails
+  closed.
+- Optional exact-message delivery claims in HTTP 2.1, MCP, and the CLI. HTTP 2.0 keeps
+  the released claim-next contract.
+
 ### Post-release validation and adoption
 
 - Move the project's own normal traffic to the authenticated gateway while retaining a
@@ -97,6 +123,9 @@ The published npm version is the authority for whether this package line has shi
   check covered startup, private mailbox sends, caller-scoped history, receipts, and
   client restart through the legacy compatibility backend. It did not prove
   gateway-only behavior.
+- Run the manual Fly proof against an operator-owned app and retain its sender,
+  receiver, machine-cycle, and verifier receipts. The repository harness is ready,
+  but the external proof remains incomplete until an approved workflow run succeeds.
 - Replace remaining direct legacy table pollers with the v2 cursor protocol.
 - Confirm the README, npm metadata, GitHub metadata, release notes, and package contents
   match the released artifact.

package/SECURITY.md

@@ -74,6 +74,36 @@ Keep the schema-owner, runtime, operator, archive, backup, and restore database
 authorities separate. Do not copy one client's token or backend file into another
 client's configuration.
 
+When a gateway receives `AGENT_BRIDGE_RUNTIME_DATABASE_CA_BASE64`, it decodes the PEM
+bundle in memory and forces PostgreSQL certificate and hostname verification. The
+gateway removes `sslmode` and `sslrootcert` before it opens the pool. It rejects URL
+parameters for `ssl`, a client certificate, client key, or key password. Keep the
+restricted database URL in a separate secret. Do not put either value in the image,
+source tree, command arguments, or deployment logs.
+
+Managed PostgreSQL may expose a schema-owner administrator with `CREATEROLE` instead
+of true superuser authority. That capability is sufficient for migrations. Native backup
+requires the schema owner to be a true superuser or hold `BYPASSRLS`, because the source
+backup must read tables protected by RLS. A restore target validates a suspended restored
+schema-owner shell through its own superuser session. Agent Bridge creates internal roles with safe
+defaults and fails if an existing role has elevated attributes. PostgreSQL 16 and newer
+may split the schema owner's admin, inherit, and set authority across two catalog rows.
+Native DR may restore the same authority as one combined bootstrap-superuser row.
+Security readiness accepts only those documented grant shapes, then checks their
+effective authority. Registered runtime, control, and archive logins do not receive
+that exception.
+
+The database-derived backup-reader role is `NOLOGIN` and has read-only access to Agent
+Bridge tables and sequences. Only the schema owner may inherit it. The runtime role,
+control and archive roles, and external principals must not hold it. Native-backup
+readiness fails on a missing object grant, an added privilege, an unexpected member, or
+a source schema owner without true-superuser or `BYPASSRLS` authority. A restricted
+runtime login cannot validate a suspended restored schema owner.
+
+PostgreSQL native restore does not reactivate external identities. Runtime memberships
+are omitted. Active control and archive memberships are replaced by explicit revocation
+events after the restored history. Re-enrollment requires a separate operator action.
+
 Run migrations as a one-shot schema-owner job before starting a new gateway image.
 Take and verify a native DR backup first. Gateway readiness checks the exact migration
 plan and protected catalog state. Once a migration changes the database, starting an

package/SKILL.md

@@ -39,7 +39,11 @@ Use v2 delivery tools for executable work. MCP `ack_context` and CLI `acknowledg
 
 Publish executable work with `deliveryPolicy`; consumers never select retry limits or backoff. Leased policy accepts `maxAttempts`, `retryBaseDelayMs`, `retryMaxDelayMs`, `retryJitterRatio`, and optional `notBefore`. Untargeted messages default to mailbox mode and targeted messages to leased mode. Only publishers cancel or requeue. Publishers and recipients can inspect delivery history. Requeue starts a new cycle without resetting lifetime attempts. Consumer `maxAttempts` on claim and `retryPolicy` on nack are validated but ignored for one compatibility release. External task completion stays outside Agent Bridge.
 
-Claim a delivery before acting. Renew a long lease only to retain ownership. A lease extension does not report progress or success. Record external task completion through the application or A2A protocol, then settle the Agent Bridge delivery separately.
+Claim a delivery before acting. Use `messageId` or CLI `--message-id` when the caller
+must atomically claim one known message instead of the next due item. Renew a long
+lease only to retain ownership. A lease extension does not report progress or success.
+Record external task completion through the application or A2A protocol, then settle
+the Agent Bridge delivery separately.
 
 Use `agent-bridge pending` as a cheap process gate before starting an agent. Exit 0 means unread candidates or due delivery work are visible. Exit 1 means the authoritative state is empty. Exit 2 means the remote state is unknown. During a gateway outage, cached unacknowledged results are degraded candidates with unknown acknowledgement state.
 

package/dist/archive.d.ts

@@ -1,6 +1,6 @@
 import { J as JsonValue, i as MessagePriority, f as DeliveryPolicy } from './bridge-domain-CBX3IVqC.js';
-import { P as PgQueryable } from './postgres-bridge-store-WASumj26.js';
-import './bridge-store-Boaj-ZbO.js';
+import { P as PgQueryable } from './postgres-bridge-store-C9KG9Z69.js';
+import './bridge-store-ByJ6CaJk.js';
 
 interface PortableArchiveMessage {
     id: string;

package/dist/{bridge-service-YTjGr91A.d.ts → bridge-service-CNBKdYXh.d.ts}

@@ -1,4 +1,4 @@
-import { a as BridgeStore, I as InsertMessageResult, d as MessageQuery, M as MessagePage, c as DeliveryQuery, b as DeliveryPage, D as DeliveryEventPage } from './bridge-store-Boaj-ZbO.js';
+import { a as BridgeStore, I as InsertMessageResult, d as MessageQuery, M as MessagePage, c as DeliveryQuery, b as DeliveryPage, D as DeliveryEventPage } from './bridge-store-ByJ6CaJk.js';
 import { c as BridgePrincipal, M as MessageDraft, B as BridgeDelivery, A as AgentPresence } from './bridge-domain-CBX3IVqC.js';
 
 type PublicMessageQuery = MessageQuery & {
@@ -12,6 +12,7 @@ declare class BridgeService {
     acknowledge(principalInput: BridgePrincipal, messageIds: string[]): Promise<number>;
     claim(principalInput: BridgePrincipal, options?: {
         leaseMs?: number;
+        messageId?: string;
         maxAttempts?: number;
     }): Promise<{
         delivery: BridgeDelivery;

package/dist/{bridge-store-Boaj-ZbO.d.ts → bridge-store-ByJ6CaJk.d.ts}

@@ -44,6 +44,7 @@ interface BridgeDiagnostics {
 }
 interface ClaimOptions {
     leaseMs: number;
+    messageId?: string;
     now?: Date;
     maxAttempts?: number;
 }

package/dist/bridge.d.ts

@@ -1,12 +1,12 @@
 import { b as BridgeMessage, c as BridgePrincipal, B as BridgeDelivery, R as RetryPolicy, A as AgentPresence } from './bridge-domain-CBX3IVqC.js';
 export { a as BridgeDeliveryEvent, d as BridgePrincipalMismatchError, e as BridgeValidationError, D as DeliveryAction, f as DeliveryPolicy, g as DeliveryState, h as DeliveryStateConflictError, J as JsonValue, L as LeasedDeliveryPolicy, M as MessageDraft, i as MessagePriority, j as cursorScope, k as decodeCursor, l as decodeScopedCursor, m as encodeCursor, n as encodeScopedCursor, s as scopedCursorScope, u as uuidv7, v as validateDeliveryCursorPosition, o as validateDeliveryPolicy, p as validateEventCursorPosition, q as validateLeasedDeliveryPolicy, r as validateMessageDraft, t as validatePrincipal, w as validateProject, x as validateUuid } from './bridge-domain-CBX3IVqC.js';
-import { a as BridgeStore, I as InsertMessageResult, d as MessageQuery, M as MessagePage, C as ClaimOptions, B as BridgeDiagnostics, c as DeliveryQuery } from './bridge-store-Boaj-ZbO.js';
-export { D as DeliveryEventPage, b as DeliveryPage } from './bridge-store-Boaj-ZbO.js';
-export { B as BridgeService, P as PublicMessageQuery } from './bridge-service-YTjGr91A.js';
-import { P as PgQueryable } from './postgres-bridge-store-WASumj26.js';
-export { a as PgTransactionClient, b as PostgresBridgeStore } from './postgres-bridge-store-WASumj26.js';
-export { A as AuthenticatedCredential, C as CredentialResolver, G as GatewayOptions, P as PostgresCredentialResolver, b as bearerToken, c as createGateway, h as hashCredential, s as safeTokenHashEqual } from './gateway-BQHpV-MZ.js';
-export { E as EdgeConflictError, a as EdgeDrainLease, b as EdgeEnqueueResult, c as EdgeMigrationDrainingError, d as EdgeMigrationGate, e as EdgeMigrationGateState, f as EdgeMigrationLeaseError, g as EdgeMigrationRetiredError, h as EdgeOutboxRecord, i as EdgeReadOnlyInspection, j as EdgeScope, k as EdgeStats, P as PendingMessage, S as SQLiteEdgeStore, l as edgeMessageFingerprint, m as edgeScopeKey, n as inspectEdgeScopeReadOnly, s as stableIdempotency } from './sqlite-edge-store-Bc15DvpX.js';
+import { a as BridgeStore, I as InsertMessageResult, d as MessageQuery, M as MessagePage, C as ClaimOptions, B as BridgeDiagnostics, c as DeliveryQuery } from './bridge-store-ByJ6CaJk.js';
+export { D as DeliveryEventPage, b as DeliveryPage } from './bridge-store-ByJ6CaJk.js';
+export { B as BridgeService, P as PublicMessageQuery } from './bridge-service-CNBKdYXh.js';
+import { P as PgQueryable } from './postgres-bridge-store-C9KG9Z69.js';
+export { a as PgTransactionClient, b as PostgresBridgeStore } from './postgres-bridge-store-C9KG9Z69.js';
+export { A as AuthenticatedCredential, C as CredentialResolver, G as GatewayOptions, P as PostgresCredentialResolver, b as bearerToken, c as createGateway, h as hashCredential, s as safeTokenHashEqual } from './gateway-CW-61lvs.js';
+export { E as EdgeConflictError, a as EdgeDrainLease, b as EdgeEnqueueResult, c as EdgeMigrationDrainingError, d as EdgeMigrationGate, e as EdgeMigrationGateState, f as EdgeMigrationLeaseError, g as EdgeMigrationRetiredError, h as EdgeOutboxRecord, i as EdgeReadOnlyInspection, j as EdgeScope, k as EdgeStats, P as PendingMessage, S as SQLiteEdgeStore, l as edgeMessageFingerprint, m as edgeScopeKey, n as inspectEdgeScopeReadOnly, s as stableIdempotency } from './sqlite-edge-store-CdMIOrho.js';
 export { CachedMessagePage, SQLiteBridgeStore, SyncDiagnostics, SyncInsertResult, SyncReport, SyncingBridgeStore, SyncingBridgeStoreOptions, isRetryableSyncError } from './sqlite.js';
 import 'node:http';
 
@@ -102,6 +102,7 @@ interface AppliedMigration {
 interface MigrationPlanEntry extends AppliedMigration {
     source: string;
 }
+declare function migrationRecordMatches(recorded: Pick<AppliedMigration, "version" | "name" | "checksum">, required: Pick<AppliedMigration, "version" | "name" | "checksum">): boolean;
 declare const REQUIRED_MIGRATIONS: readonly [{
     readonly version: 1;
     readonly name: "schema_state";
@@ -159,6 +160,12 @@ declare const REQUIRED_MIGRATIONS: readonly [{
 }, {
     readonly version: 19;
     readonly name: "endpoint_migration_same_successor";
+}, {
+    readonly version: 20;
+    readonly name: "managed_authority_compat";
+}, {
+    readonly version: 21;
+    readonly name: "native_backup_reader";
 }];
 declare function loadMigrationPlan(directory: string): Promise<MigrationPlanEntry[]>;
 declare function migrationsReady(db: PgQueryable, expected: ReadonlyArray<Pick<MigrationPlanEntry, "version" | "name" | "checksum">>): Promise<boolean>;
@@ -168,4 +175,4 @@ declare function runtimeSchemaReady(db: PgQueryable, options?: {
 }): Promise<boolean>;
 declare function runMigrations(db: PgQueryable, directory: string): Promise<AppliedMigration[]>;
 
-export { AgentPresence, type AppliedMigration, BridgeDelivery, BridgeDiagnostics, BridgeHttpError, BridgeMessage, BridgePrincipal, BridgeStore, ClaimOptions, DeliveryQuery, HttpBridgeStore, type HttpBridgeStoreOptions, InsertMessageResult, LegacySupabaseError, LegacySupabaseRestStore, MessagePage, MessageQuery, type MigrationPlanEntry, NATIVE_DR_ADVISORY_LOCK_KEY, PgQueryable, REQUIRED_MIGRATIONS, RetryPolicy, loadMigrationPlan, migrationsReady, rowIsolationReady, runMigrations, runtimeSchemaReady };
+export { AgentPresence, type AppliedMigration, BridgeDelivery, BridgeDiagnostics, BridgeHttpError, BridgeMessage, BridgePrincipal, BridgeStore, ClaimOptions, DeliveryQuery, HttpBridgeStore, type HttpBridgeStoreOptions, InsertMessageResult, LegacySupabaseError, LegacySupabaseRestStore, MessagePage, MessageQuery, type MigrationPlanEntry, NATIVE_DR_ADVISORY_LOCK_KEY, PgQueryable, REQUIRED_MIGRATIONS, RetryPolicy, loadMigrationPlan, migrationRecordMatches, migrationsReady, rowIsolationReady, runMigrations, runtimeSchemaReady };

package/dist/bridge.js

@@ -4,7 +4,7 @@ import {
   HttpBridgeStore,
   LegacySupabaseError,
   LegacySupabaseRestStore
-} from "./chunk-LAHNQZDN.js";
+} from "./chunk-Z6JP6MYD.js";
 import {
   EdgeConflictError,
   EdgeMigrationDrainingError,
@@ -17,23 +17,24 @@ import {
   inspectEdgeScopeReadOnly,
   isRetryableSyncError,
   stableIdempotency
-} from "./chunk-SV3SVBYS.js";
+} from "./chunk-SN7PIVDF.js";
 import {
   SQLiteBridgeStore
-} from "./chunk-DQOZJJZ2.js";
+} from "./chunk-IVG4XWWS.js";
 import "./chunk-GTK4KOED.js";
 import {
   PostgresBridgeStore
-} from "./chunk-2DFNOLMO.js";
+} from "./chunk-XDNT6ZNZ.js";
 import {
   NATIVE_DR_ADVISORY_LOCK_KEY,
   REQUIRED_MIGRATIONS,
   loadMigrationPlan,
+  migrationRecordMatches,
   migrationsReady,
   rowIsolationReady,
   runMigrations,
   runtimeSchemaReady
-} from "./chunk-6BTJE6D4.js";
+} from "./chunk-QNXHDOJ5.js";
 import "./chunk-VOQIDTCJ.js";
 import {
   PostgresCredentialResolver,
@@ -41,11 +42,11 @@ import {
   createGateway,
   hashCredential,
   safeTokenHashEqual
-} from "./chunk-3YHVUPU2.js";
+} from "./chunk-P635FAN4.js";
 import {
   BridgeService
-} from "./chunk-4VB44KJU.js";
-import "./chunk-IHZFI7TH.js";
+} from "./chunk-AWE3DFZV.js";
+import "./chunk-E4OWHGUE.js";
 import {
   BridgePrincipalMismatchError,
   BridgeValidationError,
@@ -99,6 +100,7 @@ export {
   inspectEdgeScopeReadOnly,
   isRetryableSyncError,
   loadMigrationPlan,
+  migrationRecordMatches,
   migrationsReady,
   rowIsolationReady,
   runMigrations,