Add job_applications/ with 2026-09-09 batch (5 tailored packages)

[dl1413]

Summary

Introduces job_applications/ for the daily scheduled routine that turns the
portfolio's projects into submission-ready application packages, and lands the
first day's batch (2026-09-09).

What's here

• job_applications/README.md — layout, per-day folder shape, submission
  workflow, and an explicit note that the routine drafts materials but does
  not authenticate to job boards or submit on the candidate's behalf.
• job_applications/2026-09-09/INDEX.md — five NYC-or-remote openings with
  the posting URL, the three projects highlighted, and a submission checklist.
• Five per-role cover-letter drafts, each ~450 words, leading with the three
  most relevant portfolio projects and citing the reported metrics from the
  technical reports:
  • 01_Anthropic_Alignment_Science.md — AI Safety Red-Team · LLM Ensemble Bias · RAG
  • 02_ScaleAI_LLM_Evals.md — AI Safety Red-Team · LLM Ensemble Bias · RAG
  • 03_Anthropic_Data_Science_Engineer.md — LLM Ensemble Bias · Breast Cancer · AI Safety Red-Team
  • 04_Bloomberg_ML_Engineer.md — RAG · AI Safety Red-Team · Breast Cancer
  • 05_TwoSigma_Quant_ML.md — Breast Cancer · LLM Ensemble Bias · AI Safety Red-Team

How to use

Open 2026-09-09/INDEX.md, follow each posting link, copy the drafted body
into the employer's form (or send by email where the file says), and tick
the checklist as you submit. Rows 4 and 5 are stretch fits (senior-leaning)
included as target-company applications; the framing leans on the M.S. +
independent-research portfolio.

Scope of automation

The routine drafts materials and points to live postings. Submission is a
manual step; postings may relocate between run day and submission day, so
verify the URL before you send.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JV9ooNaZe9by7CCrTAyeJq

---

Generated by Claude Code

[dl1413]

CI: portfolio check failing — not this PR's diff, no fix I can push.

Both attempts completed in 3–4s and produce no downloadable logs (HTTP 404 on the job log endpoint):

• attempt 1: job 102484778228 — failed in ~4s
• attempt 2 (re-run): job 102485363836 — failed in ~3s

That duration is shorter than checkout + actions/setup-python@v5 normally take, so the job is failing before the Validate project inventory and links step runs. The prior day's scheduled run (PR #104) showed the same pattern on a different diff, which rules out a regression from these files.

Verification that the validator itself is green on this head:

$ python3 scripts/validate_portfolio.py
Portfolio validation passed: 4 projects and all index links are valid.

The diff adds job_applications/ only. scripts/validate_portfolio.py inspects README.md and project_packages/*/README.md for its local-link pass and expects the four project reports/PDFs to exist — none of which this PR touches.

Root cause is most likely at the Actions permissions / runner-allocation layer (e.g. workflow runs from claude/* branches aren't allowed to execute on PRs), not the workflow body or the script. Fix options are outside a diff I can push:

1. In repo Settings → Actions → General, ensure "Allow all actions and reusable workflows" and that PRs from branches with the claude/* prefix are permitted to run workflows, or
2. Adjust the workflow trigger, e.g. gate the pull_request event on approved branches (or set runs-on: to a self-hosted runner if that's what the org expects).

Keeping the PR watched until it's green or closed. Re-run budget for this PR is spent; a next push (from any subsequent day's batch) will trigger a fresh attempt.

---

Generated by Claude Code