docs(email): record shared context evidence

docs/work-programmes/decisions.md

@@ -489,3 +489,13 @@
 - **Consequences:** wording can evolve without breaking CI while the page-to-builder navigation contract remains protected. Replacement CI and live deployment verification are still required.
 - **User approval required:** No; this is a focused correction to a stale test exposed by the user-authorized deployment repair.
 - **Reversible:** Yes. Revert the focused smoke change, though run 608 would fail again until the expectation or page behavior is reconciled.
+
+## DEC-050 — Share correspondence context without broadening mailbox authority
+
+- **Date:** 2026-08-10
+- **Decision:** Give the shared correspondence component a minimal company/recruiter/role context contract and supply it from both the job dialog and Application Workspace. Do not add provider mutation buttons or scopes in this increment.
+- **Reason/evidence:** the workspace reused the correct correspondence domain but passed `null as any`, so its suggestion surface lost job context. Gmail currently grants readonly plus send, Graph grants read plus send, and IMAP is read-only; none has a safe read/write mutation seam. Focused tests and the full frontend/build pass.
+- **Alternatives considered:** duplicate the correspondence implementation; expand the workspace aggregate with a full job object; silently request Gmail modify/Graph read-write scopes; display unsupported actions. These add coupling, authority or misleading behavior.
+- **Consequences:** both application surfaces now generate the same optional contextual searches without automatic linking. Provider category mutations remain explicit remaining work that requires a separately reviewed scope/re-consent design.
+- **User approval required:** No; this is a local shared-view correction inside active MAIL-001 and invokes no provider.
+- **Reversible:** Yes. Revert the context-prop changes and test; stored data, scopes and provider grants are unchanged.