@engineeros/connector 1.52.6 → 1.53.0

package/README.md

@@ -369,6 +369,13 @@ Verification results are cached per commit and role. Completed checks are reused
 
 `engineeros-connector start` keeps running across connector releases. It runs the connector as a child process; a release is installed into `~/.engineeros/connector/versions/<version>` beside the running one with `npm install --ignore-scripts`, checked against the registry's lockfile integrity, its npm registry signatures and the Node.js range it declares, and smoke-tested (`engineeros-connector version`) there before anything switches. When a release is activated, the connector waits until no assessment, connected prompt, integration request or local command is in flight, then restarts only its own process on the new release. EngineerOS, conversations and Goal runs are not interrupted: Goal workers run in their own processes. A release that stops before it ever reaches EngineerOS is rolled back automatically and not retried; the previous verified release stays installed for **Roll back**.
 
+Each start, including the restart onto a new release, also brings what the connector runs up to date:
+
+- **Coding agent.** A connector paired with an agent from the official ACP catalog (`--agent codex`, `claude`, `gemini` and so on) moves to the version the catalog lists now. The new version is installed and started once before the saved configuration changes; if either fails, or a Goal is still running, the version that works stays and the next start tries again. Saved conversations are kept; one the new version cannot load starts a new session that is sent the whole conversation. The `manual` update policy turns this off.
+- **Tools.** Every enabled tool set up from the catalog (Playwright, CodeGraph, ast-grep and the rest) moves to the newer reviewed pin this release ships, exactly as `tools upgrade` does; a tool that fails keeps its version, and a tool you rolled back stays rolled back until a later pin ships. Playwright's browser is then prepared for the Playwright version in use.
+
+Forge and Codex CLI (`--agent-protocol codex`) are your own global installs and are never updated by the connector.
+
 ```sh
 engineeros-connector update                 # version, policy and state
 engineeros-connector update check           # ask npm for the latest release
@@ -419,7 +426,7 @@ engineeros-connector tools sign-out PROVIDER_ID --workspace PATH
 
 After pairing connector 1.8 or newer, open **Project → Steering → Local workspace → Tools and plugins** to search the catalog and control registered providers. The web UI can enable, disable and remove registrations through the authenticated connector session. Enabling and removal require confirmation. Registration remains local because its evaluated manifest contains machine paths and integrity metadata that are never advertised to EngineerOS.
 
-Use `enable all` to clear the global disable. Registration never installs packages or executes a provider. Providers set up from the catalog are installed into `tools/<provider>/<version>` beside the registry file; when a connector release ships a newer reviewed pin, **Update to** (or `tools upgrade PROVIDER_ID`) installs it into its own version directory after console approval, verifies it, and points the registration at it. New agent sessions use it with no restart; sessions already running keep the previous version, which stays installed for **Roll back to** (`tools rollback PROVIDER_ID`) as long as it still passes its integrity check. Replacing any other pin requires explicit removal and registration. Registry files live beside the user-owned connector configuration as `<workspace-key>.tools.json`, outside the repository. The connected workspace displays their inventory, refreshed through authenticated heartbeats. Stop any abandoned operator update before removing its `.tools.json.lock` file.
+Use `enable all` to clear the global disable. Registration never installs packages or executes a provider. Providers set up from the catalog are installed into `tools/<provider>/<version>` beside the registry file; when a connector release ships a newer reviewed pin, the connector applies it to enabled tools when it next starts (see [Updates without restarting](#updates-without-restarting)), and **Update to** (or `tools upgrade PROVIDER_ID`) applies it at once after console approval. Either way it is installed into its own version directory, verified, and the registration pointed at it. New agent sessions use it with no restart; sessions already running keep the previous version, which stays installed for **Roll back to** (`tools rollback PROVIDER_ID`) as long as it still passes its integrity check. Replacing any other pin requires explicit removal and registration. Registry files live beside the user-owned connector configuration as `<workspace-key>.tools.json`, outside the repository. The connected workspace displays their inventory, refreshed through authenticated heartbeats. Stop any abandoned operator update before removing its `.tools.json.lock` file.
 
 Manifests are strict internal JSON configuration with these required fields: