33 lines
2.0 KiB
Markdown
33 lines
2.0 KiB
Markdown
---
|
||
title: T01 summary
|
||
status: done
|
||
files:
|
||
- JobTrackerApi/Controllers/JobApplicationsController.cs
|
||
- JobTrackerApi.Tests/JobApplicationsApplicationPackageTests.cs
|
||
verification:
|
||
- $HOME/.dotnet/dotnet build JobTrackerApi/JobTrackerApi.csproj
|
||
- docker run --rm -v "$PWD":/src -w /src mcr.microsoft.com/dotnet/sdk:9.0 bash -lc '...dotnet test /tmp/apptests/AppPkgTests.csproj...'
|
||
---
|
||
|
||
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
|
||
|
||
Verification:
|
||
- Native backend build passed with `$HOME/.dotnet/dotnet build JobTrackerApi/JobTrackerApi.csproj`
|
||
- Focused application-package backend test passed in an isolated Docker harness (`1 passed`)
|
||
|
||
Important caveat:
|
||
- As with S01 backend verification, the repository’s broader `JobTrackerApi.Tests` project still has unrelated compile drift, so the focused package test was isolated instead of relying on the full test project.
|