new vacancies

modes/_shared.md

@@ -122,6 +122,29 @@ After detecting archetype, read `modes/_profile.md` for the user's specific fram
 9. **Tracker additions as TSV** -- NEVER edit applications.md directly. Write TSV in `batch/tracker-additions/`.
 10. **Include `**URL:**` in every report header.**
 
+### Tracker-Additions TSV Format
+
+Write one TSV file per evaluation to `batch/tracker-additions/{num}-{company-slug}.tsv`. Single line, 9 tab-separated columns:
+
+```
+{num}\t{date}\t{company}\t{role}\t{status}\t{score}/5\t{pdf_emoji}\t[{num}](reports/{num}-{slug}-{date}.md)\t{note}
+```
+
+**Column order (IMPORTANT -- status BEFORE score):**
+1. `num` -- sequential number (integer)
+2. `date` -- YYYY-MM-DD
+3. `company` -- short company name
+4. `role` -- job title
+5. `status` -- canonical status (e.g., `Evaluated`)
+6. `score` -- format `X.X/5` (e.g., `4.2/5`)
+7. `pdf` -- `✅` or `❌`
+8. `report` -- markdown link, always written **root-relative**: `[num](reports/...)`
+9. `notes` -- one-line summary
+
+**Note:** In applications.md, score comes BEFORE status. The merge script handles this column swap automatically.
+
+**Report link normalization:** The TSV always carries a **root-relative** `[num](reports/...)` link. `merge-tracker.mjs` rewrites it so the link is relative to the tracker file's own directory before writing it into the tracker — `../reports/...` when the tracker is at `data/applications.md`, or `reports/...` at the root layout. This keeps links clickable from the tracker (markdown links resolve relative to the file that contains them). Normalization is idempotent. To fix links in an existing tracker, run `node merge-tracker.mjs --migrate` (see #760).
+
 ### Tools
 
 | Tool | Use |