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.

docs/work-programmes/master-progress.md

@@ -2,18 +2,18 @@
 
 Updated: 2026-08-10
 
-- **Overall programme status:** Active. Seven packages are locally verified; nineteen packages through CAREER-002 are implemented with automated/runtime evidence but blocked from applicable browser/provider/production gates; MAIL-001 is in progress with ten committed implementation increments. Gitea run 608 confirms DEP-001 cleared the remote dependency audit; its later stale Career Workspace smoke assertion is corrected locally (4/4 Playwright) and awaits replacement CI.
-- **Current work package:** `MAIL-001` — consolidated job-email hub and explicit sending (`IN PROGRESS`); routing/reads/detail, ledger, Gmail/Graph delivery/re-consent, safe send API/UI, recovery, legacy SMTP retirement and content-free export/job-cascade coverage are committed. Local empty/disconnected and legacy-route browser smoke passes partially. Shared provider actions/capability behavior is next; full account deletion stays SEC-009.
+- **Overall programme status:** Active. Seven packages are locally verified; nineteen packages through CAREER-002 are implemented with automated/runtime evidence but blocked from applicable browser/provider/production gates; MAIL-001 is in progress with eleven committed implementation increments. Gitea run 609 passes complete pull-request CI in 4m20s; DEP-001 now awaits approved merge-to-main and production verification only.
+- **Current work package:** `MAIL-001` — consolidated job-email hub and explicit sending (`IN PROGRESS`); routing/reads/detail, ledger, Gmail/Graph delivery/re-consent, safe send API/UI, recovery, legacy SMTP retirement and content-free export/job-cascade coverage are committed. The dedicated Application Workspace now supplies the same contextual suggestion contract as the job dialog. Shared provider actions/capability behavior is next; full account deletion stays SEC-009.
 - **Completed work packages:** None are `DONE`; all repository security/AI packages still have applicable browser, provider and/or production gates.
 - **Locally verified work:** SEC-001, SEC-002, SEC-003, SEC-005A, CORE-001, PROD-002 and DEP-001 (`VERIFIED LOCALLY`).
 - **Implemented, verification incomplete:** SEC-004, SEC-005B, SEC-008, CORE-002, BG-001, OPS-001A/B/C, POL-001/002, AI-001/002/003/004, UX-001/002, QA-001, CAREER-001 and CAREER-002 (`IMPLEMENTED — NOT VERIFIED`). CAREER-002 now protects unsaved edits and provides tested structured custom-entry, profile-override and preview-error interactions; all automated/build gates pass.
 - **Production-verified work:** None.
-- **Blocked work:** SEC-006 parser upgrades remain outside the scoped frontend advisory permission; PROD-001/003/004 and REL-001 require documented production access and unfinished dependencies. Real provider, SMTP/MariaDB and production environments are unavailable; DEP-001 awaits replacement CI plus live verification. The in-app browser is available for local UI checks.
+- **Blocked work:** SEC-006 parser upgrades remain outside the scoped frontend advisory permission; PROD-001/003/004 and REL-001 require documented production access and unfinished dependencies. Real provider, SMTP/MariaDB and production environments are unavailable; DEP-001 awaits approved merge/live verification. The in-app browser is available for local UI checks.
 - **Deferred work:** None. Conditional multi-replica coordination, model deletion, realtime operation delivery and unrelated production changes remain outside current packages.
 - **Next five work packages:** MAIL-001 consolidated email experience; JOBS-001 job-search/application redesign; HOME-001 homepage/Pro promotion; UX-003 authentication/profile polish; PRODUCT-001 homepage/Pro claims. SEC-006/007 resume after package-index permission.
 - **Status counts:** 7 `VERIFIED LOCALLY`; 19 `IMPLEMENTED — NOT VERIFIED`; 1 `IN PROGRESS`; 8 `NOT STARTED`; 5 `BLOCKED`; 0 `DONE`; 0 `DEFERRED`.
