@creatornader/agent-bridge 0.2.0

package/CHANGELOG.md

@@ -0,0 +1,60 @@
+# Changelog
+
+All notable changes to agent-bridge are documented in this file.
+
+The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.2.0] - 2026-07-14
+
+### Added
+
+- Provider-neutral stores for local SQLite, PostgreSQL, the authenticated HTTP gateway, and legacy Supabase.
+- Immutable v2 messages, opaque cursors, receipts, delivery leases, retries, dead letters, transition history, and leased presence.
+- SQLite gateway outbox, inbox cache, restart-safe synchronization, and explicit stale-cache results.
+- Cross-platform Node CLI with init, health, delivery, sync, presence, watch, migration, and client installation commands.
+- Cheap `pending` process gate for unread context or due delivery work.
+- Runtime manifests and native installers for Codex, Claude Code, and Claude Desktop.
+- Runtime-neutral `SKILL.md` guidance and an `llms.txt` package map.
+- PostgreSQL migrations with checksum validation and runtime schema readiness checks.
+- Restricted PostgreSQL runtime grants separated from schema migration credentials.
+- Linux, macOS, and Windows test matrices, live PostgreSQL tests, and clean tarball installation smoke tests.
+
+### Changed
+
+- Package identity is `@creatornader/agent-bridge` at version `0.2.0`. Tagged package builds are automatic; npm publication remains gated until scope access is confirmed.
+- Agent identity is process-scoped. Shared config no longer supplies `AGENT_BRIDGE_AGENT`.
+- Exact idempotent replays deduplicate. Reusing a key for changed content returns a conflict.
+- Gateway clients authenticate through separate principal-bound credentials stored in owner-only client backend files.
+- Package-root imports expose the provider-neutral API without starting the MCP server.
+- `watch` runs until interrupted and retries transient gateway or legacy provider failures.
+
+### Security
+
+- The v2 PostgreSQL schema is private from Supabase Data API roles.
+- Remote providers require HTTPS except on loopback.
+- Gateway startup validates migration checksums, required objects, credential status, and principal binding.
+- Gateway startup requires a restricted runtime database URL and cannot run schema migrations.
+- Local config and SQLite state use owner-only permissions where the platform supports POSIX modes.
+
+## [0.1.0] - 2026-05-17
+
+First tagged release. Marks the point where agent-bridge has shipped its initial feature set, completed the public-flip prep (Apache 2.0 license, generic integration framing in docs), and integrated the public-OSS-prep tooling stack.
+
+### Added
+
+- MCP server with three tools: `post_context`, `get_context`, `ack_context`. Direct fetch to Supabase REST API (no `@supabase/supabase-js`) so the MCP server and the bash CLI share the same lightweight approach.
+- Bash CLI at `bin/agent-bridge` for shell-based agent integrations.
+- SQL schema (`sql/setup.sql`) with the `shared_context` table, permissive RLS (anon key is the access control), and the `ack_context_atomic` RPC for race-free acknowledgement via `array_append`.
+- Optional `atrib_receipt_id` column for callers that wrap writes behind an atrib signing layer. The column is format-validated and optional; agent-bridge does not require atrib integration.
+- Integration with the public-OSS-prep stack: textleaks pre-commit hook, oss-twin structural mirror gate, oss-security-scan reusable CI workflow.
+
+### Security
+
+- gitleaks + trufflehog + osv-scanner via the reusable workflow at `creatornader/oss-security-scan@v0.1.0`.
+- 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.2.0...HEAD
+[0.2.0]: https://github.com/creatornader/agent-bridge/compare/v0.1.0...v0.2.0

package/LICENSE

@@ -0,0 +1,216 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+   Copyright 2026 Nader Helmy
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied. See the License for the specific language governing
+   permissions and limitations under the License.

package/README.md

