docs: reconcile proton rclone runtime posture

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

@@ -0,0 +1,39 @@
+---
+name: 2026-06-14-personal-agent-proton-rclone-runtime-reconciliation
+status: complete
+triage: evidence
+owner: jp
+created: 2026-06-14
+source: docs/contracts/personal-agent-runtime-readiness-snapshot.json
+artifact_type: evidence
+---
+
+# Personal-Agent Proton/rclone Runtime Reconciliation
+
+## Scope
+
+This evidence reconciles the `personal-agent` Proton/rclone profile snapshot
+against a same-day redacted runtime probe.
+
+## Redacted 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.
+- systemd user inventory: `proton-bridge.service` and
+  `proton-bridge-proxy.service` are loaded and enabled but currently
+  `activating-auto-restart`.
+- rclone inventory: explicit Proton remote `about` probe succeeded with
+  redacted quota output only; no drive file names or file contents were listed.
+
+## Result
+
+The profile runtime snapshot now records Proton Bridge systemd convergence as a
+must-fix gap. The aggregate `personal-agent` runtime state remains degraded.
+
+This proof does not read or store mail bodies, mail subjects, sender or
+recipient addresses, contact details, calendar event details, drive file names,
+drive file contents, endpoint payloads, credentials, cookies, Keychain values,
+password-manager values, or secret values.