From 992468dcccc51c4cf7fbf31225c040de26293b78 Mon Sep 17 00:00:00 2001 From: atlas Date: Fri, 18 Sep 2026 10:35:16 +0200 Subject: [PATCH] docs: reword three vale-flagged sentences in matrix.md Preserve meaning exactly: 'There is no' -> 'No ... exists', 'That is' -> 'that's', 'is not' -> isn't. Refs #4475 --- docs/tools/matrix.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tools/matrix.md b/docs/tools/matrix.md index 59440b69..87f2ea77 100644 --- a/docs/tools/matrix.md +++ b/docs/tools/matrix.md @@ -5,7 +5,7 @@ When the agent has at least one `services.hyperhive.agent.matrixAccounts` entry, the harness autoinjects `hive-matrix-daemon`'s streamable-http endpoint as a second MCP server (no stdio bridge — -see Architecture below). There is no `matrix.enable` switch: the account +see Architecture below). No `matrix.enable` switch exists: the account set *is* the switch, and the module declares the hive-internal `main` account for you as soon as `services.hyperhive.agent.matrix.url` is non-null — which hive-c0re fills in per agent whenever the host-level @@ -93,11 +93,11 @@ name. `main` is present exactly when that URL is non-null, which is the whole mechanism behind "accounts are the enable signal": an agent with no homeserver and no account of its own has an empty set, so it gets no -daemon, no path watcher and no injected MCP entry. That is how you give +daemon, no path watcher and no injected MCP entry. That's how you give an agent no matrix tools — it replaces the removed `services.hyperhive.agent.matrix.enable = false`, which now fails evaluation with a message saying so. Declaring an external account with -its own `homeserver` is enough on its own; a hive homeserver is not +its own `homeserver` is enough on its own; a hive homeserver isn't required. Every matrix tool above takes an optional `account` parameter (a name