From 24c289376d872e09f2d1bbff4ddbe47ea6f37217 Mon Sep 17 00:00:00 2001 From: iris Date: Sun, 20 Sep 2026 13:54:31 +0200 Subject: [PATCH 1/5] docs: clear write-good.Passive hits in docs/integrations/forge.md --- docs/integrations/forge.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/integrations/forge.md b/docs/integrations/forge.md index 3604d609..0979081e 100644 --- a/docs/integrations/forge.md +++ b/docs/integrations/forge.md @@ -106,7 +106,8 @@ The crate builds a second, independent binary for a different host — see The host-specific calls — list unread, mark read, resolve own login — live behind `Source` in `hive-forge-notify/src/source.rs`; -classification, formatting, dedupe and todo delivery are shared. Todo +classification, formatting, dedupe and todo delivery live in `notify.rs`, +common to both binaries. Todo keys here are the bare thread ids, and must stay that way: renaming them would orphan every in-flight forge todo on the first restart after a deploy. From a0ada3919152399422fdd345a50d1cc115da956f Mon Sep 17 00:00:00 2001 From: iris Date: Sun, 20 Sep 2026 13:55:27 +0200 Subject: [PATCH 2/5] docs: clear write-good.Passive hits in docs/tools/lifecycle.md --- docs/tools/lifecycle.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tools/lifecycle.md b/docs/tools/lifecycle.md index c556098a..88b6f90f 100644 --- a/docs/tools/lifecycle.md +++ b/docs/tools/lifecycle.md @@ -23,8 +23,8 @@ one-row answer naming itself. Meta-flake input bumps route through the operator approval queue. Creating a new agent is **not** in this group — agents have no tool for -it. A new agent's config repo is scaffolded by the swarm controller's -`InitAgentConfigRepo` job (`POST /api/agents`, see +it. The swarm controller's `InitAgentConfigRepo` job scaffolds a new +agent's config repo (`POST /api/agents`, see `swarm-controller/`), and the operator spawns the container from the dashboard (`◆ R3QU3ST SP4WN` / `Spawn` approval, routed via `HostRequest::RequestSpawn`). From 5ec742a2d3ba58a935d03f4729c5a5af1dc7df93 Mon Sep 17 00:00:00 2001 From: iris Date: Sun, 20 Sep 2026 13:56:51 +0200 Subject: [PATCH 3/5] docs: clear write-good.Passive hits in docs/turn-loop/mcp.md --- docs/turn-loop/mcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/turn-loop/mcp.md b/docs/turn-loop/mcp.md index e254d0fd..79784309 100644 --- a/docs/turn-loop/mcp.md +++ b/docs/turn-loop/mcp.md @@ -218,7 +218,7 @@ see [`docs/tools/subagent.md`](../tools/subagent.md). `TodoWrite`. `Bash` **isn't** in the managed deny — see below. - Allowed MCP tools: as listed above (by tool group). -`Bash` is disallowed for the autonomous harness — shell execution goes +The autonomous harness disallows `Bash` — shell execution goes through `mcp__bash__run` (background tasks with structured output + task-id tracking) instead of an interactive shell. The harness gate is `--tools` / `--allowedTools` (Bash absent from `ALLOWED_BUILTIN_TOOLS`), From 457cae708cc0103495dcbdbe06d8b9cbc9a923db Mon Sep 17 00:00:00 2001 From: iris Date: Sun, 20 Sep 2026 13:56:51 +0200 Subject: [PATCH 4/5] docs: clear write-good.Passive hits in docs/web-ui/terminal-rendering.md --- docs/web-ui/terminal-rendering.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/web-ui/terminal-rendering.md b/docs/web-ui/terminal-rendering.md index 68b680ea..1eb32c31 100644 --- a/docs/web-ui/terminal-rendering.md +++ b/docs/web-ui/terminal-rendering.md @@ -11,7 +11,8 @@ as `TermEnvelope { seq?, msgs: TermMsg[] }` frames `ts` is ISO 8601 UTC (`2026-09-13T12:35:03Z`) and is the **source event's** time, stamped at classify time from the event's own stamp — so a row -replayed from sqlite says when it happened, not when it was fetched. It +replayed from sqlite says when it happened, not when a client fetched +it. It lives on the row rather than on the envelope because the swarm queue publishes rows bare, with no envelope around them (`hive-agent/src/swarm_term.rs`); a subscriber there has nowhere else to From cc1f2d2594311e818e203d2ed47a3f47c96c83e4 Mon Sep 17 00:00:00 2001 From: iris Date: Sun, 20 Sep 2026 13:57:39 +0200 Subject: [PATCH 5/5] docs: clear write-good.Passive hits in docs/process/pr-review-gate.md --- docs/process/pr-review-gate.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/process/pr-review-gate.md b/docs/process/pr-review-gate.md index 132a28fb..d8fd1960 100644 --- a/docs/process/pr-review-gate.md +++ b/docs/process/pr-review-gate.md @@ -46,8 +46,9 @@ already happened. No large changes are expected to surface after that point — a reviewer's job past that point is to flag it if one does, not to assume none ever will. -The practical consequence for a reviewer: on a repo where automerge -may already be armed before your review lands, a plain `APPROVED` can +The practical consequence for a reviewer: on a repo where someone with +write access may already have armed automerge before your review +lands, a plain `APPROVED` can be the last step before the merge actually happens, with no further review pass after yours. That's a reason to actually finish checking before approving — not a reason to hesitate over every small thing.