docs(email): track hub consolidation evidence
This commit is contained in:
@@ -369,3 +369,13 @@
|
||||
- **Consequences:** original entries use Hide rather than Delete; custom entries receive explicit destructive confirmation. Existing render/public/PDF/version data remains compatible.
|
||||
- **User approval required:** No; this preserves the programme's explicit Career Profile separation and existing data.
|
||||
- **Reversible:** Yes. Revert `a5b74e0` and `2043349`; settings JSON remains backward-compatible.
|
||||
|
||||
## DEC-038 — Job email has one canonical route with filtered compatibility redirects
|
||||
|
||||
- **Date:** 2026-08-09
|
||||
- **Decision:** Make `/correspondence` the canonical Job email hub and represent recruitment review as `?view=review`. Redirect the legacy `/correspondence/review` route into that filtered view while reusing the existing review component and APIs.
|
||||
- **Reason/evidence:** the two pages were separate navigation surfaces over related linked/review workflows, while the job workspace already reuses the same correspondence domain. Route composition removes duplicate information architecture without prematurely rewriting mature Gmail decision logic.
|
||||
- **Alternatives considered:** delete the old route immediately; copy review cards into the inbox; merge backend endpoints before a provider capability trace; keep both pages indefinitely. These break bookmarks, duplicate behavior, expand risk or preserve the approved UX defect.
|
||||
- **Consequences:** existing links remain compatible and there is one user-facing hub. Provider-neutral thread state and explicit draft/send remain separate MAIL-001 increments and are not implied by this routing change.
|
||||
- **User approval required:** No; the product decision to consolidate and preserve route compatibility is explicit.
|
||||
- **Reversible:** Yes. Revert `6008b4a`; no persisted correspondence/provider data changes.
|
||||
|
||||
Reference in New Issue
Block a user