@@ -0,0 +1,338 @@
+# Agent Bridge
+
+Agent Bridge is a shared messaging and work-delivery layer for AI agents that run in different clients, processes, sessions, and machines.
+
+It supports three operating modes:
+
+| Mode | Store | Use case |
+| --- | --- | --- |
+| Local | SQLite WAL | One machine, no service or account |
+| Gateway | PostgreSQL plus a local SQLite edge store | Cross-machine messaging, offline sends, claims, retries, and presence |
+| Legacy Supabase | Existing `shared_context` table through PostgREST | Compatibility while a v1 deployment migrates |
+
+PostgreSQL remains the authority in gateway mode. SQLite holds local-only messages or gateway edge state. Supabase is one way to host PostgreSQL, not a protocol dependency.
+
+## What v2 provides
+
+- Immutable messages with UUIDv7 IDs and opaque server cursors.
+- Indexed source, thread, timestamp, workspace, and delivery queries.
+- Read receipts separated from executable delivery state.
+- Atomic claim, lease renewal, acknowledgment, negative acknowledgment, retry, and dead-letter operations.
+- Append-only delivery transition history.
+- Idempotency conflict detection. Exact replay deduplicates; changed content under the same key fails.
+- Scoped credentials that bind a remote workspace and agent principal.
+- SQLite outbox and inbox cache for gateway clients.
+- Leased runtime presence with instance IDs and capabilities.
+- MCP, CLI, Codex, Claude Code, and Claude Desktop integration paths.
+- Existing `post_context`, `get_context`, `ack_context`, `post`, and `get` behavior during migration.
+
+The accepted protocol and storage decisions live in [docs/architecture-v2.md](docs/architecture-v2.md).
+
+## Architecture
+
+```text
+ Codex       Claude Code       Claude Desktop       scripts
+   |              |                  |                 |
+   +--------------+------------------+-----------------+
+                          MCP or CLI
+                              |
+                  process-scoped agent identity
+                              |
+             +----------------+----------------+
+             |                                 |
+       local SQLite                  SQLite edge store
+                                               |
+                                     authenticated HTTPS
+                                               |
+                                      Agent Bridge gateway
+                                               |
+                                          PostgreSQL
+```
+
+Realtime notifications or hooks may wake a client, but cursored reads remain authoritative. A missed notification does not lose a message.
+
+## Requirements
+
+- Node.js 22.23.1 or newer.
+- SQLite 3.51.3 or newer for local and edge storage. The supported Node version includes it.
+- PostgreSQL 15 or newer for gateway mode.
+
+## Install from source
+
+The unscoped npm name belongs to another project. This repository uses `@creatornader/agent-bridge`. The release workflow always builds a tagged package. Publishing remains disabled until the `npm` environment has an approval rule, npm trusts `release.yml` as this package's publisher, and `NPM_PUBLISH_ENABLED` is set to `true`.
+
+```bash
+git clone https://github.com/creatornader/agent-bridge.git
+cd agent-bridge
+npm ci
+npm run build
+npm link
+```
+
+The package exposes three executables:
+
+- `agent-bridge`: CLI.
+- `agent-bridge-mcp`: stdio MCP server.
+- `agent-bridge-gateway`: HTTP gateway.
+
+`npm pack` builds the package before creating a tarball. CI installs that tarball into an empty project, imports the provider-neutral library API, and runs the packaged CLI. Importing the package root does not start the MCP server.
+
+## Local quick start
+
+Initialize backend settings. `init` does not write an agent identity into the shared config.
+
+```bash
+agent-bridge init --provider local
+```
+
+Each client supplies its own identity:
+
+```bash
+AGENT_BRIDGE_AGENT=codex agent-bridge post --category operational "Bridge is ready"
+AGENT_BRIDGE_AGENT=claude-code agent-bridge get --unacked-by claude-code
+```
+
+You can also pass `--source` to a standalone send. If the process already has `AGENT_BRIDGE_AGENT`, an explicit identity must match it.
+
+Run a two-principal local proof:
+
+```bash
+agent-bridge demo
+```
+
+## Install client integrations
+
+Agent identity and gateway credentials belong to each client process, not the shared `~/.agent-bridge/config` file.
+
+```bash
+agent-bridge clients install codex --identity codex
+agent-bridge clients install claude-code --identity claude-code
+agent-bridge clients install claude-desktop --identity claude-desktop
+```
+
+For gateway mode, issue a distinct principal-bound token for each client and pass it only during that client's installation:
+
+```bash
+AGENT_BRIDGE_CLIENT_TOKEN=<codex token> \
+  agent-bridge clients install codex --identity codex
+AGENT_BRIDGE_CLIENT_TOKEN=<claude-code token> \
+  agent-bridge clients install claude-code --identity claude-code
+AGENT_BRIDGE_CLIENT_TOKEN=<claude-desktop token> \
+  agent-bridge clients install claude-desktop --identity claude-desktop
+```
+
+`--token` accepts the same value, but the environment form avoids putting a credential in shell history. Each install writes an owner-only backend file under `~/.agent-bridge/clients/`. The host MCP registration receives that file path, the client identity, and a generated instance ID. Tokens are not copied into the shared config, and one client cannot reuse a token bound to another principal.
+
+Codex and Claude Code installation uses their native MCP commands. Claude Desktop installation merges the `agent-bridge` server into its JSON config with an atomic write. Restart the client after installation.
+
+The runtime contracts are under [`clients/`](clients/). OpenClaw and generic MCP manifests declare the required environment variable and command but leave config mutation to the operator because their host config shapes vary.
+
+[`SKILL.md`](SKILL.md) provides concise runtime-neutral operating instructions for agents. [`llms.txt`](llms.txt) gives tools and model crawlers a compact map of the package, modes, commands, and identity rules.
+
+## Gateway setup
+
+Apply migrations to a PostgreSQL database:
+
+```bash
+PGUSER=schema_owner PGPASSWORD='<password>' \
+AGENT_BRIDGE_DATABASE_URL=postgresql://host/database \
+  agent-bridge migrate
+```
+
+The migration sequence creates or refreshes a database-specific restricted role. Get its name, then create a login that inherits it. Keep the schema-owner URL out of the gateway process:
+
+```sql
+create role agent_bridge_gateway login password '<generated password>';
+do $grant$
+declare
+  runtime_role text := 'agent_bridge_runtime_' || substr(md5(current_database()), 1, 16);
+begin
+  execute format('grant %I to agent_bridge_gateway', runtime_role);
+end
+$grant$;
+```
+
+The database-derived suffix prevents a gateway login for one database from inheriting access to another Agent Bridge database on the same PostgreSQL cluster. Do not grant the login another database's runtime role.
+
+Create a workspace, agent, and credential with the migration or provisioning connection. Store only a SHA-256 token hash:
+
+```sql
+insert into agent_bridge.workspaces (id, name)
+values ('team', 'Team');
+
+insert into agent_bridge.agents (workspace_id, principal, runtime_type)
+values ('team', 'codex', 'codex')
+returning id;
+
+insert into agent_bridge.credentials (workspace_id, agent_id, token_hash, label)
+values ('team', '<agent uuid>', '<sha256 token hash>', 'codex laptop');
+```
+
+Repeat the agent and credential inserts for Claude Code, Claude Desktop, or any other principal. Each plaintext token should be random, unique, and shown only to the matching client installer.
+
+Start the gateway:
+
+```bash
+PGUSER=agent_bridge_gateway PGPASSWORD='<password>' \
+AGENT_BRIDGE_RUNTIME_DATABASE_URL=postgresql://host/database \
+AGENT_BRIDGE_HOST=127.0.0.1 \
+AGENT_BRIDGE_PORT=8787 \
+agent-bridge-gateway
+```
+
+Put the gateway behind TLS for any non-loopback deployment.
+
+Configure a client backend without storing its identity:
+
+```text
+AGENT_BRIDGE_PROVIDER=gateway
+AGENT_BRIDGE_URL=https://bridge.example.com
+AGENT_BRIDGE_WORKSPACE=team
+```
+
+These shared settings are enough before `clients install`. The installer takes `AGENT_BRIDGE_CLIENT_TOKEN`, creates a private client backend file containing the matching token, and registers `AGENT_BRIDGE_AGENT`, `AGENT_BRIDGE_INSTANCE`, and that file's path with the host. Gateway initialization checks readiness, token validity, and that the token-bound principal matches that process identity.
+
+## Offline gateway behavior
+
+Gateway clients use `~/.agent-bridge/edge.sqlite3` by default.
+
+When a send cannot reach the gateway:
+
+1. The validated message is written to the SQLite outbox with a stable idempotency key.
+2. The CLI or MCP result reports `disposition: "queued"` and `authoritative: false`.
+3. `agent-bridge sync` retries due messages in queue order and pulls remote history into the inbox cache. A permanently blocked message remains visible in diagnostics but does not stop later messages.
+4. An ambiguous retry is safe because the gateway enforces idempotency and rejects changed content under the same key.
+
+Cached reads report `source: "cache"` and `stale: true`. Claims, lease changes, delivery settlement, presence, and read receipts require the gateway because replaying those operations after a lease or identity change is unsafe.
+
+## CLI
+
+```bash
+agent-bridge init --provider local
+agent-bridge doctor
+agent-bridge status
+agent-bridge pending
+agent-bridge send --type request --target worker "Run the task"
+agent-bridge post --category goal-update --project agent-bridge "Gateway is ready"
+agent-bridge inbox --limit 20
+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 extend --delivery-id <uuid> --lease-token <uuid>
+agent-bridge ack --delivery-id <uuid> --lease-token <uuid>
+agent-bridge nack --delivery-id <uuid> --lease-token <uuid> --error "retry later"
+agent-bridge join --instance desktop-1 --runtime codex --capability mcp
+agent-bridge presence
+agent-bridge sync
+agent-bridge watch
+```
+
+`agent-bridge pending` is a cheap shell gate for agent startup. It exits 0 when unread messages or due delivery work exists and 1 when neither exists. Its JSON result separates unread context from executable delivery work. Gateway checks fail instead of returning a false negative when the remote authority cannot confirm unread state.
+
+`watch` runs until interrupted unless `--polls` sets an explicit bound. Empty polls use capped backoff and jitter. Gateway and legacy network failures retry when the error is transient. Authentication and validation errors stop the watcher.
+
+Unknown flags and missing option values fail before a message can be sent. This prevents a misspelled target flag from becoming a broadcast.
+
+## MCP tools
+
+All providers expose the v1 compatibility tools:
+
+- `post_context`
+- `get_context`
+- `ack_context`
+
+Local and gateway providers also expose:
+
+- `send`
+- `history`
+- `claim`
+- `extend`
+- `acknowledge`
+- `negative_acknowledge`
+- `heartbeat`
+- `presence`
+
+Legacy Supabase does not advertise delivery or presence tools because its schema cannot enforce those operations.
+
+## Identity and security
+
+- `~/.agent-bridge/config` contains backend settings only. A stored `AGENT_BRIDGE_AGENT` value is ignored.
+- Local clients bind identity through their process environment or an explicit CLI send argument.
+- Gateway tokens bind workspace and principal. The API ignores caller-supplied source and workspace fields.
+- Gateway clients use separate owner-only backend files and principal-bound tokens.
+- The gateway uses `AGENT_BRIDGE_RUNTIME_DATABASE_URL`. Migration and provisioning commands use the separate schema-owner `AGENT_BRIDGE_DATABASE_URL`.
+- Remote HTTP must use TLS. Plain HTTP is accepted only on loopback.
+- Local config, database, WAL, and shared-memory files use owner-only permissions where the platform supports POSIX modes.
+- The private `agent_bridge` schema is denied to Supabase `anon` and `authenticated` Data API roles.
+- Expired presence rows are pruned during heartbeat and listing. Each agent is capped at 128 active instances, and each workspace is capped at 4,096.
+- Errors expose stable codes without database URLs, tokens, or provider response bodies.
+- Delivery work is at least once, not exactly once. Consumers must make external side effects idempotent.
+
+## Legacy Supabase compatibility
+
+Existing deployments can continue using:
+
+```text
+AGENT_BRIDGE_PROVIDER=legacy-supabase
+AGENT_BRIDGE_URL=https://your-project.supabase.co
+AGENT_BRIDGE_KEY=<publishable key>
+```
+
+Legacy mode keeps the v1 `shared_context` and `ack_context` RPC behavior. It adds bounded network calls, HTTPS enforcement, UUID mapping across CLI processes, newest-first reads, and the complete compatibility envelope. It cannot provide secure principal binding, delivery leases, presence, or an offline outbox. Use gateway mode for those features.
+
+When gateway migrations run in the same PostgreSQL database as `public.shared_context`, migration 006 imports legacy rows and receipts into the private v2 schema. It preserves valid envelope UUIDs, keeps the existing synthetic UUID mapping for ordinary numeric IDs, assigns deterministic UUIDs to larger IDs, maps projects to workspaces, rejects ID collisions, and verifies the imported count. It does not create executable deliveries for historical targeted rows because an upgrade must not replay old work.
+
+The original v1 schema remains in [`sql/setup.sql`](sql/setup.sql). Ordered gateway migrations live in [`sql/migrations/`](sql/migrations/).
+
+## Health and operations
+
+`doctor` and `status` return JSON with:
+
+- Provider and actual schema version.
+- Bound workspace, agent, and instance.
+- Endpoint or database path.
+- Cursor and queue state.
+- Pending, claimed, retrying, and dead delivery counts.
+- Gateway reachability, outbox depth, blocked outbox rows, cache size, and last sync error.
+
+The gateway exposes unauthenticated `/readyz`. `/v2/status` and `/metrics` require a valid credential.
+
+Before dropping an Agent Bridge database, remove its gateway login and database-specific runtime role. Run this while connected to that database so `current_database()` still identifies the right role:
+
+```sql
+drop role if exists agent_bridge_gateway;
+do $cleanup$
+declare
+  runtime_role text := 'agent_bridge_runtime_' || substr(md5(current_database()), 1, 16);
+begin
+  execute format('drop role if exists %I', runtime_role);
+end
+$cleanup$;
+```
+
+The runtime role owns no schema objects. PostgreSQL keeps roles after a database is dropped, so skipping this step leaves an unused cluster role behind.
+
+## Development
+
+```bash
+npm run typecheck
+npm test
+npm run build
+npm pack
+```
+
+Set `AGENT_BRIDGE_TEST_DATABASE_URL` to run the live PostgreSQL contract and migration tests. CI runs Node 22 and 24 on Linux, macOS, and Windows, plus PostgreSQL and clean package-install jobs.
+
+## Documentation
+
+- [docs/architecture-v2.md](docs/architecture-v2.md): protocol and storage decisions.
+- [SKILL.md](SKILL.md): runtime-neutral agent operating instructions.
+- [llms.txt](llms.txt): compact machine-readable project map.
+- [docs/postmortems/2026-07-08-wrapper-source-drift.md](docs/postmortems/2026-07-08-wrapper-source-drift.md): wrapper and source-identity incident.
+- [CLAUDE.md](CLAUDE.md): repository rules, architecture constraints, and documentation ownership.
+- [CHANGELOG.md](CHANGELOG.md): released and pending changes.
+
+## License
+
+Apache-2.0

