parent-sync

# parent-sync — parity release pipeline Proven across v1.119.0 (parent 1.19), v1.120.0 (1.20), v1.123.0 (1.21). Each phase below is a hard gate — do not skip, do not reorder. The parent repo (`..`) is **READ-ONLY** except the user-authorized `git pull` itself. **Also covers audit-driven patch releases** (no parent delta — e.g. v1.134.1 validation-hardening from a full-project + all-locales audit). Skip Phases 1–2 (no pull, no provider port); Phases 3–7 apply UNCHANGED — QA prompt, docs ×17, site changelog resync, wiki, cross-surface verify are all still mandatory. The count that moves on a fix-only release is usually just the **test count**. ## Phase 1 — Pull & scope 1. `cd .. && git rev-parse HEAD` (save OLD), `git pull`, `cat VERSION`. Diff by **commit range**, never by VERSION (release-please lags main). 2. Read the new CHANGELOG entries + `git diff OLD..HEAD --name-status`. 3. Classify every change: - `providers/*.mjs` **added** → PORT as a web-ui source+adapter (Phase 2). - Changes to code web-ui MIRRORS (`role-matcher`, `detect-reposts`, `trust-validator`, `scan-sanitize`, providers already ported, `cooldown`) → PORT the diff into `server/lib/` + port the parent's test cases. - Scripts web-ui RELAYS read-only (`stats.mjs`, `salary-gap.mjs`, `analyze-patterns.mjs`, `followup-*`) → usually NO code change (fail-soft relay absorbs shape changes) — note it. - CLI-only (modes/*.md prompts, updater, doctor, PDF templates, ledger/site ...