@creatornader/agent-bridge 0.5.2 → 0.6.1

package/docs/architecture-v2.md

@@ -1,20 +1,26 @@
 # Agent Bridge v2 architecture
 
-Status: living architecture for the 0.4.x package line.
+Status: living architecture for the 0.6.x package line.
 
 ## Product boundary
 
-Agent Bridge is the durable, pull-first mailbox and work-delivery control plane for agents that run in different clients, processes, sessions, and machines. It supports three operating modes: local SQLite, the authenticated PostgreSQL gateway, and the legacy Supabase adapter.
+Agent Bridge lets AI agents message each other and hand off work across clients,
+processes, sessions, and machines. It supports two operating modes: local SQLite and
+the authenticated PostgreSQL gateway.
 
 History visibility is caller-relative. `inbox` is the default and preserves broadcast-plus-targeted visibility; `sent` is source equal to the caller; `all` is their union. Receipt state (`any`, `unread`, `read`) is valid only for inbox and is always evaluated for the authenticated caller. Opaque v2 cursors bind workspace, caller, mailbox, and normalized filters. Readers temporarily accept v1 sequence cursors but emit only v2. After an edge cache contract upgrade, the gateway resets the authoritative pull cursor and replays `all` visibility; the publication outbox is never treated as sent history.
 
-These authorization guarantees apply to local v2 and the authenticated gateway. The legacy Supabase adapter can enforce them only cooperatively because its publishable key can call the underlying PostgREST table and receipt RPC directly.
+These authorization guarantees apply to local v2 and the authenticated gateway.
 
 - Local mode runs without an account or network connection.
 - Shared mode uses a remote service so agents on different machines see the same history and delivery state.
 
 The protocol must support informational context and executable work without treating them as the same thing. A2A and application task semantics sit above Agent Bridge. MCP, CLI, HTTPS, and the Node library are access surfaces. Agent harnesses and host applications use those surfaces through host adapters or direct integration. Optional transports may sit below the core, but they cannot replace authoritative cursor replay or durable delivery state.
 
+Authenticated gateway capabilities identify the running package version. Production
+images also report the Git revision supplied at build time. Deployment checks compare
+both values with the intended release before client rollout or production proof.
+
 [ADR-0001](decisions/0001-protocol-layers-and-acknowledgment-semantics.md) defines these layers and the distinct meanings of receipts, claims, leases, delivery settlement, and external task completion.
 
 [ADR-0002](decisions/0002-canonical-operation-contract-registry.md) defines the canonical cross-surface operation contract, deterministic artifacts, capability discovery, and protocol negotiation.
@@ -29,7 +35,10 @@ PostgreSQL stores shared messages, identities, receipts, deliveries, and migrati
 
 A standalone Agent Bridge API sits between remote clients and PostgreSQL. Clients authenticate to the API with scoped credentials. They do not receive a database password or rely on a shared Supabase publishable key for identity.
 
-Supabase can still host the database. Existing direct PostgREST deployments remain available through an explicitly named legacy adapter while they migrate.
+Supabase can host the database. Agent Bridge 0.6.0 removed the direct PostgREST runtime
+adapter. Historical deployments migrate through the checked-in schema and ordered
+PostgreSQL migrations described in
+[ADR-0005](decisions/0005-retire-direct-supabase-runtime.md).
 
 ### Deployment separates schema and request authority
 
@@ -237,7 +246,7 @@ The v2 envelope uses fields that can be mapped to CloudEvents without changing s
 
 A receipt records that a principal read a message.
 
