Add protected interaction evidence and measured debugging phases

docs/development-observability.md

@@ -64,3 +64,35 @@ when investigating latency. Do not optimize by removing an audit gate or retryin
 an action. The proof is in `artifacts/individual-agent-native-proof.json`.
 The final Windows package verifier checks current source and runs both shipped
 legacy and individual DPAPI/PQ clients successfully.
+
+## Latest interaction and session measurements
+
+The actual protected interaction proof uses trace
+`32cbbb58088d193301c5f6ac530284af`: 30 spans, verified parent correlation,
+capture 0.3353 ms, challenge 8.1735 ms, encryption 0.4718 ms, send 62.1817 ms
+and acknowledgement 0.4234 ms. The backend store stage took 54.2629 ms.
+Collector rejected writes were zero. These are one local reproduction's
+measurements, not performance guarantees.
+
+After session-title classification was added, the actual native session inventory
+proof uses trace `64013e27cfc37bc3792983bc06149c87`: request 85.675 ms,
+session adapter 1.0637 ms and durable audit phases 33.3975 and 47.2472 ms.
+This fixture did not enable the semantic model; it cannot establish semantic-model
+latency. The native proof confirms a confidential title is masked while preserving
+its opaque session ID.
+
+A parallel fixture timed out before enrollment and therefore before signed
+diagnostics activation. Its isolated rerun and restart reached the shell in
+794/806 ms. Safe local startup snapshots were added; the original timeout's cause
+is unresolved. Do not describe that failure as a traced DLP/model regression.
+The current Windows package proof and 515-test suite passed before the subsequent
+export-counter refinement. Ignored proof artifacts remain local.
+
+After the refinement and policy child stages, the final suite passes 522 tests.
+Real signed policy/bookmark fixtures verify actual OTLP child spans and disabled
+transitions. Windows build, packaged-runtime verification and the native tabs
+proof pass. The native receiver attributes exports by actual `service.name`:
+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.