@securecoms/agent-runtime 0.13.1 → 0.14.0

package/README.md

@@ -64,7 +64,7 @@ location encodes a version (a Homebrew Cellar keg, or nvm/asdf/fnm/volta/n) is
 resolved to a stable equivalent — `/usr/local/bin/node`,
 `/opt/homebrew/bin/node`, `/opt/homebrew/opt/node/bin/node`, `/usr/bin/node`,
 or `~/.local/bin/node`, preferring one that is the same real file as the Node
-you ran, and requiring Node >= 22 on the running architecture. If no stable
+you ran, and requiring Node >= 24 on the running architecture. If no stable
 Node exists, install refuses and tells you to install one or pass
 `--exec-path <path>`, which overrides the choice outright.
 
@@ -527,6 +527,58 @@ The paragraph is therefore an advisory configuration summary, not an authority
 claim. Channel authorization and the local gate are both enforced at call
 time, so a configured but ungranted or denied tool is still refused.
 
+## Release notes: 0.14.0
+
+<!-- [COPY, approved by Eric 2026-10-17 (search release notes) and 2026-10-16 (held 0.14.0 items); adapted to 0.14.0 on 2026-10-18] -->
+
+0.14.0 adds four search providers and a page reading tool, limits daily search
+in the owner's private chat, and needs Node 24 or newer. Install it together
+with `@securecoms/agent-bridge` 0.30.3 and restart both.
+
+- **Upgrade the bridge and the runtime together.** An older bridge with this
+  runtime can still use install-time search keys after a search setup
+  mismatch.
+- **Five search providers.** Web search supports Parallel (suggested), Exa,
+  Firecrawl, Tavily and Brave. The agent uses only the provider its owner
+  signed, with that provider's key file.
+- **Read web pages.** The new `web_extract` tool reads one public page in the
+  owner's private chat, through Parallel, Exa, Firecrawl or Tavily (not
+  Brave). Every address is checked before it is sent. The owner turns it on
+  and signs it from the agent's page.
+- **Daily limit.** Searches and page reads in the owner's private chat are
+  limited to 200 a day by default, up to 2000. The owner sets it on the agent's
+  page, which shows "Limit in use: {n} per day". An operator can only lower it
+  with `SECURECOMS_OWNER_DM_SEARCH_DAILY_CAP`.
+- **Fixed error messages.** Search errors reach the agent as short fixed
+  messages. The agent no longer sees provider status codes or text.
+- **Node 24 or newer.** The runtime now requires Node 24 (`engines` and the
+  start-up check).
+- **Budget lock label.** A budget lock path longer than 128 characters, or with
+  a space, is now logged as a safe label instead of `invalid`.
+- **Linux reinstall.** Install on Linux now restarts a running service, so the
+  new version starts.
+
+Behaviour changes
+
+- **No fallback to another key.** If the owner's search setting is invalid,
+  its key file is refused, or the managed config cannot be read, the agent has
+  no web search instead of using `--brave-key-file` or `--tavily-key-file`.
+  Install-time keys still work when no search setting exists at all (search
+  only, never page reading).
+- **Tavily key in a header.** The Tavily key is now sent in a request header
+  instead of the request body.
+- **Stricter `fetch_url`.** It refuses more private address ranges, including
+  Tailscale/CGNAT (100.64.0.0/10) and 198.18.0.0/15. On computers that use a
+  fake-IP DNS proxy (Surge, Clash or Stash in fake-IP mode, some corporate
+  proxies), `fetch_url` and "Read web pages" do not work.
+- **Log changes.** `provider=<name>` replaces `provider_brave`;
+  `skills_config.search_block_invalid reason=…` replaces two older warnings;
+  new `authz.owner_dm_cap`.
+
+Known limits: Exa's fast setting with highlights was not tested against the
+live service. Provider data retention differs by provider; the agent page
+shows it for Exa, Firecrawl, Tavily and Brave.
+
 ## Release notes: 0.13.1
 
 <!-- [COPY, approved by Eric 2026-10-15] -->