docs: pick up proton rclone runtime gate repair

docs/evidence/2026-06-14-personal-agent-proton-rclone-runtime-reconciliation.md

@@ -19,9 +19,9 @@ against a same-day redacted runtime probe.
 
 - MCP registration: `proton-calendar`, `proton-email`, and `proton-contacts`
   are enabled for the Steev profile.
-- Docker inventory: calendar gate is up, email gate and contacts gate remain
-  exited, one Proton Bridge container is up, and one stale Proton Bridge
-  container remains created.
+- Docker inventory: calendar, email, and contacts gates are up after the
+  child-local bind-mount repair; one Proton Bridge container is up, and one
+  stale Proton Bridge container remains created.
 - systemd user inventory: `proton-bridge.service` and
   `proton-bridge-proxy.service` are loaded and enabled but currently
   `activating-auto-restart`.
@@ -30,8 +30,10 @@ against a same-day redacted runtime probe.
 
 ## Result
 
-The profile runtime snapshot now records Proton Bridge systemd convergence as a
-must-fix gap. The aggregate `personal-agent` runtime state remains degraded.
+The profile runtime snapshot now records the email and contacts gate repair as
+complete child-local. The aggregate `personal-agent` runtime state remains
+degraded because Core registration, Proton Bridge systemd convergence, rclone
+service posture, source-lock pickup, and final acceptance remain open.
 
 This proof does not read or store mail bodies, mail subjects, sender or
 recipient addresses, contact details, calendar event details, drive file names,