adityamukho · Oct 24, 2026 · Oct 24, 2026
@@ -190,8 +190,8 @@ See `docs/TEST_COVERAGE.md` for the full per-file breakdown.
 
 Current plan (see `ROADMAP.md` and the milestones):
 - **v2.x** (`main`, format v7) now gets only data-integrity and security fixes as patch releases (v2.0.3 is the first); v2.0.2 was the last planned v2.x release.
-- **v3.0.0** (format v8 and data integrity, tracker #383) is developed on the long-lived `v3` branch. Do not merge `main` into `v3` routinely: `main` only gets backports of fixes already on `v3`. Shared CI and workflow changes land on both branches as separate PRs. Just before the v3.0.0 cut, merge `main` into `v3` once (merge commit; source conflicts resolved to `v3`, `main`'s v2.0.x CHANGELOG sections brought over) so the cut is a fast-forward.
-- **v3.next** (the release after v3.0.0) holds new features (query profiler #185, `:limit` #306/#310, lag/lead #182, UniFFI additions).
+- **v3.0.0** (format v8 and data integrity, plus `:limit` #306, query profiler #185, set membership predicates #316 and UniFFI `PreparedQuery`/UDF registration #181/#180; tracker #383) is developed on the long-lived `v3` branch. Do not merge `main` into `v3` routinely: `main` only gets backports of fixes already on `v3`. Shared CI and workflow changes land on both branches as separate PRs. Just before the v3.0.0 cut, merge `main` into `v3` once (merge commit; source conflicts resolved to `v3`, `main`'s v2.0.x CHANGELOG sections brought over) so the cut is a fast-forward.
+- **v3.next** (the release after v3.0.0) holds new features (lag/lead #182, sliding row frames #183, rule persistence #241).
 - Known v2.x data issue: same-transaction multi-valued facts (#371). Fix ships in v3.0.0. All v2.x known issues are listed in pinned issue #421 (`known-issue` label); `data-integrity`/`corruption`/`durability` issues stay open until the fix is in a published release (CONTRIBUTING.md).
 - Support policy and tiers: PHILOSOPHY.md §7 and §10. v2.x gets data-integrity and security fixes for 12 months after v3.0.0. Tier 1 = Rust + Python; other bindings are Tier 2.
 

@@ -148,6 +148,15 @@ Scope — format and storage integrity:
 - Net-assert on v8 keys before resolving facts, for O(live) point queries (#379)
 - `btree_page` fuzz target that reaches node decoding (#375)
 
+Scope — query and bindings:
+
+- Native `:limit N` / `:offset` for plain `:find` queries (#306, #310)
+- Query profiler (#185)
+- Set membership predicates (#316)
+- `PreparedQuery` over UniFFI (#181)
+- UDF registration over UniFFI (#180)
+- `OpenOptions` exposed over UniFFI, so embedders can suppress the close-time checkpoint (#322; done on `v3`)
+
 Scope — release-gate testing and documentation:
 
 - Golden-file compatibility corpus for every format version, frozen before v8 work goes further (#391)
@@ -168,14 +177,8 @@ Scope — release-gate testing and documentation:
 Additive features, kept out of v3.0.0 so the #371 fix is not held up by them:
 
 - Rule persistence — design first (#241)
-- Query profiler (#185)
-- Native `:limit N` / `:offset` for plain `:find` queries (#306, #310)
-- Set membership predicates (#316)
 - `lag`/`lead` window functions (#182)
 - Sliding row frames — `:rows N preceding` (#183; builds on #182)
-- `PreparedQuery` over UniFFI (#181)
-- UDF registration over UniFFI (#180)
-- `OpenOptions` exposed over UniFFI, so embedders can suppress the close-time checkpoint (#322)
 - Temporal graph-traversal research (#273; may result in documentation or a blog post rather than code)
 
 ---
@@ -187,7 +190,7 @@ Additive features, kept out of v3.0.0 so the #371 fix is not held up by them:
 ### Developer Tools
 
 - 🎯 Database inspector/debugger (separate repository: [minigraf-inspector](https://github.com/project-minigraf/minigraf-inspector))
-- 🎯 Query profiler (#185, v3.next)
+- 🎯 Query profiler (#185, v3.0.0)
 - 🎯 Time-travel visualizer (separate repository: [minigraf-visualizer](https://github.com/project-minigraf/minigraf-visualizer))
 
 ### Integration Examples