Cut v1.9.0

[crypticpy]

Stable release record: records-only promotion of the accepted v1.9.0-rc.7 candidate per work package 8, step 1 — no template behaviour change since rc.7.

• package.json / package-lock.json: 1.9.0-rc.7 → 1.9.0; CHANGELOG gains the [1.9.0] promotion section and compare links; README upgrade example and plan/ledger version strings updated.
• Release ledger: candidate bullet promoted to the stable release; RR-H01 rc.7 leg closed (candidate PR Cut v1.9.0-rc.7 #54 b97432b + human-reviewed BCHC PR #34 929b007); RR-H08: candidate soak accepted by the release owner (gate stays In progress — the one-business-day observation of the deployed stable update per WP8 remains the tracked open leg) — rc.7 deployment soaked clean 2026-08-28T18:29Z→2026-08-29T08:17Z (29 half-hourly probes: 200 homepage, versioned search index, zero failed default-branch workflow runs, window absorbed the live rollback drill), on top of the superseded rc.6 soak (30 clean probes, ~15h); no P0/P1 defect observed.
• npm run verify recorded at cut commit 05008c2: 799 Node tests / 3 suites, 233 Ruby tests / 578 assertions, 109 build-matrix tests / 6 suites, plus every non-browser release gate. The head differs from that commit only by the evidence sentence.

Per docs/maintaining.md governance this PR needs maintainer review and merge — after merge I will publish the immutable v1.9.0 tag at the merge commit, publish release notes, and run the BCHC updater against the tag to generate the stable update PR (also maintainer-merged).

🤖 Generated with Claude Code

https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD

Summary by Sourcery

Promote the verified v1.9.0-rc.7 candidate to the v1.9.0 stable release and update its release records.

Enhancements:

• Promote the accepted v1.9.0-rc.7 candidate to the v1.9.0 stable release without changing template behavior.
• Record the completed candidate verification, downstream update, rollback, and deployment soak evidence while tracking the remaining stable-tag handoff gates.

Build:

• Update the package and lockfile versions from v1.9.0-rc.7 to v1.9.0.

Documentation:

• Add the v1.9.0 changelog entry and comparison links, and update release-readiness records and upgrade documentation for the stable version.

Tests:

• Record the successful release verification results for the stable release cut.

[sourcery-ai]

Reviewer's Guide

This records-only release PR promotes v1.9.0-rc.7 to stable 1.9.0, synchronizes version and release documentation, and updates the readiness ledger with rc.7 review, deployment-soak, rollback, and exact-commit verification evidence; publication of the immutable stable tag and the downstream BCHC updater remain post-merge steps.

Sequence diagram for the v1.9.0 stable promotion and downstream update

sequenceDiagram
    actor Maintainer
    participant PHCT
    participant BCHC
    participant Pages

    Maintainer->>PHCT: Review and merge stable release record
    Maintainer->>PHCT: Publish immutable v1.9.0 tag
    Maintainer->>BCHC: Run updater against v1.9.0
    BCHC-->>BCHC: Generate machine-verified update pull request
    Maintainer->>BCHC: Review and merge stable update pull request
    BCHC->>Pages: Deploy v1.9.0
    Pages-->>Maintainer: Verify live stable deployment

Loading

Flow diagram for rc.7 acceptance to stable release readiness

flowchart LR
    RC7[v1.9.0-rc.7 candidate] --> Review[RR-H01 rc.7 review and BCHC update accepted]
    Review --> Soak[RR-H08 deployment soak passes]
    Soak --> Verify[npm run verify passes at 05008c2]
    Verify --> Promote[Records-only promotion to v1.9.0]
    Promote --> Pending[Stable tag and BCHC updater remain post-merge]

Loading

File-Level Changes

Change	Details	Files
Promote the accepted release candidate to the stable 1.9.0 version without changing application or template behavior.	Update npm package metadata and lockfile from rc.7 to 1.9.0. Add the stable changelog entry and rc.7-to-1.9.0 comparison link. Update the README upgrade example to target the stable version. Replace candidate terminology with stable-release terminology in the readiness plan and status record.	package.json package-lock.json CHANGELOG.md README.md docs/release-readiness-plan.md docs/release-readiness-status.md
Close the documented release-readiness evidence for the rc.7 candidate and record the stable-cut verification state.	Record the immutable rc.7 commit, downstream BCHC consumption, human review, rollback evidence, and remaining stable-tag handoff. Mark the RR-H01 rc.7 leg complete while retaining review requirements for this release record and the future stable BCHC update. Mark the release-owner-approved RR-H08 Pages soak as Pass with probe, workflow, rollback-window, and defect results. Update the verification evidence to reference commit 05008c2 and its test and release-gate results.	docs/release-readiness-status.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-08-29T08:42:46.259414Z	1b60cbf	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1b60cbf8db

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[sourcery-ai]

Sourcery assessment

Approved.