docs: clear write-good.Passive hits in docs/process/conventions.md

docs/process/conventions.md

@@ -185,8 +185,8 @@ it directly as a bulleted list, no follow-up fetch needed.
 rows, on both the agent and manager sockets alike (the manager, `ruth`,
 is a normal agent here, just deployed automatically with different
 default capabilities). `Approval` rows only appear when the calling agent is
-the manager (sub-agents don't submit approvals). `Reminder` rows are
-scoped to `owner == self`.
+the manager (sub-agents don't submit approvals). `Reminder` rows always
+carry `owner == self`.
 
 Per-variant fields:
 
@@ -242,8 +242,8 @@ status_text, status_set_at, hive_name, swarm_name, matrix_accounts }`:
   currently pinned at.
 - `running`: whether the target's container is currently up. When
   `false`, the host clears `status_text` / `status_set_at` —
-  on-disk values from before the stop are stale snapshots and
-  shouldn't be shown as live status. Defaults to `true` on the
+  on-disk values from before the stop are stale snapshots, not
+  live status. Defaults to `true` on the
   wire (older harnesses never serialised it, and the host only
   knew how to ask about live containers — keeps backwards-compat
   with pre-running-field payloads).
@@ -321,7 +321,7 @@ being able to report its status chip, and the server-side `SetStatus` handler
 has no tool-group check (only length validation), so gating it would only
 desync the `--allowedTools` list from what the host actually accepts.
 Revoking `meta` therefore drops `get_agent_meta` but never `set_status`.
-`mark_todos_done` is here because todos are pushed to an agent independent of
+`mark_todos_done` is here because producers push todos to an agent independent of
 whether it holds `inbox` — an agent without that group still needs a way to
 clear them.
 
@@ -427,7 +427,7 @@ Anything that changes per-container state on the host should be
 re-applied here so a manual `↻ R3BU1LD` from the dashboard is
 sufficient to recover.
 
-## Actions are factored
+## Actions live in one place
 
 `approve` / `deny` / `destroy` (and the lifecycle helper) live in
 `actions.rs` / `hive-c0re/src/dashboard/`. The admin socket and the dashboard