-A publisher stores an immutable `deliveryPolicy` with each message. Untargeted messages default to mailbox mode. Targeted messages default to leased mode with `maxAttempts: 5`, `retryBaseDelayMs: 1000`, `retryMaxDelayMs: 60000`, and `retryJitterRatio: 0.2`. Leased policy may also set `notBefore`. Mailbox messages create no deliveries, and legacy mode rejects leased policy.
+A publisher stores an immutable `deliveryPolicy` with each message. Untargeted messages default to mailbox mode. Targeted messages default to leased mode with `maxAttempts: 5`, `retryBaseDelayMs: 1000`, `retryMaxDelayMs: 60000`, and `retryJitterRatio: 0.2`. Leased policy may also set `notBefore`. Mailbox messages create no deliveries.
 
 A leased delivery records executable work for a recipient. Its state is one of `pending`, `claimed`, `acked`, `retrying`, `dead`, or `cancelled`. `attempt` is lifetime-monotonic, while `cycleAttempt` resets on publisher requeue and `requeueCount` increments. Stored policy owns retry and exhaustion. Claims order due work by urgent, high, then info priority, followed by availability, message creation time, and the stable delivery ID tie-break. HTTP 2.1, MCP, and CLI may optionally identify one message. That form atomically selects only the eligible delivery for the authenticated recipient and scopes claim-time expiry and exhaustion maintenance to the same message. Omitting the filter preserves claim-next behavior. The frozen HTTP 2.0 request rejects the additive field.
 
@@ -253,7 +262,9 @@ The system promises at-least-once delivery. It does not promise exactly-once exe
 
 Project participates in the idempotency fingerprint. Reads without a project filter span labeled and unlabeled messages inside the credential-bound workspace. An exact filter narrows that same cursor authority. Migration 008 adds the PostgreSQL column and index. Existing local and edge SQLite databases add their project columns during initialization. Migration 006 is not rewritten. A schema-owner command dry-runs or reconciles its rows into workspace `agent-bridge` in one transaction. It preserves IDs, timestamps, receipts, and row counts, and it verifies that no delivery exists before or after the change.
 
-The legacy Supabase schema has no tenant workspace column. Its adapter reports workspace `*` and uses the legacy `project` column only as a message label. It rejects per-command workspace overrides because assigning a caller-selected workspace to global rows would create a false isolation boundary.
+The historical Supabase schema has no tenant workspace column. Migration 006 maps its
+global rows into canonical workspaces before gateway activation. A caller cannot use
+the retired runtime shape to assign a workspace to those rows.
 
 The delivery API supports:
 
@@ -274,9 +285,9 @@ Reads use an opaque cursor backed by the backend sequence number. UUIDv7 improve
 
 During gateway outages, normal inbox and pending reads return the locally cached candidate set with explicit degraded and stale metadata. Because receipt state is remote authority and is not mirrored, an offline `unacknowledgedBy` result reports acknowledgement state as unknown; it must not be interpreted as proof that every returned message is unread.
 
-Realtime, hooks, webhooks, and desktop notifications may wake a client. The client still pulls from its last durable cursor. This closes notification gaps and makes reconnect behavior testable.
-
-Supabase documents that Realtime does not guarantee every database change. Agent Bridge therefore treats it as an optional delivery hint, not a message log.
+Hooks, webhooks, and desktop notifications may wake a client. The client still pulls
+from its last durable cursor. This closes notification gaps and makes reconnect
+behavior testable.
 
 ### Identity is bound at the client boundary
 
@@ -311,7 +322,6 @@ Protocol logic depends on a `BridgeStore` interface, not a provider SDK. The ini
 
 - SQLite for local mode and edge state.
 - PostgreSQL for a standalone shared deployment.
-- Supabase legacy REST for v1 compatibility during migration.
 - Agent Bridge HTTP API for normal remote clients.
 
 Host and wakeup adapters are independent from storage. A client manifest declares identity injection, supported wake modes, config locations, health checks, and install actions for Codex, Claude Code, Claude Desktop, OpenClaw, or a generic MCP client. The v1 manifest key named `runtime` identifies an installation target for compatibility. It does not identify a unique running process. The `codex` adapter configures the profile shared by the Codex CLI and the Codex surface in the ChatGPT desktop app. Scripts, CI jobs, daemons, and application services may instead call the CLI or HTTPS API or embed the Node library without pretending to be a harness adapter.
@@ -503,11 +513,14 @@ because an immutable read could miss uncheckpointed outbox state.
 
 The MCP tools `post_context`, `get_context`, and `ack_context` remain available. Existing CLI verbs and flags remain accepted. Text responses remain present while v2 adds structured result data.
 
