docs: prune recent additions for readability

docs/plugins/architecture.md

@@ -511,10 +511,9 @@ At startup, OpenClaw does roughly this:
 4. normalize plugin config (`plugins.enabled`, `allow`, `deny`, `entries`,
    `slots`, `load.paths`)
 5. decide enablement for each candidate
-6. load enabled native modules — built `dist/*` bundled modules go through a
-   native loader path, while non-built native plugin modules are loaded via
-   jiti
-7. call native `register(api)` (or `activate(api)` — a legacy alias) hooks and collect registrations into the plugin registry
+6. load enabled native modules: built bundled modules use a native loader;
+   unbuilt native plugins use jiti
+7. call native `register(api)` hooks and collect registrations into the plugin registry
 8. expose the registry to commands/runtime surfaces
 
 <Note>

docs/plugins/bundles.md

@@ -261,10 +261,6 @@ dual-format packages from being partially installed as bundles.
   plugins; the release pipeline is responsible for shipping a complete bundled
   dependency payload (see the postpublish verification rule in
   [Releasing](/reference/RELEASING)).
-- Sub-agent runs that launch bundled MCP servers dispose those MCP clients
-  through the shared runtime-cleanup path when the sub-agent exits, so
-  sub-agent lifecycles do not leak stdio child processes or long-lived MCP
-  connections across turns.
 
 ## Security
 

docs/plugins/codex-harness.md

@@ -29,8 +29,7 @@ aligned with the PI harness:
 - `agent_end`
 
 Bundled plugins can also register a Codex app-server extension factory to add
-async `tool_result` middleware, and mirrored Codex transcript writes route
-through `before_message_write`.
+async `tool_result` middleware.
 
 The harness is off by default. It is selected only when the `codex` plugin is
 enabled and the resolved model is a `codex/*` model, or when you explicitly