Cut v1.9.0-rc.7

[crypticpy]

Release record for the seventh candidate: version and lock to 1.9.0-rc.7, a Fixed changelog section for the two rc.6 refresh-cycle robustness fixes (#49, merged at af54f2810ed9d94fbfbb9b92ecf500ceaba18ddb), the upgrade preview and executable plan ledger retargeted from rc.6 to rc.7, and the readiness evidence brought current (candidate provenance, the completed PHCT leg of the RR-H03 rehearsal via #51/#52/#53, and the recorded npm run verify pass at f1e5699f147ce770137cc50d3d7c86c372c83a37: 799 Node / 233 Ruby / 109 build-matrix tests, all gates green).

Per governance this release pull request is yours to merge. After it merges I will:

1. create the immutable v1.9.0-rc.7 tag on the merge commit and publish candidate notes with full SHA and rollback point,
2. run the BCHC updater against v1.9.0-rc.7 so it opens the machine-verified update PR (also yours to merge).

🤖 Generated with Claude Code

https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD

Summary by Sourcery

Prepare the v1.9.0-rc.7 release candidate with refresh-cycle fixes, updated version metadata, and current release-readiness evidence.

Bug Fixes:

• Correct refresh-reminder guidance to use each catalog’s configured verified-date field.
• Prevent large verification sweeps from exceeding runner output limits when passing drafted reminder issues between steps.

Enhancements:

• Record the v1.9.0-rc.7 release candidate and update upgrade, release-planning, and readiness documentation to reference it.
• Refresh release-readiness evidence with the latest candidate provenance, PHCT rehearsal completion, and verification results.

Build:

• Bump the package and lockfile version to 1.9.0-rc.7.

Documentation:

• Add the v1.9.0-rc.7 changelog entry and comparison links.
• Retarget upgrade instructions and release procedures from rc.6 to rc.7.

[sourcery-ai]

Sorry @crypticpy, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 day and 3 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's Guide

This release-record PR cuts v1.9.0-rc.7 by synchronizing package metadata, changelog and upgrade documentation, while updating candidate provenance and readiness evidence to reflect the two rc.6 robustness fixes, current verification results, and completed PHCT rehearsal work.

Sequence diagram for rc.7 release and BCHC update

sequenceDiagram
    participant Maintainer
    participant PHCT
    participant BCHC

    Maintainer->>PHCT: Merge release-record PR
    Maintainer->>PHCT: Create immutable v1.9.0-rc.7 tag
    Maintainer->>PHCT: Publish candidate notes
    Maintainer->>BCHC: Run BCHC updater against v1.9.0-rc.7
    BCHC-->>Maintainer: Open machine-verified update PR
    Maintainer->>BCHC: Review and merge update PR

Loading

Flow diagram for verification sweep data handoff

flowchart LR
    Sweep[Verification sweep] --> TempFile[Draft issue bodies in runner temp file]
    Sweep --> Outputs[count, slugs, max_new]
    TempFile --> FollowUp[Follow-up step]
    FollowUp --> Reminders[Refresh reminders using entry.verified_key]

Loading

File-Level Changes

Change	Details	Files
Promote the release candidate and synchronize version references and release links.	Bump package and lock metadata to 1.9.0-rc.7. Retarget upgrade documentation, release-plan milestones, and changelog comparison links from rc.6 to rc.7. Define the rc.7 changelog entry covering the two refresh-cycle robustness fixes.	package.json package-lock.json CHANGELOG.md README.md docs/polish-and-publish-plan.md
Refresh release-readiness evidence and provenance for the rc.7 candidate.	Record rc.7 provenance after the rc.6 refresh fixes and preserve the immutable rc.6 lineage. Update verification evidence to the current commit and test totals: 799 Node, 233 Ruby, and 109 build-matrix tests. Document completion of the PHCT leg of the RR-H03 rehearsal and update remaining readiness status.	docs/release-readiness-plan.md 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.