-Legacy Supabase rows remain readable as broadcast messages. A migration command checks schema state, backfills v2 records, and verifies counts before activation. Secure shared mode cannot silently inherit the old permissive RLS policies.
+Migration 006 checks the historical Supabase schema, imports v1 records, and verifies
+counts before activation. The reconciliation command can correct imported project
+labels without reopening the retired runtime adapter. Secure shared mode cannot
+silently inherit the old permissive RLS policies.
 
 ## Security boundary
 
-Shared mode uses a token-authenticated API. The service stores only token hashes. Credentials bind a workspace and principal, carry canonical operation scopes, can expire, and can be revoked. Capabilities requires an active credential but no named scope. Local and legacy providers do not claim gateway scope enforcement.
+Shared mode uses a token-authenticated API. The service stores only token hashes. Credentials bind a workspace and principal, carry canonical operation scopes, can expire, and can be revoked. Capabilities requires an active credential but no named scope. Local mode does not claim gateway scope enforcement.
 
 Migration 011 grants every pre-migration credential the full compatibility scope set, including expired and revoked rows, without rewriting lifecycle metadata. Migration 014 preserves those rows but changes new raw inserts to empty scopes. Owner provisioning selects an immutable named scope set. Database constraints reject unknown, duplicated, or unsorted scopes.
 
@@ -640,7 +653,7 @@ The TypeBox 1.x registry validates closed requests before domain semantics. Resp
 
 Compatibility is asymmetric. An upgraded gateway serves released headerless and explicit 2.0 clients. A new 2.1 client probes before mutation and accepts the gateway only when complete, consistent response headers select 2.1 and advertise 2.1 support. A headerless response, selected 2.0 response, or partial negotiation means the gateway must be upgraded. The client rejects mutation instead of using the d8184fe 2.0 contract. Deploy the gateway before 2.1 clients.
 
-The OpenAPI paths describe protocol 2.1. Embedded 2.0 vendor extensions carry only the frozen compatibility schemas and metadata needed to document released clients; they do not form a second OpenAPI description. `npm run contracts:check` proves that JSON Schema 2020-12, OpenAPI 3.1.2, MCP manifest, and capability artifacts match the registry. All schema references are local. Protocol, npm package, MCP implementation, and migration versions are independent. Gateway scope enforcement comes from the registry. Provider-neutral artifacts report enforcement separately for gateway, local, and legacy modes.
+The OpenAPI paths describe protocol 2.1. Embedded 2.0 vendor extensions carry only the frozen compatibility schemas and metadata needed to document released clients; they do not form a second OpenAPI description. `npm run contracts:check` proves that JSON Schema 2020-12, OpenAPI 3.1.2, MCP manifest, and capability artifacts match the registry. All schema references are local. Protocol, npm package, MCP implementation, and migration versions are independent. Gateway scope enforcement comes from the registry. Provider-neutral artifacts report enforcement separately for gateway and local modes.
 
 The v2 implementation is not accepted until all of these checks pass:
 
@@ -670,7 +683,6 @@ End-to-end payload encryption needs a separate threat model and key-management d
 - SQLite WAL-reset bug: <https://sqlite.org/forum/forumpost/0b7fd7f028>
 - PostgreSQL row locking and `SKIP LOCKED`: <https://www.postgresql.org/docs/current/sql-select.html#SQL-FOR-UPDATE-SHARE>
 - Supabase self-hosting responsibilities: <https://supabase.com/docs/guides/self-hosting>
-- Supabase Realtime delivery limitations: <https://supabase.com/docs/reference/self-hosting-realtime>
 - MCP tools specification: <https://modelcontextprotocol.io/specification/2025-11-25/server/tools>
 - MCP transport specification: <https://modelcontextprotocol.io/specification/2025-11-25/basic/transports>
 - UUIDv7: <https://www.rfc-editor.org/rfc/rfc9562.html#name-uuid-version-7>

package/docs/decisions/0001-protocol-layers-and-acknowledgment-semantics.md

@@ -16,7 +16,8 @@ Agent Bridge needs to serve agents across clients, sessions, processes, and mach
 
 ## Decision
 
