docs(roadmap): mark v1.3+v1.4 shipped; #148 merged on v1.5; #216 to v1.6; fix #141→#188 - #230
Merged
Merged
Conversation
…188 v1.5 line: annotate #148 BM25F as merged (commit 86c62b5), correct dynamic-trigger revisit issue ref from #141 to #188. v1.6 line: add #216 (Plate FFT HRR primitives) — relabeled from v1.5 to v1.6 since it's an HRR prereq for #152, which itself sits on v1.7. #204 stays on v1.5 (its schema is already merged on main under v1.5.0 banner; backfill is the remaining v1.5 work).
The 'Versions at a glance' table marked v1.3.0 and v1.4.0 as planned, and the body still listed them under the 'Planned' section, despite v1.3.x retrieval-wave commits and the v1.4.0 release tag (#185, 2026-04-28) being on main. README's roadmap table already showed both as shipped, so README and docs/ROADMAP.md disagreed. - Table: flip v1.3.0 and v1.4.0 to shipped, fold the README's more specific wording back into ROADMAP for consistency. - Body: move v1.3.0 and v1.4.0 subsections out of '## Planned' into the end of '## What shipped'; tighten verbs to past-tense; relink the dynamic-trigger revisit to the live tracker (#188 instead of the resolved #141 closer); point the full-posterior eval at v1.6.0/#151 (the new home per the v1.5/v1.6/v1.7 split) rather than v2.0 directly. - v1.2.x search-tool hook stays in Planned (still unshipped; #155 is the v1.5 follow-up).
robotrocketscience
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
belief_versions/edge_versions+version_vector_backfill_completemarker) is already merged onmainunder the v1.5.0 banner per the in-source comments; remaining backfill is the v1.5 work that keeps the issue open.docs/ROADMAP.mdto reflect that v1.3.0 and v1.4.0 actually shipped. README's roadmap table already showed both as shipped (release tag release: v1.4.0 #185 landed 2026-04-28); ROADMAP's "Versions at a glance" table and "Planned" section still listed them as planned. Move the v1.3 and v1.4 subsections from "Planned" to "What shipped", tighten verbs to past-tense, and relink the dynamic-trigger revisit ([v1.4] Rebuilder trigger modes — manual, threshold, dynamic #141 → [v1.5] Dynamic-trigger revisit — captured-corpus calibration retest #188).Originally moved #204 to v1.6 alongside #216 in the issue-label sweep; reverted after spotting that the schema had already shipped.
Test plan
#148, mergedand#188#216