docs: close spec-traceability and dashboard-hygiene gaps (0.18.7) - #646
Merged
Conversation
012-query-constraints/Req 3 (Range and Prefix Constraints) still read [Future] with 0/0 scenarios even though #606/ADR-0034 (index range seeks) shipped — flip it to [MUST] with real Implementation/Tests links against src/codegen/select/range_scan.rs and tests/unit/range_scan_test.rs (6 scenarios: BETWEEN, LIKE/GLOB prefix, IN dedup, affinity-mismatch fallback, EXPLAIN QUERY PLAN reporting). tools/assurance.py's VERSION_MAP stopped at minor 14 (V5 phase 1, #353); extend it through minor 18 (V6 phases 1-3 / #354, V7 phase 2 / #421) so the crate's actual current version (0.18.7) resolves instead of reporting "no VERSION_MAP entry". make assurance now reports 86/86 requirements (100%) and 276/276 scenarios (100%) test-backed, with no dead links. spend: trivial (dashboard/spec hygiene, no code change) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
iheitlager
force-pushed
the
chore/assurance-dashboard-hygiene
branch
from
August 29, 2026 16:20
229a7f5 to
d7a0c82
Compare
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
Two small hygiene gaps flagged during a V7-polish status check:
.openspec/specs/012-query-constraints/spec.mdRequirement 3 (Range and Prefix Constraints) still read[Future]with 0/0 scenarios inmake assurance, even though perf: LIKE/GLOB prefix range, BETWEEN single-range, and IN-list index optimizations #606/ADR-0034 (index range seeks —SeekIndexGE/IdxCompareGT) shipped. Flipped to[MUST]with realImplementation:/Tests:links againstsrc/codegen/select/range_scan.rsandtests/unit/range_scan_test.rs— 6 scenarios covering BETWEEN, LIKE/GLOB prefix, IN dedup, the affinity-mismatch fallback, and EXPLAIN QUERY PLAN reporting.tools/assurance.py'sVERSION_MAPstopped at minor 14 (V5 phase 1, epic: V5 Slim — Core Transactions (0.14.0) #353), so the crate's actual current version (0.18.7) reported "no VERSION_MAP entry". Extended through minor 18 (V6 phases 1-3 → epic: V6 Slim — WAL & Basic CTEs (0.15.0 / 1.0) #354, V7 phase 2 → epic: V7 — Polish & Compatibility (0.17.0+) #421), matching CHANGELOG.md's actual per-minor phase history.No code changes — spec/tooling only.
Test plan
make assurancenow reports86/86 requirements (100%)and276/276 scenarios (100%)test-backed, zero dead links (was 85/86, 270/270 before).Version 0.18.7 = V7 phase 2 released (epic #421)now prints instead of the "no VERSION_MAP entry" warning.make lintclean..rsfiles touched — no test-suite regression risk.spend: trivial (dashboard/spec hygiene, no code change)
🤖 Analysis by Claude