docs(email): record provider state evidence

2026-08-10 09:46:38 +02:00
parent f9e641c23b
commit 4efee0726a
6 changed files with 31 additions and 13 deletions
@@ -509,3 +509,13 @@
 - **Consequences:** a thread can be reconsidered in recruitment review after unlink. Imported JobTracker copies are removed only after confirmation, while the mailbox remains untouched. Relink/move stays on the existing per-job management surface for now.
 - **User approval required:** No; this is local implementation of the approved MAIL-001 unlink workflow and uses only mocked/synthetic data.
 - **Reversible:** Yes. Revert `1dabbeb`; the endpoint and per-job unlink remain available, with no schema/provider grant change.
+
+## DEC-052 — Report only capabilities the connection can use
+
+- **Date:** 2026-08-10
+- **Decision:** Distinguish disconnected, connected-without-read, read-only/re-consent, read-plus-send and provider-status failure in the canonical hub. Keep saved correspondence visible during provider-status failure.
+- **Reason/evidence:** the previous chip appended `Read only` even to disconnected providers and silently removed all provider context when the status request failed. Focused failure/capability tests, full frontend and build pass.
+- **Alternatives considered:** keep the ambiguous chip; hide the entire inbox on provider failure; infer archive/read-write support from provider name. These misstate capability, reduce failure isolation or invent authority not present in installed scopes.
+- **Consequences:** users can distinguish connection state from send consent and know saved data remains available. Mailbox organization actions remain absent until a reviewed provider contract and re-consent path exist.
+- **User approval required:** No; this corrects local state communication and invokes no provider.
+- **Reversible:** Yes. Revert `f9e641c`; no API, schema, scope or stored state changes.