v1.2.0

## Why update

**A privacy correction leads this release.** SETUP.md used to say your fork is "private working space" - it is not: forks of public GitHub repositories are always public and cannot be made private, so that sentence pointed people toward committing personal profile data somewhere anyone could read it. Section 8 now states the fork-is-public fact plainly and documents the safe setup (a **private repository** with this repo as the `upstream` remote), and `/setup` now ends with a privacy note at the exact moment your profile data first lands in git-tracked files. If you currently push personalization to a public fork, read the updated [SETUP.md section 8](SETUP.md#8-pulling-upstream-updates-into-your-fork) before your next push. (Thanks @rasstamann, discussion #266.)

Pairing with it: `tools/check_upstream_updates.py` no longer reports a false "up to date with upstream" when a fork without an `upstream` remote silently falls back to comparing against itself - the default state of a plain fork clone. It now tells you the comparison is fork-vs-self and shows the exact `git remote add upstream` command. In other words, the update checker this release note tells you to run actually works in a fresh fork now. (Thanks @oscarbol09, #265.)

## Also in this release

- **`/rank` persists its per-job `strengths` and `gaps` into `seen_jobs.json`** instead of discarding them after the terminal output, replaced (never accumulated) on `--all` re-ranks - so downstream consumers can read real triage findings. First half of the #258 proposal by @NotAbdelrahmanelsayed; the `/upskill` consumer side is in review as #264.
- **Two more personal-data gitignore rules are now CI-guarded** (`cover_letters/Cover_*.*`, `cv/*.txt`) - the rules already existed; now weakening them fails CI. (Found via a review-bot triage on @jakob1379's fork.)
- CONTRIBUTING's "run what CI runs" list is complete (it omitted `security_guards.py` and the exact `unittest` command - thanks @jakob1379, #262), the vestigial `cover_letters/OpenFonts/cover.cls` is gone, and #252's ragged-row fix gained regression tests.

## For fork maintainers

No `framework_version` bumps in this span - none of the personalized methodology files (01-08, the assistant SKILL.md, AGENTS.md) changed, so `git merge v1.2.0` should land without conflicts in profile-bearing files. Full details in [CHANGELOG.md](CHANGELOG.md).