package/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: agent-bridge
+description: Share context and reliable work between agents across runtimes and machines.
+---
+
+# Agent Bridge
+
+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.
+
+At session start, call `get_context` with a small limit. Summarize relevant unacknowledged entries, then call `ack_context` with the IDs you handled.
+
+Post context as events happen when another agent would need the information later:
+
+- `goal-update`: material progress, decisions, or completed research
+- `config-change`: configuration or infrastructure changes
+- `flag`: failures, blockers, or unsafe assumptions
+- `operational`: runtime and repository handoffs
+- `bridge-meta`: limitations or proposed improvements to Agent Bridge
+
+Use v2 delivery tools for executable work. A read receipt does not claim work. Claim a delivery before acting, renew long leases, acknowledge success, and negatively acknowledge retryable or dead work with a bounded error.
+
+Use `agent-bridge pending` as a cheap process gate before starting an agent. Exit 0 means unread context or due delivery work exists. Exit 1 means neither exists. Treat network errors as unknown state, not as an empty queue.
+
+Keep side effects idempotent. Agent Bridge provides at-least-once delivery and idempotent message insertion, not exactly-once execution.

package/bin/CLAUDE.md

@@ -0,0 +1,11 @@
+<claude-mem-context>
+# Recent Activity
+
+<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
+
+### Feb 23, 2026
+
+| ID | Time | T | Title | Read |
+|----|------|---|-------|------|
+| #5341 | 6:57 AM | ✅ | Agent-bridge database configuration migrated from old to new Supabase account | ~523 |
+</claude-mem-context>

package/bin/agent-bridge

@@ -0,0 +1,7 @@
+#!/usr/bin/env node
+import { runCli } from "../dist/cli.js";
+
+runCli().catch((error) => {
+  process.stderr.write(`Error: ${error instanceof Error ? error.message : String(error)}\n`);
+  process.exitCode = 1;
+});