feat: harden gmail sync foundation
This commit is contained in:
@@ -0,0 +1,40 @@
|
||||
# Smart Gmail Job Correspondence Integration Progress
|
||||
|
||||
## Branch
|
||||
- feat/gmail-job-correspondence
|
||||
|
||||
## Status
|
||||
- Workstream initialized.
|
||||
- Milestones planned: M006-M010.
|
||||
- Current focus: M006 / S01 foundation work.
|
||||
|
||||
## Completed so far
|
||||
- Created separate Gmail feature branch.
|
||||
- Captured foundation context in `.gsd/milestones/M006/M006-CONTEXT.md`.
|
||||
- Planned milestones M006-M010 for the Gmail workstream.
|
||||
- Planned slice M006/S01.
|
||||
- Confirmed existing architecture seams:
|
||||
- Gmail OAuth/token flow already exists.
|
||||
- Per-job Gmail candidate search/import/thread refresh already exists.
|
||||
- Correspondence persistence already stores Gmail thread/message metadata.
|
||||
- Current implementation is job-local, not global-inbox/review oriented.
|
||||
- Implemented M006/S01 foundation changes:
|
||||
- durable Gmail sync-state fields on `GmailConnection`
|
||||
- SQLite/MySQL bootstrap support for new Gmail sync-state columns
|
||||
- richer `GET /api/gmail/status` response
|
||||
- per-job correspondence UI now shows sync diagnostics
|
||||
- focused backend/frontend Gmail tests added and passing
|
||||
- Phase 2 extension seam scaffolded with a no-op enrichment service
|
||||
- Phase 1/2 design doc added at `docs/gmail-correspondence-phase1.md`
|
||||
|
||||
## Next tasks
|
||||
1. Implement M006/S01/T01: refactor Gmail connection foundation and sync-state model.
|
||||
2. Implement M006/S01/T02: expose sync-state surfaces in UI without breaking current correspondence workflow.
|
||||
3. Implement M006/S01/T03: prepare Phase 2 extension seam/docs.
|
||||
4. Verify backend + frontend Gmail focused tests.
|
||||
5. Commit and push incremental progress.
|
||||
|
||||
## Resume notes
|
||||
- Previous CV/parsing branch work is separate and already pushed.
|
||||
- Local dev SQLite runtime still has missing-table drift in some unrelated surfaces (`RuleSettings`, `Companies`, etc.); avoid conflating that with the Gmail feature work.
|
||||
- Existing per-job Gmail tests live in `JobTrackerApi.Tests/GmailControllerTests.cs` and `job-tracker-ui/src/correspondence-gmail-import.test.tsx`.
|
||||
Reference in New Issue
Block a user