Cut v1.9.0-rc.4

[crypticpy]

Release-record PR for v1.9.0-rc.4, cut from protected main at the merged head of the non-coder workflow audit remediation (#32, f22c67b277cc6005d8217410b4ab7aa56827b846).

What this PR contains

• package.json / package-lock.json bumped to 1.9.0-rc.4.
• CHANGELOG.md gains the 1.9.0-rc.4 entry summarizing PR fix: make every maintainer-facing flow legible to a non-coder #32 (submitter-reply coverage on every issue-form exit, updater legibility + reachable no-op, scheduled-workflow explanations, wizard repository guard with case-insensitive positive detection, docs walkthrough consolidation) and back-fills the missing rc.3/rc.4 compare links.
• docs/release-readiness-status.md re-dated with the rc.4 candidate evidence; docs/release-readiness-plan.md candidate line advanced to v1.9.0-rc.4.

Verification

• npm run validate — passed.
• npm test — 657/657 passed.

After merge: tag v1.9.0-rc.4 at the merge commit, publish release notes, then run BCHC's Update from PHCT with the exact tag (rc.3 precedent: BCHC PR #6). Rollback point: v1.9.0-rc.3 at a9741c9845e0928ec6b6654e6e04b6ebe71c2233.

🤖 Generated with Claude Code

Summary by Sourcery

Prepare the v1.9.0-rc.4 release candidate with workflow audit fixes, clearer user guidance, and updated release-readiness records.

New Features:

• Add issue-form diagnostics and schedule-update previews to make common workflow failures and replacement effects visible.
• Improve scheduled workflow and setup-wizard guidance for disabled modules, failures, repository configuration, and submission errors.

Bug Fixes:

• Ensure all issue-form content workflows provide clear responses for every exit path, including re-edits, no-op submissions, closed forms, and permission failures.
• Make downstream release updates produce complete run summaries and safely handle unchanged releases and tag validation.
• Improve workflow error handling, sweep limits, metrics reporting, and attachment updates.

Enhancements:

• Consolidate settings and administration guidance across the launch, admin, and maintenance documentation.

Build:

• Bump the package version to 1.9.0-rc.4.

Documentation:

• Update release documentation and readiness evidence for the 1.9.0-rc.4 candidate, including BCHC rc.3 provenance and corrected release comparison links.

[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 hour and 29 minutes 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.4 from the merged non-coder workflow audit remediation, synchronizes package and changelog metadata, repairs compare links, and updates release-readiness documentation with candidate provenance, verification status, rollback information, and BCHC handoff state.

Flow diagram for rc.4 release readiness

flowchart TD
    Baseline[PR 32 merged and verified] --> Metadata[Version and lock metadata updated]
    Metadata --> Docs[Changelog and readiness docs updated]
    Docs --> Validate[npm run validate]
    Validate --> Tests[npm test: 657 of 657 passed]
    Tests --> Candidate[rc.4 candidate ready]
    Candidate --> Gates{Manual and live-demo gates pass?}
    Gates -->|No| Hold[Hold wider demo and stable release]
    Gates -->|Yes| Handoff[Tag rc.4 and update BCHC]

Loading

File-Level Changes

Change	Details	Files
Records the v1.9.0-rc.4 release and documents the audited non-coder workflow remediation included in the candidate.	Adds the rc.4 changelog entry covering issue-form response coverage, updater behavior, scheduled-workflow diagnostics, wizard repository protection, and documentation updates. Adds and corrects release comparison links, including the rc.3 and rc.4 ranges.	CHANGELOG.md
Advances package metadata to the rc.4 version.	Updates the package version in both manifest and lockfile.	package.json package-lock.json
Refreshes release-readiness evidence for the rc.4 candidate and its downstream handoff state.	Updates the candidate version, evidence date, source merge commit, CI/CodeQL status, and rc.3 rollback lineage. Records that BCHC is currently on rc.3 pending the exact-tag rc.4 update.	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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 993ce8a653

ℹ️ 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".