-Agent Bridge is the durable, pull-first mailbox and work-delivery control plane for intermittently connected agent runtimes.
+Agent Bridge provides messaging and work delivery for intermittently connected agent
+runtimes across tools, sessions, and machines.
 
 Its protocol owns:
 

package/docs/decisions/0002-canonical-operation-contract-registry.md

@@ -26,7 +26,16 @@ Compatibility runs in the other direction. An upgraded gateway continues to serv
 
 The OpenAPI paths require protocol 2.1. The `x-agent-bridge-protocol-2.0` and `x-agent-bridge-schemas-2.0` vendor extensions provide limited metadata and frozen schemas for the released compatibility contract. They do not define a second set of paths or a separate OpenAPI description.
 
-Capability documents are filtered by surface and provider. HTTP capability discovery requires a valid credential but has no named scope. The exact scope names are reserved metadata until a later security migration. Gateway credentials grant access as a whole, local mode uses process identity, and legacy mode uses its configured key. Capability documents and OpenAPI set `scopeEnforcement` to false.
+Capability documents are filtered by surface and provider. HTTP capability discovery
+requires a valid credential but no named scope. Gateway operations enforce the scopes
+declared by the registry, while local mode uses process identity and reports scope
+enforcement as false. [ADR-0005](0005-retire-direct-supabase-runtime.md) removed the
+legacy runtime provider from this contract.
+
+Authenticated gateway capability documents may also identify the running package
+version and image Git revision. These implementation fields are independent of the
+HTTP protocol version. Deployment gates compare them with the intended release so a
+healthy but stale gateway cannot pass release proof.
 
 Package version, MCP implementation version, Agent Bridge protocol version, and migration version remain independent. The MCP server reports the explicit `MCP_IMPLEMENTATION_VERSION` constant instead of the npm package version.
 
@@ -42,5 +51,6 @@ Package version, MCP implementation version, Agent Bridge protocol version, and
 ## Related
 
 - [ADR-0001](0001-protocol-layers-and-acknowledgment-semantics.md) defines the protocol layers and acknowledgment meanings.
+- [ADR-0005](0005-retire-direct-supabase-runtime.md) removes the direct Supabase runtime provider.
 - [Architecture v2](../architecture-v2.md) describes the system that follows these decisions.
 - The [README](../../README.md) documents public setup and upgrade behavior.

package/docs/decisions/0005-retire-direct-supabase-runtime.md

@@ -0,0 +1,52 @@
+# ADR-0005: Retire the direct Supabase runtime
+
+Status: accepted
+
+Date: 2026-07-21
+
+## Context
+
+Early Agent Bridge releases could read and write `public.shared_context` through
+Supabase PostgREST with a publishable key. That adapter kept the first deployment
+working while the canonical protocol and gateway were built.
+
+The adapter could not provide the gateway's security or delivery model. Its shared key
+did not bind a principal or workspace. Its schema had no delivery leases, offline
+outbox, presence, scoped credentials, or transaction-bound request authority. Keeping
+it as a runtime provider also made every public contract describe a weaker third mode.
+
+Supabase remains a useful managed PostgreSQL host. The problem is the direct client API,
+not the database service.
+
+## Decision
+
+Agent Bridge 0.6.0 supports two runtime providers:
+
+- `local`, backed by SQLite.
+- `gateway`, backed by an authenticated Agent Bridge gateway with PostgreSQL authority
+  and a local SQLite edge store.
+
+The package no longer exports or constructs the direct Supabase store. It rejects
+`legacy`, `supabase`, `legacy-supabase`, and key-only configurations with an upgrade
+message.
+
+Historical migration support remains:
+
+- `sql/setup.sql` records the v1 schema shape.
+- Migration 006 imports `public.shared_context` rows and receipts.
+- `reconcile-legacy-projects` repairs the imported workspace and project mapping.
+- Released HTTP 2.0 and MCP compatibility tools remain independent protocol contracts.
+
+## Consequences
+
+Remote clients now use one authenticated boundary and one capability model. Supabase
+deployments can continue to host the canonical PostgreSQL database without exposing
+PostgREST to Agent Bridge clients.
+
+Operators upgrading an old direct deployment must preserve the source, run the
+historical import, provision principal-bound gateway credentials, and change client
+configuration before installing 0.6.0. A running direct client cannot upgrade in place
+without that provider change.
+
+The removed adapter is not a promise to delete historical migration code. Migration
+fixtures remain until the project adopts an explicit migration-support window.

