---
title: T01 summary
status: done
files:
  - JobTrackerApi/Controllers/JobApplicationsController.cs
  - JobTrackerApi.Tests/JobApplicationsApplicationPackageTests.cs
observability_surfaces:
  - POST /api/jobapplications/{id}/generate-application-package
  - JobApplicationsApplicationPackageTests in JobTrackerApi.Tests/JobApplicationsApplicationPackageTests.cs
  - persisted package fields and notes markers on JobApplication records after generation/save loops
verification:
  - $HOME/.dotnet/dotnet build JobTrackerApi/JobTrackerApi.csproj
  - $HOME/.dotnet/dotnet test JobTrackerApi.Tests/JobTrackerApi.Tests.csproj --filter JobApplicationsApplicationPackageTests
---

Strengthened application-package generation so it now consumes imported correspondence and recruiter/job context instead of relying mostly on job description text plus the profile CV.

## What changed

- `JobTrackerApi/Controllers/JobApplicationsController.cs`
  - added `BuildCorrespondenceContextAsync(...)` to gather recent imported correspondence, participants, thread ids, and AI-derived package signals
  - enriched `generate-application-package` context with:
    - recruiter name/email and greeting baseline
    - imported correspondence context from S01
    - existing saved job material (tailored CV / cover letter / recruiter message) when present
    - job URL in the package context
  - updated prompts so tailored CV, cover letter, application answer, recruiter message, and variants all explicitly use imported correspondence when helpful without crossing the manual-send boundary
  - expanded `KeyPoints` to include correspondence-derived and attachment-derived signals
- `JobTrackerApi.Tests/JobApplicationsApplicationPackageTests.cs`
  - added focused backend proof that package generation reacts to imported correspondence and recruiter context rather than falling back to generic output

## Diagnostics

- Call `POST /api/jobapplications/{id}/generate-application-package` on a job that already has imported correspondence; inspect whether the response package now includes recruiter-aware wording, correspondence-derived `keyPoints`, and non-generic draft content.
- Check `JobTrackerApi.Tests/JobApplicationsApplicationPackageTests.cs` first when the package feels generic; it is the narrowest automated proof that imported correspondence and recruiter context reach the generator.
- If runtime output looks weak, inspect the job record and linked `Correspondence` rows first; this generator now depends on persisted correspondence quality rather than only the raw job description.

## Verification Evidence

| Command | Exit code | Verdict | Duration |
|---|---:|---|---|
| `$HOME/.dotnet/dotnet build JobTrackerApi/JobTrackerApi.csproj` | 0 | PASS | 4.8s |
| `$HOME/.dotnet/dotnet test JobTrackerApi.Tests/JobTrackerApi.Tests.csproj --filter JobApplicationsApplicationPackageTests` | 0 | PASS | 8.4s |