Skip to content

docs: cut v3.0 scope (#608) — replace stale v2.2 line with substrate-completion + design tickets - #609

Merged
robotrocketscience merged 3 commits into
mainfrom
docs/v3-roadmap
May 10, 2026
Merged

docs: cut v3.0 scope (#608) — replace stale v2.2 line with substrate-completion + design tickets#609
robotrocketscience merged 3 commits into
mainfrom
docs/v3-roadmap

Conversation

@robotrocketscience

@robotrocketscience robotrocketscience commented May 10, 2026

Copy link
Copy Markdown
Owner

Summary

Cuts v3.0 scope. Three docs files (README.md, docs/ROADMAP.md, CHANGELOG.md) updated to replace the stale v2.2 "Next" line + ROADMAP row with v3.0 scope. Three atomic commits.

Closes part of #608 (the v3.0 milestone tracker — docs side; the substrate-completion work and design decisions are separate child issues that close the rest).

Why the v2.2 line was stale

The prior README "Next: v2.2" line and docs/ROADMAP.md v2.2 row referenced three issues that turned out to be stale:

What v3.0 contains

Substrate completion (existing open work):

  • #553 HRR persistence default-ON + split-format .npy+.npz migration
  • #542 wonder consolidation umbrella, with open sub-tasks #547 (B bake-off), #550 (C4 promotion trigger), #552 (E4 skill layer integration)
  • #434 type-aware compression
  • #152 HRR structural-query retrieve_v2 phase-2 wiring (phase 1 shipped v2.x)
  • #592 eval-harness wire for #587 hot-start scoring
  • #600 replay_post_fork host-agent JSONL split (PR feat(eval-harness): replay_post_fork host-agent JSONL split (closes #600) #601 in flight)

v3.0 design decisions (new tickets, filed fresh as part of this cut):

  • #605 v3.0 PHILOSOPHY: natural-language-relatedness gate — deterministic vs embedding
  • #606 sentiment-feedback hook production wire-up
  • #607 multimodel scope memo (re-evaluate post-wonder-dispatch)

Close-outs (separate ops, not in this PR):

  • #474 v2.1 milestone tracker — replaced by #608
  • #436 intentional clustering — default flip in this Unreleased CHANGELOG
  • #291 query understanding R1+R3 — PR-1/PR-2 shipped
  • #602 merge-thrash advisory — workflow shipped

Parked / deferred:

  • #480 adaptive half-life exploration, #476 PR-smoke fixtures license review, #594 + #593 doctor decisions-needed

GH state shipped alongside this PR

  • v3.0.0 milestone created (milestone/2)
  • v3.0 label created
  • 9 existing in-scope issues relabeled (v2.0 / v2.1v3.0) and assigned to the v3.0.0 milestone
  • 3 new issues filed (#605, #606, #607) and 1 umbrella tracker (#608)

Verification

  • README.md line 168 + docs/ROADMAP.md line 31 reference v3.0 issue numbers that all exist on GitHub
  • CHANGELOG.md Unreleased Documentation section gets one new entry
  • No source changes; no tests changed (docs-only)
  • git log --format='%G?' github/main..HEAD shows all signed commits

Summary by Sourcery

Update documentation to reflect the v3.0 scope and replace stale v2.2 references.

Documentation:

  • Refresh README and ROADMAP to describe v3.0.0 scope, including substrate-completion work and new design-decision tickets, instead of the outdated v2.2 plan.
  • Add an Unreleased CHANGELOG entry documenting the v3.0 scope cut and associated roadmap and labeling changes.

The v2.2 line referenced #197 (WONTFIX terminal — relatedness gate
punted to v3.0 philosophy decision), #193 (evaluation shipped; no
hook-integration successor existed), and #194 (mislabeled — was
ingest_turn(bulk=), shipped). All three references were stale.

v3.0 replaces the line with substrate-completion work (#553 / #542 /
#434 / #152 / #592 / #600) plus three v3.0 design tickets filed fresh
(#605 NL-relatedness philosophy, #606 sentiment-hook integration, #607
multimodel scope). Milestone tracker: #608.
Same rationale as the README change: the v2.2 row referenced three
stale issues (#197 WONTFIX, #193 evaluation-only, #194 mislabeled
ingest_turn(bulk=)). v3.0 row lists substrate-completion work plus
three fresh design tickets (#605 / #606 / #607) and points at the
v3.0 umbrella tracker (#608).
Explains the v2.2 → v3.0 roadmap replacement: the three v2.2 issues
referenced in README (#197, #193, #194) were all stale, and the v3.0
scope replaces them with substrate-completion work plus three fresh
design tickets (#605 / #606 / #607). Milestone tracker is #608.
@robotrocketscience robotrocketscience added the author-Planck PR coordination mutex label May 10, 2026
@sourcery-ai

sourcery-ai Bot commented May 10, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Docs-only PR that replaces stale v2.2 roadmap/README references with a new v3.0 scope description, and records this scope cut in the Unreleased CHANGELOG entry, aligning docs with the current v3.0 milestone, labels, and issues on GitHub.

File-Level Changes

Change Details Files
Update README "Next" line to describe v3.0 scope instead of stale v2.2 plan. README.md
Revise roadmap to swap the v2.2 planned row for a v3.0.0 planned row with updated scope and issue mapping. docs/ROADMAP.md
Record the v3.0 scope cut and doc updates as an Unreleased documentation CHANGELOG entry. CHANGELOG.md

Possibly linked issues


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

@coderabbitai

coderabbitai Bot commented May 10, 2026

Copy link
Copy Markdown

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: accd93a9-f750-4577-8d32-4aac4396625d

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 docs/v3-roadmap

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

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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • The new v3.0 entries in CHANGELOG and ROADMAP are quite dense and long; consider breaking them into shorter sentences or sub-bullets so the key scope items and ticket references are easier to scan.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new v3.0 entries in CHANGELOG and ROADMAP are quite dense and long; consider breaking them into shorter sentences or sub-bullets so the key scope items and ticket references are easier to scan.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@robotrocketscience

Copy link
Copy Markdown
Owner Author

[claim:review:noether:2026-05-10T23:28:34Z]

@robotrocketscience
robotrocketscience merged commit 00b5a9c into main May 10, 2026
22 of 30 checks passed
@robotrocketscience
robotrocketscience deleted the docs/v3-roadmap branch May 10, 2026 23:29
@robotrocketscience

Copy link
Copy Markdown
Owner Author

[release:review:noether:2026-05-10T23:29:39Z]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

attn:review Needs review (PR open, awaiting reviewer) author-Planck PR coordination mutex docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant