v1.9.0

Stable release of the 1.9.0 line. Records-only promotion of
v1.9.0-rc.7
— no template behaviour changes since rc.7. Cut from protected main via
release-record PR #56.

The 1.9.0 line at a glance

• Search that scales — worker-backed index with concept matching beyond
  exact keywords, interaction-latency budgets enforced to 1,000 entries.
• Staleness/refresh cycle — monthly verification sweep opens refresh
  reminders per stale entry; refresh-entry issue flow stamps the schema's
  own verified-date key.
• "Also deployed by" — other organizations attach their implementation
  info to an existing entry through a dedicated issue flow.
• Security signals — per-entry security posture surfaced from repository
  metadata.
• Full details per release candidate in the
  CHANGELOG.

Release evidence

• npm run verify at cut commit 05008c274352846f6661728a5f35042428305da4:
  799 Node tests across 3 suites, 233 Ruby tests with 578 assertions,
  109 build-matrix tests across 6 suites, plus every non-browser release gate.
• RR-H08 soak: rc.7 deployment ran clean on the intended Pages configuration
  2026-08-28T18:29Z → 2026-08-29T08:17Z (29 half-hourly probes; no P0/P1
  defect), accepted by the release owner; the window absorbed the live
  rollback drill (BCHC PRs #35/#36 — revert and byte-identical roll-forward
  both proven through required checks, Pages redeploys and live verification).
• Exact update rehearsal: rc.7 consumed by the live updater
  (run 33144777338
  → machine-verified
  BCHC PR #34,
  merged after human review).
• Full ledger: release-readiness status.

Upgrading

Run Update from PHCT (workflow_dispatch with release=v1.9.0) in your
deployment, or npm run upgrade:check -- --to v1.9.0 for a read-only preview.
No ownership-contract changes since rc.6, so no migration is required first.

Rollback point

v1.9.0-rc.7 at b97432bc1d5298407046e599248bc62a6f09ce37.

🤖 Generated with Claude Code