docs: v3.0.1 sweep — README Status + ROADMAP rows (#791) - #794
Conversation
v3.0.1 fully released 2026-05-14T15:53Z (tag 2026-05-13T20:41Z, PyPI publish 2026-05-13T20:42Z run 25825264439). The README Status section still pointed at v3.0.0 as the latest stable. Bump both the version label and the CHANGELOG anchor in the per-entry-detail link.
v3.0.1 shipped 2026-05-13 (pipx-no-more install-surface collapse #730 + auto-migrate #733 + follow-up #774; search-tool/Bash hooks default-on #738; cross-fire dedup ring #740; authlib CVE-2026-44681 bump). The roadmap table ended at v3.0.0 with no v3.0.1 row even though the CHANGELOG and README already track it.
Mirrors the v3.0.0 subsection structure: one paragraph framing the release plus a per-feature bullet list (install-surface collapse #730, auto-migrate #733/#774, default-on agent-side retrieval hooks #738, cross-fire dedup ring #740, transitive authlib CVE-2026-44681 bump). Sits under '## Planned' for consistency with v3.0.0 — the section name has been a misnomer since v1.7.0 shipped, but reorganising that header is out of scope for this docs sweep.
There was a problem hiding this comment.
Sorry @robotrocketscience, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
[claim:review:pascal:2026-05-14T16:37:00Z] |
|
Reviewed: 3 atomic signed commits, +12/-1, docs-only diff. Verified content against
CI: all green (pytest 3.12/3.13, secrets-scan, pattern-scan, history-scan, release-docs-check, bench-smoke, typos, all prefix/link checks). Discretion grep on diff: clean. All commits SSH-signed (G). FF on main. Labeling ready-to-merge. |
|
[release:review:pascal:2026-05-14T16:38:46Z] |
|
merge-train: merged 385b8e3 → |
Closes #791 (partial — see "What's still open" below)
Docs sweep for v3.0.1. Three atomic commits closing the highest-signal staleness from the #791 checklist.
What's in the diff
docs(readme): bump Status section v3.0.0 -> v3.0.1— README line 169 still pointed at v3.0.0 as the latest stable; v3.0.1 has been tagged + published to PyPI + GitHub-released since 2026-05-13.docs(roadmap): add v3.0.1 row to versions-at-a-glance table— ROADMAP's table ended at v3.0.0. New row carries the same theme phrasing as v3.0.0.docs(roadmap): add v3.0.1 'What shipped' subsection— Mirrors the v3.0.0 subsection: one framing paragraph + per-feature bullets (Collapse install/upgrade surface to uv-only #730 install collapse, Auto-migrate non-uv aelfrice installs to uv tool on first 3.0.1 setup #733/fix(lifecycle): runnable uv install one-liner when maybe_migrate_to_uv hits uv-not-found #774 auto-migrate, Flip default: search-tool + search-tool-bash hooks on by default #738 default-on agent-side retrieval, Cross-fire injection dedup: amortize search hooks against the UPS-fire memory block #740 dedup ring, authlib CVE-2026-44681 bump).What's NOT in this PR (verified non-stale)
Items from the #791 checklist that I checked against
github/mainb2287ef6and found already-current:README.mdheadline NOTE (> v1.0 ships the surface ...) — no such line exists in the README; the checklist item points at copy that's already been removed.README.mdInstall / 60-seconds blocks — alreadyuv tool install aelfriceper the Collapse install/upgrade surface to uv-only #730 collapse; no new install-time commands shipped in v3.0.1.docs/INSTALL.mdoptional extras / post-install verification — already references v3.0.1+ at the search-tool hook rows (lines 146-147).docs/RELEASING.mdpytest count — the file deliberately doesn't pin a count (uv run pytest tests/ -x -q # track the actual count in CI), so there's nothing to refresh.docs/COMMANDS.md— every CLI subcommand that ships ongithub/mainis already documented; the opening paragraph doesn't carry a total count.docs/MCP.md— "fifteen memory tools" matches@mcp.tooldecorator count insrc/aelfrice/mcp_server.py(15).docs/SLASH_COMMANDS.md— "Nineteen markdown files" matchessrc/aelfrice/slash_commands/*.mdcount (19).docs/BENCHMARKS.mdactivation-status / version label — no adapter status changed in v3.0.1.docs/LIMITATIONS.md— none of the listed known-issue items shipped a resolution in v3.0.1.The "next-version" rows in README/ROADMAP point at v3.1 work that hasn't crystallised yet — keeping the existing pointers is the right call until v3.1 scope ratifies.
Verification
G).pytest tests/unaffected (docs-only).github/main: clean.Out of scope