@creatornader/agent-bridge 0.7.4 → 0.7.7

package/CHANGELOG.md

@@ -4,6 +4,31 @@ 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.7.7] - 2026-07-30
+
+### Fixed
+
+- Publish the packed package before checking npm for immutable release recovery.
+
+## [0.7.6] - 2026-07-30
+
+### Fixed
+
+- Read release package metadata directly from the verified tarball before checking
+  the immutable npm version during recovery.
+
+## [0.7.5] - 2026-07-30
+
+### Fixed
+
+- Create a canonical immutable GitHub Release only after the tagged gateway and npm
+  publication gates succeed. Release pages now use the same tag and `Agent Bridge
+  v<version>` title for every new version.
+- Make release recovery verify an already published package from the packed artifact
+  instead of failing on an immutable npm version.
+
 ## [0.7.4] - 2026-07-30
 
 ### Fixed
@@ -528,7 +553,14 @@ First tagged release. Marks the point where agent-bridge has shipped its initial
 - Narrative-leak detection in CI + on commit via `creatornader/textleaks@v0.2.0` (renamed from leakguard).
 
 [0.1.0]: https://github.com/creatornader/agent-bridge/releases/tag/v0.1.0
-[Unreleased]: https://github.com/creatornader/agent-bridge/compare/v0.6.4...HEAD
+[Unreleased]: https://github.com/creatornader/agent-bridge/compare/v0.7.7...HEAD
+[0.7.7]: https://github.com/creatornader/agent-bridge/compare/v0.7.6...v0.7.7
+[0.7.6]: https://github.com/creatornader/agent-bridge/compare/v0.7.5...v0.7.6
+[0.7.5]: https://github.com/creatornader/agent-bridge/compare/v0.7.4...v0.7.5
+[0.7.4]: https://github.com/creatornader/agent-bridge/compare/v0.7.3...v0.7.4
+[0.7.3]: https://github.com/creatornader/agent-bridge/compare/v0.7.2...v0.7.3
+[0.7.2]: https://github.com/creatornader/agent-bridge/compare/v0.7.1...v0.7.2
+[0.7.1]: https://github.com/creatornader/agent-bridge/compare/v0.7.0...v0.7.1
 [0.6.4]: https://github.com/creatornader/agent-bridge/compare/v0.6.3...v0.6.4
 [0.6.3]: https://github.com/creatornader/agent-bridge/compare/v0.6.2...v0.6.3
 [0.6.2]: https://github.com/creatornader/agent-bridge/compare/v0.6.1...v0.6.2

package/README.md

@@ -150,7 +150,9 @@ The authenticated check compares the running package and Git revision with the
 intended release. It also requires protocol 2.1, request authority, and row isolation.
 It prints no credential. A missing or different revision stops the rollout.
 
-Release tags run this deployment gate before npm publication. The release environment
+Release tags run this deployment gate before npm publication. After the package is
+published, the workflow creates the immutable GitHub Release for the same tag with
+the canonical title `Agent Bridge v<version>`. The release environment
 must define `AGENT_BRIDGE_FLY_APP` and `AGENT_BRIDGE_GATEWAY_ORIGIN`, and keep
 `FLY_API_TOKEN` plus `RELEASE_VERIFY_TOKEN` as protected secrets. The manual `gateway
 production proof` workflow tests the deployed gateway after this gate passes. GitHub

package/docs/deployment.md

@@ -271,7 +271,9 @@ messages before choosing one authority. If schema or data recovery is required,
 restore the verified native DR bundle into a fresh target and switch authority once.
 Do not run the source and restored database as active authorities at the same time.
 
-Release tags deploy the exact tagged revision before npm publication. The release job
+Release tags deploy the exact tagged revision before npm publication. After successful
+package publication, the release job creates the immutable GitHub Release for that
+same tag. The release job
 uses the approval-protected `agent-bridge-production-proof` environment. Configure
 `AGENT_BRIDGE_FLY_APP` and `AGENT_BRIDGE_GATEWAY_ORIGIN` as environment variables, and
 configure `PROOF_SENDER_TOKEN`, `PROOF_RECEIVER_TOKEN`, `PROOF_HOST_SALT`, and
@@ -280,6 +282,12 @@ for the release job. It runs the read-only Fly preflight, deploys the image with
 checked-out revision, requires `/readyz`, and verifies the running package version and
 revision. A failed deployment or identity check stops npm publication.
 
+To recover a release workflow, dispatch it from the release tag itself and provide the
+same tag as the input. The workflow verifies an already published package by its name
+and version from the packed artifact, then leaves that immutable npm version intact.
+It also leaves an existing GitHub Release intact. A recovery run cannot publish a
+different package under the tag.
+
 The manual `gateway production proof` GitHub Actions workflow runs its acceptance
 proof against that deployed HTTPS gateway. GitHub restricts it to `main`, and every job
 uses the same approval-protected environment. Use a release-specific proof workspace

package/docs/postmortems/2026-07-08-wrapper-source-drift.md

@@ -2,17 +2,19 @@
 
 ## Status
 
-Resolved for basic Codex, Claude Code, and Claude Desktop availability.
+Resolved for Codex, Claude Code, and Claude Desktop availability.
 
