Repository navigation
release: v1.0.0-rc.87 - #1203
Merged
Merged
Conversation
The corpus-index trust window. Four PRs, all against the corpus ingest path the rc.84-86 honesty work exposed: - #1195 (merged just past the rc.86 tag): phase-B bulk bodies coalesce across files — the per-file round-trip ceiling of #1147 (#10^5 records/node-day on the ghsa-scale mirror class). A/B'd, no regression: rustsec 10.1s -> 9.7s, pysec 17.4s -> 16.9s, phase B at parity on both shapes; the structural win shows at scale, which the standing corpus rebuild re-measures. - #1197: `xerj corpus index` proves the store answers a search before printing "searchable" — the #1183 resume that certified 642 records over a store answering every _search with store_exception. An unsearchable build is retired by exact name, not switched in. - #1199: a retrying client request announces itself (#1183 item 1's client half) — the retry envelope was bounded (6 x 300s) but silent, which is exactly how it read as a deadlock. The server-side stall under memory pressure stays open in #1183 with the #1122 class. - #1200: JSON records with no prose gain a synthesized text passage, plus a plan-time warning for any dataset mapping no text-searchable field — the build-time half of #1158, whose query-time half shipped in rc.86. The issue closes with both halves shipped. ROADMAP rolled to the rc.87 cut: nine open at the cut (#1147 and #1158 closed inside the window), the rc.86 and earlier records stand as written. Release-notes gate: PASS locally. Files: engine/Cargo.toml (version stamp), CHANGELOG.md ([Unreleased] cut into [1.0.0-rc.87]; the #1147 entry written at this roll — the PR merged past the tag, so its entry lands here), ROADMAP.md.
This was referenced Oct 7, 2026
neoneye
pushed a commit
to agent-memory-atlas-archive/xerj-org--xerj
that referenced
this pull request
Oct 10, 2026
The rc.86 release commit (baada0a) carried the landing stamp sweep inline; the rc.87 roll (PR xerj-org#1203) stamped engine/Cargo.toml and Cargo.lock but not the landing pages, so the Landing constants guard fails on main: 91 V1.0.0-RC.86 stamps (plus the data-latest-tag fallback in landing/index.html) against the tree's 1.0.0-rc.87. Mechanical sweep only, no prose touched: V1.0.0-RC.86 -> V1.0.0-RC.87 across landing/, and the one lowercase v1.0.0-rc.86 data-latest-tag span. The llms.txt 'Current release' check was already green (it reads the engine version), which is why only this guard went red. Files: 55 landing pages, one line each (print headers + footers).
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.
The corpus-index trust window. Four PRs against the corpus ingest path the rc.84–86 honesty work exposed:
xerj corpus indexproves the store answers a search before it says "searchable"; an unsearchable build is retired by exact name, not switched in (corpus index: finalize-catalog deadlocks all 297 threads on a fresh build; post-kill resume prints "searchable" while the store 500s on a missing segment #1183 item 2).textpassage, plus the plan-time zero-text warning — the build-time half of xerj code: JSON corpora index to typed records with notextfield — passage search silently returns nothing #1158, closing the issue with its rc.86 query-time half.ROADMAP rolled to the rc.87 cut (nine open; the rc.86 and earlier records stand as written). Release-notes gate: PASS locally.
Tag will be
v1.0.0-rc.87from this merge ref,previous_tag_name=v1.0.0-rc.86pinned.