package/docs/deployment.md

@@ -229,11 +229,29 @@ repository does not perform them:
    match the recorded runtime contract. It never adopts a restored `NOLOGIN` shell.
 6. Construct the restricted runtime URL. Import it and the base64-encoded PostgreSQL CA
    as the two runtime secrets shown above, then run the app-aware read-only preflight.
-7. Deploy the immutable image with `fly deploy --config deploy/fly.toml --app <app>`.
+7. Deploy the immutable image with its source revision:
+
+   ```bash
+   fly deploy --config deploy/fly.toml --app <app> \
+     --build-arg AGENT_BRIDGE_BUILD_REVISION="$(git rev-parse HEAD)"
+   ```
+
    Require `/readyz` before routing clients.
-8. Run authenticated capability and status probes, then publish, pull, claim, and
+8. Check the running package and source revision with a principal-bound credential:
+
+   ```bash
+   AGENT_BRIDGE_URL="https://<app>.fly.dev" AGENT_BRIDGE_TOKEN="..." \
+     npm run verify:gateway:release -- \
+     --version "$(node -p "require('./package.json').version")" \
+     --revision "$(git rev-parse HEAD)"
+   ```
+
+   The check also requires protocol 2.1, request authority, and row isolation. It
+   fails if the deployed image omits its revision or differs from the intended
+   release.
+9. Run authenticated status, publication, pull, claim, and
    settle a disposable targeted delivery.
-9. Move clients only after the gateway proof passes. Preserve every source edge store
+10. Move clients only after the gateway proof passes. Preserve every source edge store
    until its outbox is empty.
 
 App creation, database provisioning, secret writes, migration, bootstrap, deployment,
@@ -264,25 +282,30 @@ sender credential needs `messages:write` and `messages:read`. The receiver needs
 
 Run the workflow only when the Fly app has exactly one gateway machine. The cycle job
 restarts that machine and queries the Fly Machines API before and after. It fails
-unless the machine ID stays fixed, the runtime `instance_id` changes, the machine
-returns to `started`, and `/readyz` succeeds. This changes production compute and
-requires environment approval. It does not migrate the database or change secrets.
-
-The sender first uses an unreachable loopback origin to force a leased publication
-into its private SQLite outbox. It then synchronizes that row to the supplied gateway
-and repeats the publication with the same idempotency key. A separate host finds the
-exact message through `proof-receiver`, claims its delivery, and acknowledges it.
+unless the machine ID stays fixed, a later successful `start` event appears, the
+machine returns to `started`, and `/readyz` succeeds. Fly documents `instance_id` as a
+version changed by machine updates; a plain restart need not change it. This operation
+changes production compute and requires environment approval. It does not migrate the
+database or change secrets.
+
+The sender first writes a leased publication to its private SQLite outbox without a
+network request. It then synchronizes that row to the supplied gateway and repeats the
+publication with the same idempotency key. The gateway origin, workspace, and principal
+scope stay unchanged. A separate host finds the exact message through `proof-receiver`,
+claims its delivery, and acknowledges it.
 After the Fly machine cycle, the verifier uses a fresh instance key, edge database,
 and cursor. It reads the immutable message and confirms that the prior delivery is
-still `acked`.
+still `acked`. The sender and receiver host evidence must differ. GitHub may reuse the
+sender's hosted runner for the verifier, so the verifier proves fresh local state rather
+than requiring a third physical host.
 
 Each phase writes an `agent-bridge-production-proof-v1` receipt. The runner rejects
 unknown fields at the phase boundary and checks every receipt before use. Receipts may
 record IDs, timestamps, principal and workspace labels, the gateway origin, boolean
 checks, and salted SHA-256 host evidence. They never record bearer values, database
