Add job-application package: 3 primary projects, 5 daily cover-letter drafts

[dl1413]

Summary

Adds job_applications/ — the scaffolding the daily "5 apps in NYC or
remote" routine writes into.

• job_applications/README.md fixes the three primary projects used
  across every daily package: AI Safety Red-Team Evaluation, LLM
  Ensemble Textbook Bias Detection, and RAG Production Pipeline. (The
  Breast Cancer Classification benchmark stays in the portfolio but
  isn't featured in the archetype letters, which are aimed at LLM/AI-
  forward employers where the LLM triad tells a tighter story.)
• job_applications/2026-09-07/ is the first day's package — five
  cover-letter drafts, one per role archetype:
  1. Frontier AI lab — safety / model evaluations
  2. NYC fintech / quant — data scientist
  3. LLM evaluation / observability startup
  4. RAG / applied-LLM systems engineer (remote)
  5. Big-tech / enterprise applied data scientist
• Each letter has {COMPANY} / {ROLE_TITLE} / {HIRING_MANAGER} /
  {ROLE_SPECIFIC_HOOK} placeholders for per-opening personalization.
• tracker.md in the day folder logs which of the five got sent.

Design notes

• Letters are drafts, not submissions. Derek picks the specific
  openings, fills placeholders, reviews, and sends.
• The three primary projects are named and quantified in the package
  README so subsequent daily runs stay consistent.
• No source-tree changes; the portfolio validator still passes
  (python3 scripts/validate_portfolio.py).

Test plan

• python3 scripts/validate_portfolio.py — passes.
• Derek reviews the archetype coverage — flag any archetype that
  shouldn't be on the list, or an obvious one that's missing.
• Derek confirms the three primary projects are the right three
  to standardize on.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ahs38oZdrYz2hfJo3byPXw

---

Generated by Claude Code

[dl1413]

CI status — portfolio check failing at queue time

Both attempts of the Validate portfolio workflow on this PR aborted
before any step ran:

Attempt	Job runtime	Logs	Check output
1 (auto on push)	2s	HTTP 404	empty
2 (re-run I triggered)	2s	HTTP 404	empty

For context, prior successful runs of this same workflow on this repo
took 7–17s (they include actions/checkout + actions/setup-python@v5
for Python 3.12 + running scripts/validate_portfolio.py). A 2-second
completion with no step output and 404 logs means the job never made
it out of the queue.

Why it isn't the diff: This PR only adds files under a new
job_applications/ directory. scripts/validate_portfolio.py only
walks README.md and project_packages/*/README.md as indexes
(see validate_local_links() in scripts/validate_portfolio.py), so
the new files aren't reachable to it. I ran python3 scripts/validate_portfolio.py
locally against this exact commit and it reports:

Portfolio validation passed: 4 projects and all index links are valid.

What likely blocks it: an account- or repo-level Actions setting
that changed between the last successful run (2026-08-03) and this
one (2026-09-07) — the usual suspects are exhausted Actions minutes,
Actions being restricted or disabled for PR events, or a workflow-
permissions tightening. All of those need to be resolved in repo /
account settings rather than in the diff, so I've spent my one re-run
without pushing a speculative code fix.

What to check on your side:

• github.com/settings/billing → Actions minutes remaining
• Repo Settings → Actions → General → Actions permissions (still "Allow all actions"?) and Workflow permissions
• Repo Settings → Actions → General → Fork pull request workflows — if this changed, PR runs from branches created by non-owner actors can be blocked

I'm keeping the PR watched; ping when the Actions issue is sorted and
I'll re-check.

---

Generated by Claude Code