-- **Test status:** backend 622/622; frontend 49/49 suites and 190/190 tests; Playwright smoke 4/4; npm audit 0 vulnerabilities; DEP-001 focused router 24/24 and production build pass; MAIL-001 export/cascade 16/16, recovery/send 10/10, legacy follow-up/backend worker 10/10, legacy UI 2/2, composer 7/7, delivery/capability 18/18, provider/correspondence 5/5 and hub detail 5/5. Jest open-handle/slow-run behavior is recorded in V-127/V-128/V-130/V-131/V-135.
-- **Deployment status:** Gitea pull-request run 608 passed `Audit frontend dependencies`, then failed at the stale Career Workspace Playwright assertion. The assertion fix passes 4/4 locally and is being pushed for replacement CI. Deploy runs only on `main`, so live remains unchanged. No deployment was performed directly, no production migrations were run and the AI operation worker remains disabled by default.
+- **Test status:** backend 622/622; frontend 50/50 suites and 192/192 tests; Playwright smoke 4/4; npm audit 0 vulnerabilities; DEP-001 focused router 24/24 and production build pass; MAIL-001 shared context 10/10, export/cascade 16/16, recovery/send 10/10, legacy follow-up/backend worker 10/10, legacy UI 2/2, composer 7/7, delivery/capability 18/18, provider/correspondence 5/5 and hub detail 5/5. Jest open-handle/slow-run behavior is recorded in V-127/V-128/V-130/V-131/V-135/V-142.
+- **Deployment status:** Gitea pull-request run 609 passed the complete CI job in 4m20s. Deploy was intentionally skipped because the workflow deploys only a `push` to `main`; live remains unchanged. No merge/deployment was performed directly, no production migrations were run and the AI operation worker remains disabled by default.
 - **Production status:** Unchanged and unverified. No provider/model call, model pull, external request or paid API occurred.
 - **Known regressions:** None found by automated/local browser checks. Jest still needs `--forceExit` and reports its existing open-handle notice. Email-provider/send tests are fake/local only; real delivery is not claimed. Current MAIL browser evidence is 1280×720 only because the browser surface could not resize or perform native Tab traversal. Interrupted attempts are aged after 15 minutes and notified without retry; the five-minute scan is unmeasured on a large ledger. Direct clean EF-only SQLite migration still hits the pre-existing historical blank-chain defect before later migrations; normal startup owns reconciliation. Cross-feature monthly AI usage accounting remains a rollout gap.
 - **Outstanding security findings:** JT-001 repository ownership remains High deployment risk until migration/inventory/provider checks; production portion of JT-002; JT-006/JT-009 and associated JT-011/JT-012/JT-022 prerequisites. JT-005 foundations are implemented; AI worker activation awaits controlled rollout. JT-007/JT-008/JT-010 lack browser/provider/production verification.

docs/work-programmes/master-work-plan.md

@@ -651,8 +651,8 @@ Ordering differences from the suggested list:
 - **Required production verification:** provider read/draft/send requires explicit authorized synthetic account; never real unsolicited email.
 - **Status:** `IN PROGRESS`.
 - **Blocker:** real provider verification is external; required 375/768/1440/theme/keyboard browser gates were unavailable in the current browser surface. Mocked/local repository implementation remains unblocked.
