[kiwidream]

Version 3.0.0 and its release notes, cut on a new 3.0.x branch. 3.x.x has already moved on to 3.1.0-rc.1.

What 3.0.0 is

3.0.x starts at 4c134913 (#770), the last 3.x.x commit before the 3.1 dual-writer stack (#766–#769, #763, #773, #774). So 3.0.0 is rc.6 (81c592c3) plus the two fixes #772 prepared as rc.7, which was never tagged:

PR	Change
#760 12f1ae8e	#759: node RPC clients keep an idle connection for at most 20 s, below qbitd's 30 s idle close
#770 4c134913	#765: import-audits writes each legacy audit before SETTLEMENT_LOCK, and bounds each phase with PRISM_IMPORT_AUDITS_WRITE_TIMEOUT_MS / PRISM_IMPORT_AUDITS_LOCK_TIMEOUT_MS

No migration since rc.6. Migrations 027, 028 and 031 and the dual writer stay in 3.1.

Changes

• VERSION, [workspace.package].version and the workspace-member entries of both Cargo.lock files move to 3.0.0. These are the same lines 3.x.x: version 3.0.0-rc.7 and its release notes (#557) #772 bumps.
• doc/release-notes-3.0.0.md: the UNRELEASED banner is replaced with 3.0.0's header. 3.x.x: version 3.0.0-rc.7 and its release notes (#557) #772's rc.7 notes (changes since rc.6, upgrading, verification, known issues) are carried over, worded for 3.0.0. The existing D5 recovery contract is kept unchanged below them.
• doc/release-notes-3.x.x-development-line.md and docs/prism-rust-migration.md now say 3.0.0, using 3.x.x: version 3.0.0-rc.7 and its release notes (#557) #772's wording for the import-audits guidance.
• Dependency audit fix (f7ad2773): rustls 0.23.45 → 0.23.46 (RUSTSEC-2026-0346/0347/0348/0349), rustls-webpki 0.103.15 → 0.103.16 (RUSTSEC-2026-0382) and webpki-roots 1.0.9 → 1.0.10 (RUSTSEC-2026-0381), via cargo update --precise in both lockfiles, as 3.x.x: Update rustls to 0.23.45 for RUSTSEC-2026-0285 #354 did. Only these three patch releases change. 3.x.x has the same lockfile entries and will need the same update.
• Production wording (def1fa0d): with the coordinator's go-ahead, the development-line note's Status, Not done yet, and Upgrade and rollback sections, and the README banner, now describe 3.0.0 on 3.0.x as the production release. The 3.0.0 notes list the TLS update.

Checked locally

• scripts/check_version_skew.py, scripts/check_prism_settings.py and scripts/check_toolchain_pin.py pass.
• cargo metadata --locked passes for the root and fuzz workspaces.
• Relative links in both notes files resolve.
• cargo deny --locked check reports advisories, bans, licenses and sources ok.
• cargo check --locked --workspace --all-targets compiles.

Before merging and tagging

• Coordinator GO, given 2026-10-22 (also covers shipping DO NOT MERGE without coordinator GO: 3.x.x: drop an idle node connection after 20 s, below qbitd's 30 s idle close (#759) #760).
• Release date in the notes: 2026-10-22. Update it if the tag lands later.
• The development-line note and the README banner describe 3.0.0 as the production release.
• L3 doesn't run on PRs into 3.0.x; prism-load-l3.yml filters PRs to 3.x.x and main. Pushing the v3.0.0 tag runs l3-full. To get the evidence before tagging, dispatch it with ref=release/3.0.0 and tag_dry_run=true.
• CI's push trigger doesn't list 3.0.x, so after merging, dispatch CI on 3.0.x or the tag, as was done for rc.6.
• Afterwards: close 3.x.x: version 3.0.0-rc.7 and its release notes (#557) #772 as superseded, and decide whether main is consolidated from 3.0.x as v2.0.0 was (v2.0.0 chore: consolidate release for main #246).

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[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-10-22T15:30:59.620246Z	def1fa0	Draft marked ready

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

[kiwidream]

Promotion into main is #778, which is built on this branch's head 1d445a68. Per docs/releasing.md (only on main), v3.0.0 is tagged on #778's squashed commit on main, not on 3.0.x, so ignore this PR's tag-on-3.0.x steps. The L3 matrix runs on #778, since L3 triggers on PRs into main.