cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(plan): advance to job discovery
CI and Deploy / test (pull_request) Successful in 4m30s
Details
CI and Deploy / deploy (pull_request) Has been skipped
Details

Browse Source
This commit is contained in:
cesnimda
2026-08-10 10:31:40 +02:00
parent 289b3bec18
commit 986f58522b
5 changed files with 29 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/work-programmes/decisions.md
+10
View File
@@ -599,3 +599,13 @@
- **Consequences:** empty-job and missing-send-consent states explain why compose is unavailable. The hub currently lists the 100 most recent owned jobs; older jobs remain accessible from their job workspace and broader searchable selection is follow-up UX, not a hidden authorization bypass.
- **User approval required:** No; local UI work uses mocked APIs and sends no message.
- **Reversible:** Revert `b735963`; reply drafting and all server draft/send boundaries remain.
## DEC-061 — Stop MAIL scope at installed provider authority
- **Date:** 2026-08-10
- **Decision:** Mark MAIL-001 `IMPLEMENTED — NOT VERIFIED` after completing the repository draft/send/link flows. Do not add read/unread, pin/read-later, archive, spam or trash UI because the installed Gmail/Graph/IMAP contracts and granted scopes do not authorize those mutations.
- **Reason/evidence:** Phase 9 says these states apply where supported. Current Gmail adds read/send, Graph adds read/send, and IMAP is read-only; the neutral interface exposes read/detail/send only. Displaying or simulating category actions would be false capability and production-risking scope creep.
- **Alternatives considered:** request modify/read-write scopes silently; mutate only JobTracker copies while labelling them provider actions; add disabled controls; keep MAIL indefinitely in progress. These broaden consent, misrepresent mailbox state, clutter UX or block independent work.
- **Consequences:** real-provider re-consent, provider category design, browser gates, SEC-009 deletion and production verification remain explicit blockers before `DONE`. JOBS-001 becomes the sole in-progress item.
- **User approval required:** No for status correction; any future provider-scope/re-consent rollout needs a separately reviewed package and safe account verification.
- **Reversible:** Yes. MAIL-001 can return to `IN PROGRESS` when provider mutation authority is approved and testable.