@engineeros/connector 1.53.3 → 1.54.0

package/README.md

@@ -369,12 +369,12 @@ 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:
+The connector also keeps what it 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.
+- **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. It checks once connected, so EngineerOS never waits on the download, and then hourly, only while no Goal, prompt, assessment or hunt is running. The new version is installed and started once before the saved configuration changes; if either fails, the version that works stays and the next check tries again. Once switched, the connector signs in to EngineerOS again so the new version and its models show there. Saved conversations are kept; one the new version cannot load starts a new session that is sent the whole conversation.
+- **Tools.** On each start, 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. Pins move to each tool's newest npm release every week: a scheduled job installs every moved pin through this setup, runs the tool tests and publishes a connector release.
 
-Forge and Codex CLI (`--agent-protocol codex`) are your own global installs and are never updated by the connector.
+The `manual` update policy turns both off. Forge and Codex CLI (`--agent-protocol codex`) are your own global installs, which the connector never changes; when a newer release is out, the self-check (`doctor`, and the connector's diagnostics in EngineerOS) warns with the command to update it.
 
 ```sh
 engineeros-connector update                 # version, policy and state