Repository navigation
docs(roadmap): roll forward to 2026-09-26 — the stale-evening corrections + rc.78 queue - #1036
Merged
Merged
Conversation
…, rc.78 queue The 2026-09-21 review of this file was stale within hours: #950 closed 19:33, #941 19:38, #1015 20:49 (all 2026-09-21), #874 2026-09-22, and the stage-1 gating trio #937/#938/#939 closed the same evening — every one recorded here as open or "under way". This pass re-checks every status claim against live tracker state and rolls the file forward: - Next release: the two "in flight" items (#1015, #950) are closed with fixes on main riding to rc.78 — the section now records what actually landed since the rc.77 tag (#1009, #1017, #1018, #1020, #1021, #1023, #1025, #1026, #1033, #1034) with PR links, including #874's budget met at ~3x margin (206 -> 64 kB per idle index) and discussion #1012's email-labelling measurement (1.000 templated tier / 0.625 at 0.902 confidence on the hard tier — wrong-and-confident). - Open defects: now #1031 and #1032 only; #1015/#950 removed (closed); trackers sentence corrected (#941, #874 closed — only #298 remains by design). - GA gate: "Close the CHANGELOG gap" marked closed 2026-09-26 (the rc.19-rc.70 backfill, PR #1035); the record-complete note replaces the gap warning under "Shipping today". - Zero-token: stage-1 gating trio recorded as fixed (#991, #995, #979) with the old measured costs kept as the before-state; the #940 hash-seed spread annotated as a pre-fix measurement; stage-2 object storage marked done (#965 wired in rc.77 — the old bullet contradicted this file's own "Shipping today" section); mail ingest "unreleased" corrected to "shipped in rc.75"; three stale "In flight:" labels on landed stage-1 items relabelled "History:". - Mail-ingest memory line: #948's runaway is fixed (#1002) — the line now carries the fixed numbers and points at #1032 for the residual. Review line updated to 2026-09-26 (machine-checked format), scoped honestly as a desk review. The milestones line is true again: rc.78 milestone created, all four open issues triaged (#1030/#1031/#1032 -> rc.78, #298 -> GA).
This was referenced Sep 26, 2026
neoneye
pushed a commit
to agent-memory-atlas-archive/xerj-org--xerj
that referenced
this pull request
Sep 30, 2026
The index-size stage-1 and corpus-packs release: 28 PRs over the rc.77 window (v1.0.0-rc.77..main @ 044e6c6). No tag pushed with this commit - the cut (tag + release PR + merge) is held for maintainer go, per directive 2026-09-29. CHANGELOG: [Unreleased] -> [1.0.0-rc.78] - 2026-09-29, fresh [Unreleased] above. The section was rich but 11 of the 28 window PRs were uncited - the release-notes gate (xerj-org#474) would have failed its coverage check, the exact drift rc.77 dodged by being cut directly on main. Added: PR citations for the four size-epic format PRs that cited only epic xerj-org#1038 (ZNV2 xerj-org#1040, ZPS2 xerj-org#1041, ZBS4 xerj-org#1042, ZFM5 xerj-org#1043); the three pack-publish hardening PRs folded into the corpus-pack entry's citation parenthetical (xerj-org#1049 draft-then-publish mechanics, xerj-org#1050 dated per-build-day tags, xerj-org#1051 the loose <pack>-SHA256SUMS.sig release asset the zip consumer flow needs); new Documentation entries for the rc.19-rc.70 backfill (xerj-org#1035), the ROADMAP 2026-09-26 review (xerj-org#1036), the stage-1 blog post (xerj-org#1044) and the corner-brand/blog-endings site work (xerj-org#1045). One honesty fix from the entry verification pass: ZFM5's "every other extension byte-identical" gains its 3 B .jsonl state-noise exception (measured 3,256 -> 3,259 B between the committed controls). ROADMAP: release-cut roll per the docs_capability_lists contract - Next release -> rc.79, review line -> 2026-09-29 against rc.78, riding-to list folded into the rc.78 cut record, open defects carried into rc.79 (xerj-org#1031, xerj-org#1032, live-verified open at the cut via the tracker API). Tracker xerj-org#298 closed as abandoned (2026-09-29): the review cadence is machine-enforced by docs_capability_lists, not by the issue; its link - and the closed xerj-org#941/xerj-org#874 links - are removed from the open-defects shortlist, where the release-notes gate's check 1a requires every issues/N link to be open. Version: engine/Cargo.toml 1.0.0-rc.77 -> 1.0.0-rc.78 (the [workspace.package] version, 17 crates inherit; Cargo.lock refreshed via cargo metadata - diff is exactly the 17 member version lines); 89 landing release stamps V1.0.0-RC.77 -> V1.0.0-RC.78 (88 footer/print stamps across 52 pages + the data-latest-tag literal at landing/index.html:178; the dated tokens stay per the rc.77 release precedent). Stamps and Cargo bump ship together so the landing-constants-guard allow-set {newest tag, tree version} holds on the release branch. Gates, run locally on this tree: release-notes-gate.sh PASS (freshness, shortlist state, 5 Fixed citations closed, 28/28 window PRs cited); landing-constants-guard all green; docs_capability_lists 15 passed / 0 failed (includes the two roadmap-freshness tests that pin this roll). Engine code untouched - ES-YAML conformance surface unchanged by this commit.
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
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.
Motivation
The pinned roadmap's last review (2026-09-21) was stale within hours:
#950 closed 19:33, #941 19:38, #1015 20:49 (all the same evening), #874 the
next morning, and the stage-1 gating trio #937/#938/#939 closed that evening
too — every one of them still recorded in ROADMAP.md as open, "in flight" or
"under way". This pass re-checks every status claim against live tracker
state and rolls the file forward. (Found by the 2026-09-26 post-merge audit.)
What changed
fixes on
mainriding to rc.78. The section now records what actuallylanded since the rc.77 tag (fix(api): POST /{index}/_cache/clear releases the index's rebuildable caches (#950) #1009, fix(#950): id-position maps from the __id projection; stream the stored reassembly #1017, fix(#1015): flush drains freeze; the publication bracket wraps only the publish #1018, bench(#874): idle-budget fixture + CI gate; delete the O(N) metrics gauge loop #1020, fix(#1019): _delete_by_query pages the whole match set, ids-only #1021, fix(#1022): _update_by_query pages the match set; exact sig-text/enrich counts #1023, perf(#1024): lazy request-cache seen-set — 206 to 64 kB/idx idle RSS #1025,
bench(systemone): measure local /_decide for discussion #1012 email labelling #1026, docs(llms): #1028 — status claims caught up with main (rerank/share/mbox on main; #948 closed; residual retention re-anchored to #1032) #1033, perf(#1024): request-cache seen-set allocates on first tracked search — idle 206 → 64 kB/idx #1034) with PR links — including Meta: idle cost must be near-zero on dev laptops — the reference-coding resource budget (#871 #872 #873) #874's budget met at ~3×
margin and discussion Optional Jev classification in `xerj autoindex` (emails first): would you use it? #1012's email-labelling measurement.
sentence corrected (Tracking: the zero-token direction, stage 1 — rerank stage, share links + reading room, mbox/Takeout ingest, autoindex resilience #941/Meta: idle cost must be near-zero on dev laptops — the reference-coding resource budget (#871 #872 #873) #874 closed; only 📍 XERJ public roadmap — where the project is going and how to follow it #298 remains by design).
PR docs(changelog): reconstruct the rc.19–rc.70 gap (GA gate item) #1035 — merge docs(changelog): reconstruct the rc.19–rc.70 gap (GA gate item) #1035 before this PR so the claim is true when this
lands); the record-complete note replaces the gap warning.
old costs kept as dated before-states; hybrid RRF orders tied fused scores by HashMap iteration: top-10 differs for 21 of 40 queries after a restart on unchanged data #940 spread annotated pre-fix; stage-2
object storage marked done (Wire the index segment path to the object-storage backend (bundle a segment into one object first) #965 wired rc.77 — the old bullet contradicted
the file's own Shipping today); mail ingest "unreleased" → "shipped in
rc.75"; three stale
*In flight:*labels on landed items →*History:*.milestones claim is true again (rc.78 milestone created;
corpus/index: portable one-file bundles — indexed data that works across machines #1030/autoindex: a source file that grows mid-run (append-only log) kills the run, is misclassified as a bulk/backend failure, and the retry advice points at the wrong fix #1031/engine: stored_value_cache / dv_cache / id_pos_cache remain unbounded until merge-retire — the residual heap-per-doc retention after #1002 #1032 triaged to it, 📍 XERJ public roadmap — where the project is going and how to follow it #298 → GA — done on GitHub already).
Verification
Every closure/fix claim above was verified against the live tracker
(
gh api issues/Nstate+closed_at) and PR merge records; numbers quoted onlyfrom PR bodies' own verified runs (#1002, #1026, #1025/#1034).