-Codex, Claude Code, and Claude Desktop now launch the source repo MCP server
-directly from its built `dist/index.js` entrypoint with a pinned Node binary.
-The direct server reads credentials from `~/.agent-bridge/config`, so client
-configs no longer need to duplicate the Supabase URL or anon key.
+The public package now owns the local MCP path. Each client has a public
+`agent-bridge-loopback-host` launchd service that binds only its assigned
+loopback port and serves `/mcp/health` plus Streamable HTTP MCP. Claude Desktop
+uses the public `agent-bridge-stdio-http-proxy` to reach its local host. The
+client services read owner-private backend files, so registrations do not need
+to duplicate gateway credentials.
 
 The broken Codex, Claude Code, and Claude Desktop signed-wrapper launchd jobs
 were removed after their labels stayed loaded while `/mcp/health` refused
-connections. The wrapper code still exists as an optional signed attribution
-layer.
+connections. The wrapper remains an optional signed attribution layer outside
+the public Agent Bridge runtime.
 
 ## Impact
 
@@ -40,43 +42,56 @@ it required `AGENT_BRIDGE_URL` and `AGENT_BRIDGE_KEY` in process env. The CLI
 already read `~/.agent-bridge/config`, so the two source-repo entrypoints had
 drifted.
 
+The first public-host release also exposed a package-distribution defect. npm
+executes package bins through a symlink, while the host and proxy used a source
+file entrypoint check that compared the unresolved `argv[1]` path. Their
+install commands therefore returned success without starting a service.
+
+The release workflow published valid npm versions but did not create matching
+GitHub Release objects. This made the release page incomplete and left older
+titles inconsistent.
+
 During recovery, the wrapper installer also selected `node` from ambient
 `PATH`. That allowed restarts to drift to a local Node shim instead of the
 Homebrew Node binary that had previously run the service.
 
 ## Fixes
 
-- `src/server.ts` now reads `~/.agent-bridge/config` when env credentials are
-  absent. Env values still take precedence.
-- `test/server_factory.test.ts` covers config-file fallback, env precedence,
-  quoted config values, explicit config paths, and missing credentials.
-- Local Codex, Claude Code, and Claude Desktop configs now launch the source
-  MCP server directly with `/opt/homebrew/bin/node` and only set
-  `AGENT_BRIDGE_AGENT`.
-- The dead Codex, Claude Code, and Claude Desktop wrapper launchd jobs were
+- The public package provides a long-lived loopback host, health endpoint, and
+  Claude Desktop stdio proxy. It installs launchd services only after health
+  proves the socket is listening, and uninstalls them only after the socket
+  closes.
+- The host and proxy resolve the invoked file before deciding whether to run as
+  a CLI. Their global npm bins now work through npm's symlink layout.
+- Package-install smoke invokes both public binaries. This catches a silent
+  entrypoint failure before publication.
+- Local Codex, Claude Code, and Claude Desktop registrations now point to the
+  public client-owned loopback services. The dead private wrapper jobs were
   uninstalled.
-- The internal wrapper installer now prefers `/opt/homebrew/bin/node` by default
-  while still honoring `NODE_BIN`.
+- Tagged releases now create one immutable GitHub Release after the gateway and
+  npm gates pass. New release pages use `Agent Bridge v<version>`. A tag-based
+  recovery verifies the immutable package already in npm before continuing.
 
 ## Wrapper Policy
 
-Keep the signed wrapper for attribution receipts and local-substrate metadata.
-Do not make it the only Agent Bridge path for Codex, Claude Code, or Claude
-Desktop.
+Agent Bridge must run fully from its public package. Keep the signed wrapper
+for attribution receipts and local-substrate metadata only. Do not make it an
+availability boundary for Codex, Claude Code, Claude Desktop, or another MCP
+client.
 
-Only reinstall those wrapper jobs as active client targets after the wrapper has
-health-based supervision. A loaded launchd label is not proof that Agent Bridge
-MCP is available. The proof is a successful `/mcp/health` probe and a real MCP
-tool call.
+An active launchd label is not proof that Agent Bridge MCP is available. The
+proof is a successful public `/mcp/health` probe and a real MCP tool call. New
+versions use an immutable `v<version>` tag and the GitHub Release title `Agent
+Bridge v<version>`.
 
 ## Verification
 
-- `npm test`: 24 tests passed.
-- `npm run build`: passed.
-- Direct stdio MCP smoke: listed `post_context`, `get_context`, and
-  `ack_context`, then read live context.
-- CLI status: returned `{"status":"ok","message":"Agent Bridge is connected to Supabase"}`.
-- Claude Desktop launch proof: fresh Desktop log showed `initialize` and
-  `tools/list` succeeding against the direct source MCP entrypoint.
-- Wrapper cleanup: Codex, Claude Code, and Claude Desktop wrapper labels are
-  absent, and their launchd plist files are absent.
+- A global-package launchd install bound a disposable loopback port, passed
+  `/mcp/health`, then unbound the port after uninstall.
+- Each production Codex, Claude Code, and Claude Desktop public host passed
+  `/mcp/health`, completed an MCP handshake, listed 17 tools, and accepted a
+  `post_context` write.
+- Each client registration and its identity, instance, and private backend file
+  passed managed-client inspection.
+- The three private wrapper labels are absent. The three public launchd labels
+  are running and own ports 8794, 8793, and 8791.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@creatornader/agent-bridge",
-  "version": "0.7.4",
+  "version": "0.7.7",
   "description": "Let AI agents message each other and hand off work across tools, sessions, and machines.",
   "type": "module",
   "license": "Apache-2.0",