feat: add structured control tracing

docs/architecture.md

@@ -158,6 +158,12 @@ daemon errors include a `next:` recovery line for missing peer cards, missing
 grants, missing resources, unavailable endpoints, and missing DB/KV/document
 registrations.
 
+Daemon logs use structured `tracing` fields for local control requests:
+`command`, `peer_node`, `resource`, `capability`, `stream`, and stable
+`error_code` where applicable. The request tracer classifies requests instead of
+formatting full payloads, so bearer tokens, private key paths, packet/message
+payloads, and document JSON are not logged by that layer.
+
 Host-opening paths are intentionally narrow. TCP pipe forwarding accepts only
 explicit loopback socket addresses on both the local listener and remote target;
 Unix pipe forwarding requires absolute paths without parent-directory

docs/production-readiness-roadmap.md

@@ -271,11 +271,11 @@ Goal: make `geth` ergonomic and stable as a base layer for custom automation.
 
 Goal: make production failures diagnosable from the CLI and logs.
 
-- `[ ]` Improve structured tracing.
+- `[x]` Improve structured tracing.
   Acceptance criteria:
-  - `[ ]` Logs include fields for command, peer node, resource, capability,
+  - `[x]` Logs include fields for command, peer node, resource, capability,
     stream, cursor, and stable error code where applicable.
-  - `[ ]` Sensitive bearer tokens and private material are not logged.
+  - `[x]` Sensitive bearer tokens and private material are not logged.
 
 - `[x]` Expand health status.
   Acceptance criteria: