fix(apply): archive the job posting while /apply still holds it (#306) (#307)

/apply drafted two documents and a tracker row from the full posting, then
let the text die with the session. /outcome Step 3.2 tried to recover it by
re-fetching a `source` URL the spec itself expects to be dead, and a posting
pasted from an email or a PDF had no `source` to re-fetch at all.

Step 6b gains item 7: write the posting verbatim to
documents/applications/<company>_<role>/job_posting.md, never a re-fetch or a
reconstruction from memory. The folder is derived by citing /outcome Step 1.4
rather than restating the rule, so the two cannot drift. An existing file is
left alone and named in the report.

Step 0 and the /scrape path (job-application-assistant SKILL.md Step 1) now
retain the full posting text rather than a summary, so item 7 has something
verbatim to write.

Pinned by tests/test_apply_records_application.py.
This commit is contained in:
Jakob Stender Guldberg
2026-08-09 20:26:58 +02:00
committed by GitHub
parent e09d3eb37b
commit 0e1a895c4e
6 changed files with 81 additions and 8 deletions
+1 -1
View File
@@ -21,7 +21,7 @@ v1 preps for a **specific application**. Generic no-target practice is out of sc
## Step 1: Load the Application Context
1. **The archive** (maintained by `/outcome`): `documents/applications/<company>_<role>/`
1. **The archive** (started by `/apply`, maintained by `/outcome`): `documents/applications/<company>_<role>/`
- `job_posting.md` - the exact posting the user applied to
- `cv_draft.tex` and `cover_letter.tex` - what was actually submitted. **These are what the interviewer read**; every talking point must be consistent with their claims.
- `outcome.md` - the stage reached so far and any recorded feedback from earlier stages. Feedback from stage N is the highest-value input for stage N+1 prep.