13 lines
1.2 KiB
Markdown
13 lines
1.2 KiB
Markdown
# S03: Reply and follow-up drafting from real thread context
|
|
|
|
**Goal:** Make follow-up drafting use imported correspondence and saved application material well enough that the job workspace can produce specific, trustworthy follow-up and reply drafts without crossing the manual-send boundary.
|
|
**Demo:** After this: Inside a job, the user can generate follow-up and reply drafts grounded in imported and automatically refreshed correspondence plus saved application context, then edit them before sending manually.
|
|
|
|
## Tasks
|
|
- [x] **T01: Strengthen follow-up draft context assembly and backend reply/follow-up tests** —
|
|
- Files: JobTrackerApi/Controllers/JobApplicationsController.cs, JobTrackerApi.Tests/JobApplicationsFollowUpDraftTests.cs
|
|
- Verify: `dotnet test JobTrackerApi.Tests/JobTrackerApi.Tests.csproj --filter JobApplicationsFollowUpDraftTests`
|
|
- [x] **T02: Make the follow-up workspace show thread-grounded draft state without autonomous sending** —
|
|
- Files: job-tracker-ui/src/components/JobDetailsDialog.tsx, job-tracker-ui/src/types.ts, job-tracker-ui/src/job-details-followup-drafts.test.tsx
|
|
- Verify: `CI=true npm --prefix job-tracker-ui test -- --watch=false --runTestsByPath src/job-details-followup-drafts.test.tsx`
|