@creatornader/agent-bridge 0.3.1 → 0.5.0

package/SECURITY.md

@@ -14,19 +14,24 @@ fixed. The npm package and GitHub release page are the public version authoritie
 
 ## Release integrity
 
-GitHub immutable releases are enabled, and GitHub reports release `v0.3.0` as
+GitHub immutable releases are enabled, and GitHub reports release `v0.3.1` as
 immutable. A repository ruleset also blocks updates and deletion for every `v*` tag
-without a bypass actor. The `v0.3.0` tag is unsigned.
+without a bypass actor. The `v0.3.1` tag is unsigned.
 
 npm publication uses a protected GitHub environment, an OIDC trusted-publisher
 binding, and provenance for the package artifact. Verify the package digest and
-attestation before treating provenance as source identity. The `v0.3.0`
+attestation before treating provenance as source identity. The
+[`v0.3.1` release run](https://github.com/creatornader/agent-bridge/actions/runs/29465467036)
+used package commit `d17ba544d31beaa33b4955e41c3b3d4e3f141900`.
+
+The historical `v0.3.0`
 [recovery run](https://github.com/creatornader/agent-bridge/actions/runs/29461308262)
 checked out package commit `95eb861`, while its attestation names recovery commit
 `c23d9df` as the workflow identity. GitHub Actions logs expire, so the
 [release notes](https://github.com/creatornader/agent-bridge/releases/tag/v0.3.0)
-also record this boundary. Future recovery dispatches must run at the release tag, and
-the workflow enforces that match before packaging.
+also record this boundary. Recovery dispatches must run at the release tag. The
+workflow also requires a successful `test.yml` run from `main` for the exact package
+commit before packaging.
 
 ## Report a vulnerability
 
@@ -46,6 +51,13 @@ Local mode relies on operating-system account isolation and private file permiss
 Anyone who can act as the same operating-system user can generally read or replace that
 user's Agent Bridge state. Local mode is not a hostile multi-user boundary.
 
+Managed-client mutations may cache a successful native Windows ACL check while one
+operation lock remains held. The cache is bound to the verified directory identity and is
+discarded with the lock. New locks, resumed operations, and passive inspection check
+the ACL again. POSIX permission checks are not cached. A same-user process can still
+change an ACL on an unchanged object or replace a directory with one that reuses the
+same filesystem identity. Both actions are within the local-mode trust boundary.
+
 ### Gateway mode
 
 Gateway credentials bind one workspace and principal. The gateway derives remote
@@ -53,10 +65,54 @@ identity from the credential, applies operation scopes and rate policy, and uses
 transaction-bound PostgreSQL request authority. Production runtime roles must not be
 superusers or hold `BYPASSRLS`. Put every non-loopback gateway behind TLS.
 
+Do not publish PostgreSQL on a public interface. Put it on a private network reachable
+only by the migration, runtime bootstrap, gateway, backup, and recovery jobs that need
+it. The checked-in Compose file binds both published ports to loopback and serves plain
+HTTP for local development. It is not a public deployment template.
+
 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.
 
+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
+older image is not a safe rollback. Apply a forward fix or restore the backup into a
+fresh target and switch authority only after verification.
+
+Drain old gateway instances before migrations 017 and 018. An old image reports `/readyz` as
+not ready after the new migration is visible, but a process that was already running
+can still serve ordinary requests until traffic is removed or it exits. Start the new
+gateway only after the migration and runtime bootstrap finish.
+
+Migration 018 accepts raw endpoint-migration challenges only as SQL function input. It
+stores a domain-separated SHA-256 commitment, never the raw challenge, and excludes
+live challenge rows from native DR data dumps. The challenge proves an active direct
+credential replacement on one authority. It does not authorize endpoint cutover.
+
 ### Legacy Supabase mode
 
 The legacy adapter keeps existing v1 deployments working, but its publishable key can
@@ -74,6 +130,9 @@ through a separately trusted channel.
 PostgreSQL restore executes SQL from the source dump. Use
 `--accept-source-sql-risk` only for a bundle from a trusted source. Never activate the
 source and restored target as authorities at the same time.
+The restored gateway authority UUID identifies the same logical authority. It does not
+prevent an operator from activating a live clone, so the deployment cutover remains an
+operator-controlled safety boundary.
 
 ### Optional integrations
 
@@ -86,5 +145,19 @@ when wrapper health is uncertain.
 - Pass gateway tokens through private enrollment or backend files, not shell arguments.
 - Keep database URLs in the documented environment variables. Do not put them in CLI
   arguments, logs, issues, or examples.
+- Store Compose password files outside version control with owner-only permissions.
+  Use the deployment platform's secret manager in production. Do not bake passwords or
+  tokens into images, Compose environment blocks, or image layers.
+- File-backed Compose secrets retain host ownership on native Linux. The development
+  stack starts a small Node entrypoint as root with `DAC_OVERRIDE`, `SETUID`, and
+  `SETGID`, reads one granted secret, then drops supplementary groups and UID/GID to
+  1000 before it imports the gateway. The final process has no effective capabilities
+  and cannot regain them under `no-new-privileges`. The fixed runtime-bootstrap job
+  keeps `DAC_OVERRIDE`, `SETUID`, and `SETGID` while it reads its two secrets, then runs
+  `psql` as the PostgreSQL account. It rejects runtime passwords shorter than 32
+  characters.
 - Treat client backend files, enrollment files, archives, and DR bundles as secrets.
 - Sanitize `doctor` output and logs before sharing them publicly.
+
+A Docker volume provides persistence, not backup. Keep verified native DR bundles on a
+separate failure domain with retention and restore drills appropriate to the deployment.

package/SKILL.md

@@ -7,6 +7,11 @@ description: Share context and reliable work between agents across runtimes and
 
 Discover the active v2 operation contract with MCP `capabilities`, CLI `agent-bridge capabilities`, or authenticated `GET /v2/capabilities`. Released 2.0 clients continue to work after the gateway is upgraded. A new 2.1 client must receive complete, consistent negotiation headers that select and advertise 2.1 before it mutates remote state. If the probe is headerless, selects 2.0, or returns partial or contradictory headers, do not mutate. Upgrade the gateway first instead of downgrading the client.
 
+An authenticated PostgreSQL gateway status response can include `gatewayAuthorityId`
+and `credentialId`. They are additive in HTTP 2.1. `clients migrate cutover`
+requires and validates both fields before it switches a managed gateway endpoint.
+Do not switch an endpoint by editing its backend file.
+
 Use the Agent Bridge MCP tools for normal traffic. Let the active runtime supply its own identity. Do not pass a literal source unless a standalone CLI process has no configured identity.
 
 If the MCP server is unavailable or disconnects, report the outage instead of implying
@@ -34,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.
 
@@ -51,6 +60,104 @@ If a crash leaves the adjacent enrollment lock, wait at least 60 seconds and pas
 `--recover-lock` with the resume or install command. Recovery must prove that the
 same-host process recorded in the lock has stopped. Never remove the lock manually.
 
+Before Agent Bridge takes lifecycle ownership of an existing Codex, Claude Code, or
+Claude Desktop registration, run `agent-bridge clients inspect <runtime>` with its
+exact `--identity`, stable `--instance`, and absolute `--backend-config` path. Supply
+the installed command and Claude Code scope when they differ from defaults. Treat
+`drifted` as a stop condition. `agent-bridge clients adopt` returns a plan by default;
+only add `--apply` after reviewing an exact `unmanaged` result. Adoption writes
+credential-free owner-private metadata only. It does not rewrite the MCP registration
+or backend file, and inspection never returns backend values or contacts the gateway.
+Desktop adoption records the normalized config path. Codex adoption records the active
+profile config. Run Claude Code local or project adoption from the directory that
+later lifecycle operations should use; the native CLI exposes no stronger target.
+The backend and its immediate parent must already pass the owner-only no-link policy.
+Treat registration state separately from connectivity health; applied adoption
+re-inspects the registration before it reports success. Enrollment-based first-time
+provisioning continues to refuse registration and backend-file collisions.
+Use `agent-bridge clients operations` or append an operation UUID to inspect local
+crash-safe operation state. Artifact contents remain confined to owner-private files;
+inspection reports resumable, classification-required, blocked, or complete and names
+the exact pending step only. Begin is lock-covered, resume is same-host only, and
+ordered steps use no-replace before and verified after artifacts. Treat corrupt,
+cross-host, or ambiguous state as a stop condition. Cleanup is restartable per artifact
+and `committed` means verified writes plus removed artifacts. The terminal manifest
+keeps a credential-free completion record but no request, step, digest, locator, or
+artifact metadata.
+
+For a managed registration, use `clients repair <runtime> --identity <name> --instance
+<key>` to preview its recorded launch contract and backend privacy repair. Add `--apply`
+only after reviewing the plan. Use `clients update` with the same metadata-selected
+runtime and instance to validate a replacement launch contract. The same identity must
+match the stored metadata and the immutable request. Native commands are one executable
+contract. Do not pass arguments, URLs, or credential selectors in `--command`. Repair, update, and uninstall reject
+`--backend-config`, `--scope`, and `--config-path`; `--identity` is an assertion, not a
+locator. A no-op exact registration creates no journal. Native updates remove, prove
+absence, add, and prove the target before metadata changes. Desktop updates replace only
+the Agent Bridge entry and retain unrelated JSON values in memory. It publishes through
+a private operation-scoped temporary file. A concurrent same-user Desktop writer can
+still race this advisory single-file update because Node cannot provide an OS transaction.
+
+Use `clients uninstall <runtime> --identity <name> --instance <key>` to preview a
+forward-only removal. With `--apply`, it proves and removes the managed registration,
+deletes the already private backend file, then deletes metadata. It refuses a backend
+that needs privacy repair and never recreates an earlier target after a later failure.
+Desktop removes only its Agent Bridge entry. Backend content never enters the journal.
+
+Use `clients rollback <update-operation-id> --identity <name>` to inspect an explicit
+reverse plan for a committed same-host v4 update. Add `--apply` only after reviewing
+that plan. The source record retains only prior nonsecret managed metadata, its exact
+registration contract, and forward-state digests. Rollback verifies those digests
+against the current registration, then creates a separate reverse journal. Native
+rollback removes the forward entry, adds the prior entry, and writes prior metadata
+last. Claude Desktop replaces only its Agent Bridge entry and preserves unrelated JSON.
+Repair has no rollback. Uninstall remains forward-only, so recovery is re-enrollment.
+
+Use `clients migrate stage <runtime> --identity <name> --instance <key>
+--enrollment-file <path>` to review a gateway successor prepared from a non-immediate
+rotation enrollment. Add `--apply` only after reviewing the plan. Staging writes a
+private successor backend and a credential-free operation record. It leaves the active
+registration and active backend unchanged. It initializes the source edge gate but
+leaves that gate active. It does not drain, cut over, or prove that two gateway URLs
+reach the same database authority. The source backend must use an absolute, normalized
+edge database path, not `:memory:`. Resume an interrupted stage with `clients resume
+<operation-id> [--recover-lock]`. Use lock
+recovery only after the recorded same-host process has stopped. Never remove a lock
+manually.
+
+Use `clients migrate cutover <stage-operation-id> --exclusive-edge` to inspect the
+host switch. Add `--apply` only after checking the plan. The applied command requires
+an active source edge and an active empty target edge. It verifies both HTTP 2.1
+gateways against the recorded workspace, principal, credential IDs, and authority ID.
+It also requires the successor `status:read` and `messages:write` grants, then completes
+a direct predecessor-to-successor route challenge. Once its journal exists, it uses the
+retained normalized source URL with the successor credential for route proofs and
+source-edge replay through the target gateway. It leases and drains the source edge to
+exact zero outbox work before changing a host registration. Native clients remove the
+source and add the target. Claude Desktop replaces its one Agent Bridge entry. Managed
+metadata changes last. The command rechecks gateway authority and the source lease
+before each host write.
+
+Every phase needs `--exclusive-edge`. Agent Bridge verifies the managed registrations
+that share the edge file, including hardlink aliases. It cannot enumerate unmanaged
+publishers, so the operator must assert that cohort is exclusive. `clients migrate
+finalize <cutover-operation-id> --exclusive-edge --apply` works after
+grace expires and retires the source edge. To return to a previous endpoint, rotate a
+new owner credential and cut forward to it as a new successor. Resume any interrupted
+v6 phase with `clients resume <operation-id> [--recover-lock]`. A new worker must wait
+for the held drain lease to expire. Dry planning never contacts a gateway or writes
+SQLite. It refuses an edge with live WAL sidecars rather than read stale outbox state.
+
+Resume an action-specific operation with the same action, runtime, instance, and
+identity: `--apply --resume <uuid>`. The stored request controls resume. Do not supply
+a new command unless it exactly matches the recorded update request. Use
+`clients resume <uuid> [--recover-lock]` to resume from a recorded v3, supported v4,
+v5 migration-stage, or v6 endpoint-migration request alone. It does not accept
+replacement client authority. Use the generic form after uninstall has
+deleted metadata. `--recover-lock` on an action-specific command also requires
+`--apply`; it only recovers a stale same-host lock after process-death proof. Never
+remove operation locks by hand.
+
 Portable archive work is an offline operator task, not normal MCP traffic. Use
 `agent-bridge archive export --provider local|postgres --workspace <workspace>
 --output <file>` to create an archive, then run `agent-bridge archive verify --file

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-Bfd3hRId.js';
-import './bridge-store-DPVSCwfs.js';
+import { P as PgQueryable } from './postgres-bridge-store-C9KG9Z69.js';
+import './bridge-store-ByJ6CaJk.js';
 
 interface PortableArchiveMessage {
     id: string;

package/dist/archive.js

@@ -21,8 +21,8 @@ import {
   streamPortableArchive,
   validateArchiveWorkspace,
   validatePortableArchiveRequestId
-} from "./chunk-A6W4QALF.js";
-import "./chunk-NCO7RLBM.js";
+} from "./chunk-TC6A7GMF.js";
+import "./chunk-GTK4KOED.js";
 import "./chunk-BZLMF5O5.js";
 export {
   PORTABLE_ARCHIVE_BATCH_BYTES,

package/dist/{bridge-service-hX1ZQp4W.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-DPVSCwfs.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-DPVSCwfs.d.ts → bridge-store-ByJ6CaJk.d.ts}

@@ -35,6 +35,8 @@ interface BridgeDiagnostics {
     expiredLeases?: number | null;
     oldestDueAt?: string;
     queueLagMs?: number | null;
+    gatewayAuthorityId?: string;
+    credentialId?: string;
     principal?: {
         workspace: string;
         agent: string;
@@ -42,6 +44,7 @@ interface BridgeDiagnostics {
 }
 interface ClaimOptions {
     leaseMs: number;
+    messageId?: string;
     now?: Date;
     maxAttempts?: number;
 }

package/dist/bridge.d.ts

@@ -1,12 +1,13 @@
 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-DPVSCwfs.js';
-export { D as DeliveryEventPage, b as DeliveryPage } from './bridge-store-DPVSCwfs.js';
-export { B as BridgeService, P as PublicMessageQuery } from './bridge-service-hX1ZQp4W.js';
-import { P as PgQueryable } from './postgres-bridge-store-Bfd3hRId.js';
-export { a as PgTransactionClient, b as PostgresBridgeStore } from './postgres-bridge-store-Bfd3hRId.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-CggQ8vTC.js';
-export { CachedMessagePage, EdgeConflictError, EdgeEnqueueResult, EdgeOutboxRecord, EdgeScope, EdgeStats, PendingMessage, SQLiteBridgeStore, SQLiteEdgeStore, SyncDiagnostics, SyncInsertResult, SyncReport, SyncingBridgeStore, SyncingBridgeStoreOptions, edgeMessageFingerprint, edgeScopeKey, isRetryableSyncError, stableIdempotency } from './sqlite.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';
 
 declare class LegacySupabaseError extends Error {
@@ -101,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";
@@ -149,6 +151,21 @@ declare const REQUIRED_MIGRATIONS: readonly [{
 }, {
     readonly version: 16;
     readonly name: "native_dr_fence";
+}, {
+    readonly version: 17;
+    readonly name: "gateway_authority_binding";
+}, {
+    readonly version: 18;
+    readonly name: "endpoint_migration_challenges";
+}, {
+    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>;
@@ -158,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,32 +4,37 @@ import {
   HttpBridgeStore,
   LegacySupabaseError,
   LegacySupabaseRestStore
-} from "./chunk-CEXBMOI5.js";
+} from "./chunk-Z6JP6MYD.js";
 import {
   EdgeConflictError,
+  EdgeMigrationDrainingError,
+  EdgeMigrationLeaseError,
+  EdgeMigrationRetiredError,
   SQLiteEdgeStore,
   SyncingBridgeStore,
   edgeMessageFingerprint,
   edgeScopeKey,
+  inspectEdgeScopeReadOnly,
   isRetryableSyncError,
   stableIdempotency
-} from "./chunk-Q6PPMXJC.js";
+} from "./chunk-SN7PIVDF.js";
 import {
   SQLiteBridgeStore
-} from "./chunk-5GMB3A77.js";
-import "./chunk-NCO7RLBM.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-45BZGB77.js";
+} from "./chunk-QNXHDOJ5.js";
 import "./chunk-VOQIDTCJ.js";
 import {
   PostgresCredentialResolver,
@@ -37,11 +42,11 @@ import {
   createGateway,
   hashCredential,
   safeTokenHashEqual
-} from "./chunk-WAI2IYIQ.js";
+} from "./chunk-P635FAN4.js";
 import {
   BridgeService
-} from "./chunk-4VB44KJU.js";
-import "./chunk-GADH244D.js";
+} from "./chunk-AWE3DFZV.js";
+import "./chunk-E4OWHGUE.js";
 import {
   BridgePrincipalMismatchError,
   BridgeValidationError,
@@ -69,6 +74,9 @@ export {
   BridgeValidationError,
   DeliveryStateConflictError,
   EdgeConflictError,
+  EdgeMigrationDrainingError,
+  EdgeMigrationLeaseError,
+  EdgeMigrationRetiredError,
   HttpBridgeStore,
   LegacySupabaseError,
   LegacySupabaseRestStore,
@@ -89,8 +97,10 @@ export {
   encodeCursor,
   encodeScopedCursor,
   hashCredential,
+  inspectEdgeScopeReadOnly,
   isRetryableSyncError,
   loadMigrationPlan,
+  migrationRecordMatches,
   migrationsReady,
   rowIsolationReady,
   runMigrations,