release: v3.4.0

[yoshi280]

Cuts v3.4.0 from the changelog [Unreleased] backlog accumulated since v3.3.0.

What ships (runtime)

• Conversation-aware UserPromptSubmit retrieval (hook: UserPromptSubmit ranking surfaces irrelevant beliefs while load-bearing beliefs in the same index are skipped #909) — recent turns folded into the BM25 query; default-on, opt-out via [user_prompt_submit_hook] conversation_aware_query_enabled. Deterministic, no embeddings.
• p3_substantive cadence policy wired live in Stop + UPS dispatchers, with shadow-log capture of all four policies (feat(cadence): P3 turn-density-aware policy — design scoping (#749 P3) #876). Default-OFF.
• aelf cadence-score four-policy pairwise comparison + offline cadence replay bench (feat(cadence): P3 turn-density-aware policy — design scoping (#749 P3) #876).
• Fix: audit writes skipped for :memory: DBs (no more stray hook_audit.jsonl in CWD).

Release mechanics

• pyproject.toml 3.3.0 → 3.4.0, uv.lock re-resolved.
• CHANGELOG/v3.md: [Unreleased] dated as ## [3.4.0] - 2026-05-26, compare-link footnote added, fresh empty [Unreleased] opened.
• README "Latest stable" pointer bumped to v3.4.0.

Tag v3.4.0 (→ publish.yml → PyPI) is applied after this merges and staging-gate is green, per the release process.

Summary by Sourcery

Cut the v3.4.0 release from the existing unreleased changes and update project metadata accordingly.

New Features:

• Document the new p3_substantive cadence policy, aelf cadence-score comparison tooling, and conversation-aware UserPromptSubmit retrieval in the v3.4.0 changelog.

Bug Fixes:

• Document that audit writes are now skipped for in-memory (:memory:) databases in the v3.4.0 changelog.

Build:

• Bump the project version from 3.3.0 to 3.4.0 in pyproject.toml and refresh the uv.lock for the release.

Documentation:

• Add a v3.4.0 section to the changelog with a compare link and update the README to mark v3.4.0 as the latest stable release.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Prepares and documents the v3.4.0 release by cutting the accumulated Unreleased notes into a dated changelog section, updating compare links, and bumping project/version metadata and README pointers to the new stable version.

Flow diagram for v3.4.0 release cut and metadata updates

flowchart TD
    A[Unreleased_changes] --> B[CHANGELOG_v3_md_update_to_3_4_0]
    B --> C[Update_compare_links]
    C --> D[pyproject_toml_version_3_4_0]
    D --> E[README_md_latest_stable_3_4_0]
    E --> F[Merge_to_default_branch]
    F --> G[tag_v3_4_0_and_publish]

Loading

File-Level Changes

Change	Details	Files
Cut the accumulated Unreleased notes into a new v3.4.0 section and update changelog compare links.	Insert a dated 3.4.0 section under the Unreleased header and ensure the new features and fixes are documented there. Adjust the Unreleased compare link to start from v3.4.0 instead of v3.3.0. Add a new compare-link reference for v3.4.0 pointing from v3.3.0 to v3.4.0.	CHANGELOG/v3.md
Update public documentation to identify v3.4.0 as the latest stable release.	Change the latest stable version string and date to v3.4.0 and 2026-05-26. Update the inline changelog section reference to point to the 3.4.0 entry.	README.md
Bump the project package version and refresh the lockfile for the v3.4.0 release.	Increment the project version field from 3.3.0 to 3.4.0 for packaging and distribution. Regenerate the dependency lockfile to align with the 3.4.0 release metadata.	pyproject.toml uv.lock

---

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.

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (2)

• docs:
• release:

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b462efbb-51f0-41e9-81d4-932f840b936b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v3.4.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

PR-size soft cap

This PR is over the advisory size threshold:

• 14 changed lines (limit: 200)
• 4 changed files (limit: 3)

Bigger PRs collide with more open work, which under the parallel-session workflow tends to produce repeated attn:merge-conflict cycles (see #602). When practical, split into smaller PRs that each touch a focused surface.

This is advisory only — nothing is blocked. If the size is intentional (large refactor, module removal, generated code), apply the size:override label and this comment will be removed on the next push.

[sourcery-ai]

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

---

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.}

[robotrocketscience]

Superseded by v3.5.0. The v3.4.0 backlog (#876 / #909 / audit-write fix) lands in the v3.5.0 release under its own [3.4.0] changelog section; no separate v3.4.0 tag will be cut. New release PR incoming.