From 65495247a74cbf81b0d55bffec756d1373c10375 Mon Sep 17 00:00:00 2001 From: Aditya Mukhopadhyay Date: Wed, 14 Oct 2026 10:48:31 +0530 Subject: [PATCH] docs: #310 closed as a duplicate of #306 The :limit/:offset work is tracked in #306 alone. Drop #310 from CLAUDE.md, ROADMAP.md and the streaming engine spec. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01U611mBGbkSqJeSwNz2xd7s --- CLAUDE.md | 2 +- ROADMAP.md | 2 +- .../superpowers/specs/2026-10-11-streaming-engine-design.md | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index c202195fc..6858540cd 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -214,7 +214,7 @@ 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. All v3 PRs target `v3`; `main` stays untouched. CI runs on PRs to `v3` the same as on PRs to `main`. 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. At the first v3 release, the current `main` is copied to `v2` and `v3` becomes the new `main`. -- **v3.1.0** holds new features (query profiler #185, `:limit` #306/#310, lag/lead #182, UniFFI additions). +- **v3.1.0** holds new features (query profiler #185, `:limit` #306, lag/lead #182, UniFFI additions). - 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 fixed in a v2.x patch stay open until that patch is published; issues fixed on the unreleased `v3` branch close on merge (closing keywords do not fire on `v3`, so close them with `gh issue close`) and stay listed in #421 (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. diff --git a/ROADMAP.md b/ROADMAP.md index 24ef71e3c..ddc6090ac 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -119,7 +119,7 @@ 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) +- Native `:limit N` / `:offset` for plain `:find` queries (#306) - Set membership predicates (#316) - `lag`/`lead` window functions (#182) - Sliding row frames — `:rows N preceding` (#183; builds on #182) diff --git a/docs/superpowers/specs/2026-10-11-streaming-engine-design.md b/docs/superpowers/specs/2026-10-11-streaming-engine-design.md index 6e27860c4..96d1d2420 100644 --- a/docs/superpowers/specs/2026-10-11-streaming-engine-design.md +++ b/docs/superpowers/specs/2026-10-11-streaming-engine-design.md @@ -4,7 +4,7 @@ **Sub-issues:** #543–#551 (§12) **Milestone:** v3.0.0, branch `v3`. The `.graph` file format stays v8 and the WAL format stays v2. **Folds in:** #518 (AVET reads, parked on branch `perf/518-avet-lookup`), #530 (ids until projection) -**Followed by:** #306/#310 (`:limit`/`:offset` syntax and the 10M-fact `:limit` acceptance test), #185 (profiler) +**Followed by:** #306 (`:limit`/`:offset` syntax and the 10M-fact `:limit` acceptance test), #185 (profiler) **Status:** design approved 2026-10-11, revised the same day (§11 lists the changes from the approved summary); not implemented ## 1. Terms @@ -362,7 +362,7 @@ Schema validation and the v8 multi-value fix (#371, #287) are unaffected. ## 10. Acceptance tests -From #473. The `:limit` test moves to #306/#310, since it needs the syntax. +From #473. The `:limit` test moves to #306, since it needs the syntax. - [ ] `count` over 10M facts holds memory independent of the number of facts. - [ ] Grouped `count` with 1M groups completes, holding memory proportional to the number of groups. With `query_memory_limit` below that, it fails with `QRY-012`. @@ -406,4 +406,4 @@ Sub-issues of #473, in order. Each is one or more PRs to `v3`, and none uses a c 8. **#550 Streaming transactions** (§8): chunked parser, large transactions, statement bases, the B+tree delete. 9. **#551 Removal and measurement**: delete the existing executor and the oracle, envelope at 100K/1M/10M, documentation. -After #473: `:limit`/`:offset` syntax with the 10M-fact acceptance test (#306/#310), then the profiler (#185). +After #473: `:limit`/`:offset` syntax with the 10M-fact acceptance test (#306), then the profiler (#185).