Capture guarded human gestures and verify agent administration

docs/development-observability.md

@@ -96,3 +96,15 @@ browser exports stay at 18 across revocation while backend collection remains
 independent. The earlier aggregate assertion conflated the two services; its
 failed run is retained rather than presented as successful. Do not retroactively
 assign the original extra batch to a service without its original payload.
+
+Foreground gesture development used actual traces to find a second attribution
+gap: a queue flusher started by one event delivered the next event under the first
+async context. `withCorrelation` now validates each durable record's own IDs and
+`audit.deliver` creates a recording delivery child under that source parent.
+Malformed IDs clear unrelated context, and current signed sampling/disable still
+applies. Real OTLP regression tests and three actual human-event traces prove
+distinct parents and complete evidence phase correlation. Trace
+`b7783f42197d0cff83957b0ee96e8296` has 17 spans, capture 19.50 ms and send 13.20 ms;
+`62e09413b9a42f4a58bd7f99485176ac` and
+`545ddac025113e50effed4e9a2ac87ee` each also have 17 spans. Collector rejected writes
+were zero. These are local reproduction timings, not throughput guarantees.