-URLs, environment values, message content, lease tokens, cursor files, or edge
-databases. Download all four workflow artifacts for the operator record. A passing
-repository test still does not replace a completed external workflow run.
+URLs, secret-bearing environment values, message content, lease tokens, cursor files,
+or edge databases. Download all four workflow artifacts for the operator record. A
+passing repository test still does not replace a completed external workflow run.
 
 ### Persistent data and backup
 
@@ -313,8 +336,9 @@ owner-control state, or security events.
 5. Stop schema-changing jobs other than the selected migration job.
 6. Run the new image's migration command once with schema-owner authority.
 7. Run the runtime bootstrap with separate runtime-login credentials.
-8. Start the new gateway and require `/readyz`, an authenticated capability probe, and
-   an authenticated status probe.
+8. Start the new gateway and require `/readyz`. Run
+   `npm run verify:gateway:release` against the expected package version and Git
+   revision, then run an authenticated status probe.
 9. Send, read, claim, and settle a disposable targeted delivery.
 10. Roll clients forward only after the gateway proof passes.
 11. Keep the previous authority available but inactive until the observation window

package/docs/ecosystem.md

@@ -1,9 +1,9 @@
 # Agent Bridge in the agent ecosystem
 
-Agent Bridge is a durable mailbox and work-delivery control plane for agent runtimes
-that may disconnect, restart, or move between machines. It stores immutable messages,
-read receipts, delivery claims, leases, retries, and replay state. It does not own the
-full agent stack.
+Agent Bridge lets AI agents message each other and hand off work across tools,
+sessions, and machines. Messages wait through disconnections and restarts. It stores
+immutable messages, read receipts, delivery claims, leases, retries, and replay state.
+It does not own the full agent stack.
 
 ## System boundaries
 
@@ -21,6 +21,8 @@ defines the protocol boundary and the separate meanings of read receipts, delive
 settlement, and external task completion.
 [ADR-0003](decisions/0003-host-adapters-and-consumer-instance-keys.md) defines
 the host layers and consumer instance-key contract.
+[ADR-0005](decisions/0005-retire-direct-supabase-runtime.md) keeps Supabase as a
+PostgreSQL hosting option while removing its direct runtime adapter.
 
 ## Harnesses, hosts, adapters, and access
 

package/docs/troubleshooting.md

@@ -81,6 +81,21 @@ Queued sends retain their idempotency keys. Long-lived MCP clients retry them, a
 `agent-bridge sync` triggers the same bounded replay manually. Claims, lease changes,
 delivery settlement, presence, and read-receipt writes still require the gateway.
 
+## Legacy Supabase provider was removed
+
+Agent Bridge 0.6.0 rejects `legacy`, `supabase`, `legacy-supabase`, and key-only
+configurations. These names selected the direct PostgREST adapter in older releases.
+Choose local mode for one machine or create a principal-bound gateway backend:
+
+```bash
+agent-bridge init --provider local
+```
+
+Do not point new clients at `public.shared_context`. If the old table still contains
+data that has not been migrated, preserve it and follow the historical import and
+reconciliation steps in the
+[README](../README.md#upgrading-historical-supabase-deployments).
+
 ## Migration gate reported by status or doctor
 
 `clients migrate stage` does not begin a drain. `clients migrate cutover

package/llms.txt

@@ -3,7 +3,7 @@
 Repository: https://github.com/creatornader/agent-bridge
 Package: @creatornader/agent-bridge
 
-Agent Bridge is a durable, pull-first mailbox and work-delivery control plane for AI agents in different clients, processes, sessions, and machines.
+Agent Bridge lets AI agents message each other and hand off work across tools, sessions, and machines. Messages wait while an agent is offline and are still there after it restarts.
 History uses mailbox `inbox` (default), `sent`, or `all`. Receipt state is `any` (default), `unread`, or `read`; it is caller-relative and inbox-only. CLI: `inbox`, `sent`, and `history --mailbox/--receipt-state`. Deprecated unacked-principal arguments must equal the configured identity.
 
 ## Install
@@ -29,7 +29,6 @@ services can call the CLI or HTTPS API or embed the Node library without a host
 
 - local: SQLite WAL, no account or daemon
 - gateway: authenticated HTTPS, PostgreSQL authority, SQLite edge outbox and cache
-- legacy-supabase: compatibility with the v1 shared_context schema
 
 ## Commands
 
@@ -123,7 +122,7 @@ one logical authority across restore but does not fence a live clone.
 
 ## MCP tools
 
-- `capabilities`: return operations, required scopes, provider-specific enforcement, and supported protocol versions. Gateway access needs an active credential but no named scope for this operation.
+- `capabilities`: return operations, required scopes, provider-specific enforcement, supported protocol versions, and optional implementation version and revision metadata. Gateway access needs an active credential but no named scope for this operation.
 - Production gateway capabilities report `requestAuthority: true` and `rowIsolation: true` only after the migration and live catalog, role, policy, privilege, and function checks pass. PostgreSQL forces RLS on messages, receipts, deliveries, delivery events, and presence. Lease transitions and target-to-delivery membership remain service-enforced.
 - Authenticated gateway `/v2/status` returns optional `gatewayAuthorityId` and
   `credentialId` fields when PostgreSQL request authority is active. They are additive
@@ -190,7 +189,7 @@ sidecars rather than read uncheckpointed outbox state. Resume uses only the reta
 request and waits for an unexpired drain lease instead of taking it over.
 
 Project is an optional immutable message label, not a tenant or identity selector. Omitted project reads include labeled and unlabeled messages. Exact project filters are supported by CLI, MCP, HTTP, and stores. Gateway workspace assertions must match the bound credential before network access.
-Local CLI calls may override workspace for one invocation. The legacy Supabase schema is global and always reports workspace `*`; use project labels for legacy filtering.
+Local CLI calls may override workspace for one invocation. Agent Bridge 0.6.0 removed the direct Supabase runtime adapter; the historical schema and migration import remain for upgrades.
 
 ## References
 
@@ -203,6 +202,7 @@ Local CLI calls may override workspace for one invocation. The legacy Supabase s
 - docs/decisions/0001-protocol-layers-and-acknowledgment-semantics.md: protocol layers and acknowledgment semantics
 - docs/decisions/0002-canonical-operation-contract-registry.md: generated contracts and version negotiation
 - docs/decisions/0003-host-adapters-and-consumer-instance-keys.md: host layers and instance-key semantics
+- docs/decisions/0005-retire-direct-supabase-runtime.md: runtime-provider retirement and migration boundary
 - docs/architecture-v2.md: protocol, storage, identity, delivery, and acceptance decisions
 - clients/*.json: v1 host-adapter manifests; `runtime` is the compatibility key for the installation target
 - SKILL.md: concise agent operating instructions

package/openapi/agent-bridge-v2.openapi.json

@@ -2,6 +2,7 @@
   "openapi": "3.1.2",
   "info": {
     "title": "Agent Bridge Gateway",
+    "description": "Let AI agents message each other and hand off work across tools, sessions, and machines.",
     "version": "2.1",
     "license": {
       "name": "Apache-2.0",
@@ -331,8 +332,7 @@
                       "enum": [
                         "scoped-credential",
                         "credential-wide",
-                        "process-identity",
-                        "legacy-key"
+                        "process-identity"
                       ]
                     },
                     "surface": {
@@ -345,10 +345,16 @@
                     "provider": {
                       "enum": [
                         "local",
-                        "gateway",
-                        "legacy-supabase"
+                        "gateway"
                       ]
                     },
+                    "implementationVersion": {
+                      "type": "string"
+                    },
+                    "implementationRevision": {
+                      "type": "string",
+                      "pattern": "^[0-9a-f]{7,40}$"
+                    },
                     "grantedScopes": {
                       "type": "array",
                       "items": {
@@ -849,8 +855,7 @@
                     "schemaVersion": {
                       "enum": [
                         "local-v2",
-                        "postgres-v2",
-                        "legacy-v1"
+                        "postgres-v2"
                       ]
                     },
                     "deliverySupported": {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@creatornader/agent-bridge",
-  "version": "0.5.2",
-  "description": "Durable, pull-first mailbox and work-delivery control plane for AI agents across runtimes, sessions, and machines.",
+  "version": "0.6.1",
+  "description": "Let AI agents message each other and hand off work across tools, sessions, and machines.",
   "type": "module",
   "license": "Apache-2.0",
   "author": "Nader Helmy",
@@ -29,6 +29,7 @@
     "schemas",
     "openapi",
     "docs",
+    "scripts/gateway-release-check.mjs",
     "sql/migrations",
     "sql/setup.sql",
     "llms.txt",
@@ -87,12 +88,13 @@
     "pretest": "npm run build",
     "test": "vitest run",
     "test:built": "vitest run",
-    "test:postgres:contract": "vitest run test/postgres_integration.test.ts --maxWorkers=1 --hookTimeout=60000",
+    "test:postgres:contract": "vitest run test/postgres_integration.test.ts --maxWorkers=1 --testTimeout=30000 --hookTimeout=60000",
     "test:postgres:preflight": "node scripts/postgres-preflight.mjs",
     "test:postgres:preflight:full": "node scripts/postgres-preflight.mjs --full",
     "preflight:postgres:production": "npm run build --silent && node dist/postgres-production-preflight.js",
     "preflight:fly": "node scripts/fly-production-preflight.mjs",
     "proof:gateway:production": "node scripts/gateway-production-proof.mjs",
+    "verify:gateway:release": "node scripts/gateway-release-check.mjs",
     "test:gateway:production-proof": "vitest run test/gateway-production-proof.test.ts",
     "test:windows:contract": "vitest run test/private-path.test.ts test/windows-native-smoke.test.ts --maxWorkers=1 --testTimeout=180000 -t \"applies and verifies native Windows file and directory ACLs|recovers an (enrollment|client-operation) subsystem lock\" && vitest run test/client-maintenance.test.ts --maxWorkers=1 --testTimeout=180000",
     "typecheck": "tsc --noEmit",

package/schemas/agent-bridge-v2.capabilities.json

@@ -70,8 +70,7 @@
               "enum": [
                 "scoped-credential",
                 "credential-wide",
-                "process-identity",
-                "legacy-key"
+                "process-identity"
               ]
             },
             "surface": {
@@ -84,10 +83,16 @@
             "provider": {
               "enum": [
                 "local",
-                "gateway",
-                "legacy-supabase"
+                "gateway"
               ]
             },
+            "implementationVersion": {
+              "type": "string"
+            },
+            "implementationRevision": {
+              "type": "string",
+              "pattern": "^[0-9a-f]{7,40}$"
+            },
             "grantedScopes": {
               "type": "array",
               "items": {
@@ -219,7 +224,8 @@
           "retry-max-ms",
           "retry-jitter",
           "not-before",
-          "message-id"
+          "message-id",
+          "queue-only"
         ],
         "outputSchema": {
           "type": "object",

package/schemas/agent-bridge-v2.mcp.json

@@ -3,8 +3,7 @@
   "protocolVersion": "2.1",
   "scopeEnforcementByProvider": {
     "local": false,
-    "gateway": true,
-    "legacy-supabase": false
+    "gateway": true
   },
   "tools": [
     {
@@ -59,8 +58,7 @@
             "enum": [
               "scoped-credential",
               "credential-wide",
-              "process-identity",
-              "legacy-key"
+              "process-identity"
             ]
           },
           "surface": {
@@ -73,10 +71,16 @@
           "provider": {
             "enum": [
               "local",
-              "gateway",
-              "legacy-supabase"
+              "gateway"
             ]
           },
+          "implementationVersion": {
+            "type": "string"
+          },
+          "implementationRevision": {
+            "type": "string",
+            "pattern": "^[0-9a-f]{7,40}$"
+          },
           "grantedScopes": {
             "type": "array",
             "items": {
@@ -118,8 +122,7 @@
       "requiredScopes": [],
       "providers": [
         "local",
-        "gateway",
-        "legacy-supabase"
+        "gateway"
       ]
     },
     {
@@ -387,8 +390,7 @@
       ],
       "providers": [
         "local",
-        "gateway",
-        "legacy-supabase"
+        "gateway"
       ]
     },
     {
@@ -627,8 +629,7 @@
       ],
       "providers": [
         "local",
-        "gateway",
-        "legacy-supabase"
+        "gateway"
       ]
     },
     {