docs: record the 2026-08-28 gate evidence and the rc.7 requirement

[crypticpy]

Dated evidence update to docs/release-readiness-status.md for the work completed against the rc.6 candidate on 2026-08-28:

• RR-H02 complete for rc.6 — live updater pass with the fail-closed contract gate proven, plus rollback proof (clean revert of c0826d9 back to the full rc.5 state)
• RR-H03 complete — real form → PR chore(deps-dev): bump eslint from 10.8.1 to 10.9.0 in the npm group #27 with real media → merge → Pages → live verification, then removed via BCHC fix: make every maintainer-facing flow legible to a non-coder #32
• RR-H05 — 2026-08-28 read-only API audit synced into the operations inventory (BCHC Cut v1.9.0-rc.3 #31/Cut v1.9.0-rc.4 #33); four admin items remain manual
• RR-H07 — four of six drills passed (template update, backup/restore, rollback, takedown); credential-response and owner-transfer open
• RR-H08 — one-business-day soak running since 2026-08-28T03:35Z
• RR-H09 complete for rc.6 — 187 links checked; one live finding (the "Ask in the open" links 404 until Discussions is enabled)

Also records the sequencing consequence of merging #49: the stable cut now requires a v1.9.0-rc.7 candidate and one more updater pass before promotion.

Docs-only; no behaviour change.

🤖 Generated with Claude Code

https://claude.ai/code/session_014sAVayAT2tkQ7p9U2o9CsD

Summary by Sourcery

Record the latest rc.6 release-readiness evidence and reset the stable promotion target to require an rc.7 candidate and one additional updater validation.

Enhancements:

• Update release-readiness evidence through 2026-08-28, recording completed rc.6 validation, rollback, deployment, operations-audit, drill, soak, and link-check results.
• Document the remaining release gates and the requirement for a v1.9.0-rc.7 candidate with another downstream updater pass before stable promotion.

Documentation:

• Refresh the release-readiness status documentation with current evidence, outstanding manual checks, and deployment findings.

[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 (collapsed on small PRs)

Reviewer's Guide

This docs-only update brings release-readiness status current through 2026-08-28, captures rc.6 validation and operational evidence, documents remaining gaps and the live-link finding, and records that PHCT PR #49 necessitates an rc.7 candidate plus another BCHC updater pass before stable promotion.

Sequence diagram for the rc.6 BCHC updater and rollback evidence

sequenceDiagram
    participant Maintainer
    participant Updater
    participant Gate as ContractGate
    participant BCHC as BCHCRepository

    Maintainer->>Updater: Run updater for v1.9.0-rc.6
    Updater->>Gate: Validate ownership contract
    Gate-->>Updater: Pass fail-closed gate
    Updater->>BCHC: Create machine-verified update
    Maintainer->>BCHC: Review and merge BCHC PR #30
    Maintainer->>BCHC: Revert c0826d9
    BCHC-->>Maintainer: Restore full v1.9.0-rc.5 state

Loading

Flow diagram for rc.7 release promotion sequencing

flowchart LR
    RC6[v1.9.0-rc.6] --> Evidence[Validate rc.6 gates]
    Evidence --> PR49[Merge PHCT PR #49]
    PR49 --> RC7[Cut v1.9.0-rc.7]
    RC7 --> Updater[Run one more BCHC updater pass]
    Updater --> Stable[Promote stable release]

Loading

Flow diagram for documented rc.6 readiness evidence

flowchart TD
    Live[rc.6 live on Pages] --> H03[Real form to PR to deploy verified and removed]
    Live --> H07[Four operational drills passed]
    Live --> H08[One-business-day soak running]
    Live --> H09[187 links checked]
    H09 --> Finding[Three Ask in the open links 404 until Discussions is enabled]
    H07 --> Open[Credential-response and owner-transfer drills remain open]

Loading

File-Level Changes

Change	Details	Files
Refresh the release-readiness checkpoint with dated rc.6 evidence and the resulting rc.7 sequencing requirement.	Advance the evidence date to 2026-08-28 and document the rc.6 updater run, ownership-contract gate, merge, rollback proof, and subsequent PHCT changes. Record that stable promotion now requires v1.9.0-rc.7 and another updater pass.	docs/release-readiness-status.md
Replace stale readiness statuses with evidence-backed results for the human and live operational gates.	Mark rc.6 updater/rollback and real submission-to-Pages/takedown rehearsal complete. Sync the read-only operations audit and identify four remaining manual administration checks. Record four completed operational drills, the active one-business-day soak, and two remaining drills. Mark external-link validation complete with the Discussions-related 404 finding documented.	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: 01cf8e80aa

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