-- **Evidence:** `docs/verification/mail-001-job-email-hub.md`; V-126–V-140. Export/cascade focused 16/16; recovery/send focused 10/10; legacy follow-up/worker 10/10; composer 7/7; delivery/capability 18/18; provider/correspondence 5/5; hub detail 5/5; backend 622/622; frontend 49/49 suites and 190/190 tests plus build/audit; local empty/disconnected and compatibility-route browser smoke at 1280×720.
-- **Commit:** `6008b4a` (hub), `536d403` (neutral reads), `a20775c` (safe detail), `653f011` (ledger), `e9937ac` (Gmail/Graph delivery adapters and consent), `123fc55` (explicit-confirmed send API), `449faeb` (confirmed reply composer), `ee5ef7e` (interrupted-send recovery), `8fe3903` (legacy SMTP retirement), `aff34cc` (content-free export and cascade evidence).
+- **Evidence:** `docs/verification/mail-001-job-email-hub.md`; V-126–V-142. Shared application context focused 10/10; export/cascade focused 16/16; recovery/send focused 10/10; legacy follow-up/worker 10/10; composer 7/7; delivery/capability 18/18; provider/correspondence 5/5; hub detail 5/5; backend 622/622; frontend 50/50 suites and 192/192 tests plus build/audit; local empty/disconnected and compatibility-route browser smoke at 1280×720.
+- **Commit:** `6008b4a` (hub), `536d403` (neutral reads), `a20775c` (safe detail), `653f011` (ledger), `e9937ac` (Gmail/Graph delivery adapters and consent), `123fc55` (explicit-confirmed send API), `449faeb` (confirmed reply composer), `ee5ef7e` (interrupted-send recovery), `8fe3903` (legacy SMTP retirement), `aff34cc` (content-free export and cascade evidence), `ff547df` (shared application context).
 - **Remaining work:** full account deletion remains SEC-009; durable/new-message drafts; shared thread/application actions and category capabilities; free/pro and browser/production verification. Existing connections need explicit re-consent; IMAP remains read-only. No real email; uncertain sends need manual reconciliation.
 
 ### JOBS-001 — Job-search source and assessment redesign
@@ -759,9 +759,9 @@ Ordering differences from the suggested list:
 - **Required production verification:** CI audit and live deployment from the fixed commit.
 - **Status:** `VERIFIED LOCALLY`.
 - **Blocker:** final deployment verification depends on the remote CI/live environment.
-- **Evidence:** `docs/verification/dep-001-frontend-advisories.md`; V-137/V-141; audit 0 vulnerabilities, focused 24/24, full 190/190 and production build pass; Gitea run 608 passed the dependency audit and exposed an unrelated stale browser assertion, corrected with local Playwright 4/4.
+- **Evidence:** `docs/verification/dep-001-frontend-advisories.md`; V-137/V-141; audit 0 vulnerabilities, focused 24/24, full 190/190 and production build pass; Gitea run 609 passed complete pull-request CI in 4m20s after the stale browser assertion correction.
 - **Commit:** `b55a592` (pushed).
-- **Remaining work:** observe the replacement CI run, merge/deploy from `main`, run production route smoke and update to `DONE` only after production verification.
+- **Remaining work:** approved merge/deploy from `main`, production route smoke and update to `DONE` only after production verification.
 
 ### REL-001 — Production validation and remaining audit closure
 

docs/work-programmes/session-handoff.md

@@ -3,16 +3,16 @@
 Updated: 2026-08-10
 
 - **Exact current task:** MAIL-001 — trace shared provider-neutral thread/application actions and implement only capabilities the existing providers can safely support.
