docs(plan): advance to job discovery
This commit is contained in:
@@ -184,3 +184,4 @@ Output was reduced to filenames and commit counts. The token artifact appears un
|
||||
| V-150 | Focused correspondence-inbox Jest; full frontend Jest; production build; staged diff review | `job-tracker-ui` / repository root | Verify explicit reply-draft save, refresh-resume, server identity adoption, conflict handling and safe post-send cleanup | PASS — focused 11/11; frontend 50/50 suites and 196/196 tests; TypeScript/production build pass; save accepts incomplete reply, resume preserves private text, 409 keeps local edits visible, discard/delete and sent cleanup use revision | JSDOM/mocked API only; browser/provider/send/production not exercised; Jest retains existing force-exit notice | Reply recovery verified locally; new-message and durable failed-attempt rotation remain |
|
||||
| V-151 | Focused `EmailDraftsControllerTests`; full backend; focused/full correspondence-inbox Jest; production build; staged diff review | Repository root / `job-tracker-ui` | Verify persisted delivery identity rotates only after the matching definitive failure | PASS — draft API 5/5; backend 630/630; inbox 12/12; frontend 50 suites/197 tests; build pass; no ledger row/refused, failed/rotated, stale/refused and foreign/not-found paths pass; `29de263` pushed | Synthetic SQLite and mocked UI only; two npm commands were initially run from repository root and failed environmentally before correct-directory reruns passed; no provider/send/production action | Durable failed-attempt rotation verified locally |
|
||||
| V-152 | Focused/full correspondence-inbox Jest; production build; accessible-role inspection; staged diff review | `job-tracker-ui` / repository root | Verify new-message drafting uses an owned job and connected send-capable provider while reusing draft/send safety | PASS — inbox 13/13; frontend 50 suites/198 tests; build pass; owned paged jobs load, read-only provider is excluded, selectors have accessible names, empty job/re-consent guidance is visible, and saved new message uses null thread; `b735963` pushed | JSDOM/mocked APIs only; hub selector is bounded to 100 recent owned jobs; browser/provider/send/production not exercised | New-message repository flow verified locally |
|
||||
| V-153 | Complete Phase 9 requirement reread; provider interface/scope/controller inventory; canonical hub and embedded correspondence action comparison | Repository root | Determine whether safe independent MAIL-001 implementation remains | PASS/PARTIAL — routing, suggestions/dismissal, link/relink/unlink, shared saved domain, provider-neutral reads/detail, reply/new-message drafts and explicit send are implemented; Gmail modify/Graph read-write and IMAP outgoing/category contracts are absent, so read/unread/pin/read-later/archive/spam/trash cannot be honestly enabled | Source inspection only; no provider/re-consent/browser/production action. Full SEC-009 deletion and real-provider gates remain | Repository scope implemented; external/authority verification blocked |
|
||||
|
||||
Reference in New Issue
Block a user