docs: reconcile proton rclone runtime posture

docs/contracts/personal-agent-runtime-readiness-snapshot.json

@@ -35,7 +35,8 @@
       "health_source": "MCP registration plus local service inventory",
       "redacted_health": {
         "mcp_server_enabled": true,
-        "proton_bridge_systemd_running": true,
+        "proton_bridge_systemd_running": false,
+        "proton_bridge_systemd_state": "activating-auto-restart",
         "docker_email_gate": "exited-127",
         "raw_mail_observed": false
       },
@@ -49,7 +50,8 @@
       "redacted_health": {
         "mcp_server_enabled": true,
         "calendar_gate_running": true,
-        "proton_bridge_systemd_running": true,
+        "proton_bridge_systemd_running": false,
+        "proton_bridge_systemd_state": "activating-auto-restart",
         "raw_calendar_events_observed": false
       },
       "remaining_gap": "Calendar read has service posture but no governed package child runtime proof."
@@ -84,8 +86,8 @@
   ],
   "supervisor_posture": {
     "mac_mini_bluebubbles": "package-validator-ok-redacted",
-    "proton_bridge_service": "active-running",
-    "proton_bridge_proxy_service": "active-running",
+    "proton_bridge_service": "activating-auto-restart",
+    "proton_bridge_proxy_service": "activating-auto-restart",
     "rclone_rc_service": "disabled-inactive",
     "rclone_proxy_service": "disabled-inactive"
   },
@@ -108,6 +110,12 @@
       "state": "stale sdo-protonmail-bridge container exists in Created state",
       "impact": "duplicate service topology must be resolved before final runtime readiness"
     },
+    {
+      "id": "proton-bridge-systemd-auto-restart",
+      "severity": "must-fix",
+      "state": "proton-bridge.service and proton-bridge-proxy.service are activating with auto-restart",
+      "impact": "mail.read and calendar.read cannot claim stable runtime readiness"
+    },
     {
       "id": "proton-rclone-child-unregistered",
       "severity": "must-fix",
@@ -161,6 +169,7 @@
   "remaining_gates": {
     "proton_email_gate_repair": "blocked-follow-up",
     "proton_contacts_gate_repair": "blocked-follow-up",
+    "proton_bridge_systemd_convergence": "blocked-follow-up",
     "proton_rclone_child_registration": "blocked-follow-up",
     "secondbrain_durable_apply": "blocked-follow-up",
     "desktop_adapter_exposure": "blocked-follow-up",

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.