-- **Last completed step:** inspected public Gitea run 608 logs: the dependency audit passes remotely, while the job failed later on stale Career Workspace copy. Replaced that assertion with the stable CV Builder route action; full local Playwright passes 4/4.
-- **Files currently modified:** the focused Playwright assertion plus DEP-001/progress/verification/decision tracking; no unrelated files.
-- **Commands already run:** dependency tree/advisory review; `npm audit`; router/full frontend/build; legacy follow-up/backend worker/UI; export/backup/daily worker/cascade focused tests; full backend; Gitea status/log inspection; full `npm run test:e2e`. See V-126–V-141.
-- **Test results:** npm audit 0 vulnerabilities; remote dependency-audit step PASS; router focused 24/24; frontend 49/49 suites and 190/190 tests; Playwright 4/4; production build passes. MAIL-001 export/cascade focused 16/16, legacy follow-up/backend worker 10/10, legacy UI 2/2 and full backend 622/622 pass.
+- **Last completed step:** Gitea run 609 passed complete pull-request CI in 4m20s. MAIL-001 shared application context then removed the workspace `null as any`; focused 10/10, full frontend 192/192 and production build pass.
+- **Files currently modified:** DEP-001/MAIL tracking only; shared context implementation is committed as `ff547df`.
+- **Commands already run:** dependency tree/advisory review; `npm audit`; router/full frontend/build; legacy follow-up/backend worker/UI; export/backup/daily worker/cascade focused tests; full backend; Gitea status/log inspection; full `npm run test:e2e`; MAIL context focused/full frontend/build. See V-126–V-142.
+- **Test results:** npm audit 0 vulnerabilities; Gitea pull-request CI PASS in 4m20s; router focused 24/24; frontend 50/50 suites and 192/192 tests; Playwright 4/4; production build passes. MAIL-001 shared context 10/10, export/cascade focused 16/16, legacy follow-up/backend worker 10/10, legacy UI 2/2 and full backend 622/622 pass.
 - **Services currently running:** none on task-owned ports 3000/5202. Playwright stopped its disposable API/Next servers. Pre-existing Docker services were not changed.
 - **Temporary files or processes:** disposable local user `audit-mail-20260810@example.test`, its local session, two synthetic screenshots and a startup-created local database backup. The API applied already-committed pending development migrations to the local development database. No provider account, real email, private content, paid service or production service was accessed.
 - **Production changes currently active:** none. No deployment, migration, provider connection/sync/send or production payload occurred.
 - **Rollback status:** revert `ee5ef7e` to stop recovery, then `449faeb` to remove the composer; keep admission disabled before reverting `123fc55`/`e9937ac` and downgrade the ledger before reverting `653f011`. No production migration/deploy/provider grant occurred.
-- **Uncommitted changes:** focused CI smoke assertion and its tracking only; review, commit and push as one deployment-fix package.
-- **Known failures:** replacement CI and live deployment are not yet verified. Durable/new-message drafts, full thread/category actions and non-Gmail review remain; existing accounts need re-consent and IMAP stays read-only. Browser/provider/MariaDB/production unavailable or unverified; recovery scan performance is unmeasured at large ledger scale; Jest open handles; SEC-006 parser dependency work is still separately gated; parser isolation remains SEC-007.
-- **Exact next action:** commit/push the Career Workspace smoke correction, observe replacement CI, then inventory Gmail/Graph/IMAP read/unread/archive/pin/read-later/spam/trash contracts and job-workspace embedding. Do not invent unsupported cross-provider actions; expose capability differences and reuse the canonical detail/link domain.
+- **Uncommitted changes:** tracking for `ff547df` and remote CI run 609 only; commit and push before the next implementation increment.
+- **Known failures:** live deployment is not verified because PR deploy is intentionally skipped and the active branch is not approved for merge. Durable/new-message drafts, full thread/category actions and non-Gmail review remain; existing accounts need re-consent and IMAP stays read-only. Browser/provider/MariaDB/production unavailable or unverified; recovery scan performance is unmeasured at large ledger scale; Jest open handles; SEC-006 parser dependency work is still separately gated; parser isolation remains SEC-007.
+- **Exact next action:** commit/push the tracking for `ff547df`, then design explicit provider capability reporting before any Gmail modify/Graph read-write scope expansion. Do not invent unsupported cross-provider actions.
 - **Work that can continue independently:** remaining MAIL-001 repository work and later UX packages. SEC-006/007 await package-index permission; PROD-001/003/004 await production access.
 - **Decisions still required from the user:** none for synthetic/code-inspected repository work. Any provider connection or send test, internet/package upgrades, private data, external/paid providers and production actions retain explicit approval/safety gates; SEC-009 retention/legal policy remains unresolved.