AI search engine and MCP server for bots and agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.
Rust agent-memoryai-agentsbm25claude-codeclicode-searchcursordatabaseelasticsearchfull-text-searchhybrid-searchjsonllocal-firstmcpmcp-servermodel-context-protocolragrustsearch-enginevector-search
Merge origin/main into release/rc99
Cursor Agentdaf380f171b8
diff --cc CHANGELOG.mdindex 0043a867b,22d0d5ad6..088ccdc9d--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -7,117 -7,135 +7,196 @@@ and this project adheres to [Semantic V## [Unreleased]- ## [1.0.0-rc.99] - 2026-10-23++## [1.0.0-rc.99] - 2026-10-24+- Window since v1.0.0-rc.98: 93 merged pull requests. x86_64 release binaries++Window since v1.0.0-rc.98: 115 merged pull requests. x86_64 release binaries+run on CPUs without AVX2. Cluster mode replicates index metadata, routes a+document write to the primary named at create, copies an acknowledged write+onto replicas placed at create, acknowledges that write once a quorum of- the copies has confirmed, and reloads the shard plan from an on-disk Raft- log after a restart; [#1170](https://github.com/xerj-org/xerj/issues/1170)- stays open. `ctutils` 0.4.5 closes RUSTSEC-2026-0385. Autoindex, corpus and- search fixes landed, including partial work on++the copies has confirmed, reloads the shard plan from an on-disk Raft log++after a restart, installs a compacted Raft snapshot on a lagging member,++copies the primary's live documents onto a replica that is behind, and runs++`_bulk`, `_update` and `_update_by_query` on the shard primary;++[#1170](https://github.com/xerj-org/xerj/issues/1170) stays open. `ctutils`++0.4.5 closes RUSTSEC-2026-0385. Autoindex, corpus and search fixes landed,++including partial work on+[#1122](https://github.com/xerj-org/xerj/issues/1122); that issue stays open.- MCP gained local definition lookup. A DeepSeek Harness profile bundle ships- in `dsh/`. Contributors in this window: Jarvis636431, Tong-bit-art,- redwolf2019, ArkNill, pallidev, samuelmbabhazi, elewashy, WYSTAF, kamwoh,- mgtf and mariomarcolongo.++MCP gained local definition lookup and ordered batch retrieval. A DeepSeek++Harness profile bundle ships in `dsh/`. Contributors in this window:++Jarvis636431, Tong-bit-art, redwolf2019, ArkNill, pallidev,++samuelmbabhazi, elewashy, WYSTAF, kamwoh, mgtf, mariomarcolongo and Jun516.++### Security++- **`ctutils` 0.4.5** (RUSTSEC-2026-0385, published 2026-10-23). `Choice`+ mask generation and 32-bit `u128` comparisons before 0.4.4 can branch on+ secret values. Nothing in the workspace names the crate. It is transitive:+ `digest` 0.11 depends on `ctutils ^0.4`, and that line is what `sha1`+ 0.11, `sha2` 0.11, `hmac` 0.13 and `md-5` use, reaching `xerj-autoindex`+ and `xerj-storage` through the AWS SDK checksum path and `pdf_oxide`.+ `cargo update -p ctutils` locked 0.4.5 (0.4.4 is the advisory floor).+ `cmov` stayed at 0.5.4. Lockfile only (PR+ [#2268](https://github.com/xerj-org/xerj/pull/2268)).+### Added- - Cluster replication, five slices of-- With `[cluster] enabled = true`, `POST /{index}/_update_by_query` runs on- every shard primary, whichever member accepted the request. Each primary- updates the documents in its own shard and copies those updates to the- in-sync replicas, with the same quorum as `PUT /{index}/_doc/{id}`.- `max_docs` is one budget for the index, spent across primaries in- node-id order, not once per shard. A primary that does not answer- refuses the request before any document is written. A copy that misses- quorum is HTTP 503 `replica_not_acknowledged`: the primaries that ran- have the update, and the response still reports `updated` and- `failures`. `?pipeline=` runs on the primary; a missing or unrunnable- pipeline there is HTTP 400 and writes nothing. Pipelines are not- replicated. `wait_for_completion=false` uses the same path.- `_delete_by_query` and native `/v1` ingest still write on the receiving- node. A write still needs the primary. `[cluster] enabled = false` does- not take this path (part of- [#1170](https://github.com/xerj-org/xerj/issues/1170)).--- With `[cluster] enabled = true`, `POST /_bulk`, `POST /{index}/_bulk`, and- `POST /{index}/_update/{id}` run on the shard primary, whichever member- accepted the request. A bulk body is split by primary. An action whose- primary is another member is forwarded there and is not indexed on the- receiver. The primary then copies the stored document (or the delete)- onto the in-sync replicas and acknowledges it with the same quorum as- `PUT /{index}/_doc/{id}`. `_bulk` covers index, create, update, and- delete. `_update` covers a partial document and a script; the script- runs on the primary, where the current source is. A missing `_id` on- index or create is chosen before the owner is selected, so the stored- id is the id that was routed. An update that does not change the source- is not copied again. A copy that misses quorum is- `503 replica_not_acknowledged` for that item: the primary has the write.- Native `/v1` ingest still writes on the receiving node.- `_update_by_query` is the entry above. A write still needs the primary.- `[cluster] enabled = false` does- not take this path (part of- [#1170](https://github.com/xerj-org/xerj/issues/1170)).--- `xerj corpus add --own` and `xerj corpus own <name>` (`--off` clears it)- mark a corpus as your own first-party code (`"own": true` in its- `corpus.json`). `xerj code` and MCP `xerj_code_search` still name an- unidentified licence (`UNKNOWN` or `NONE-FOUND`) on each hit and omit- the do-not-copy banner for that unidentified licence. A licence the- detector actually named still warns. A local path is not marked own- unless the flag is passed, and a `--from` manifest cannot set the- marker. `xerj corpus index` prints a per-file-class indexed vs- ignored-data summary at the end- ([#2339](https://github.com/xerj-org/xerj/issues/2339)).--- With `[cluster] enabled = true`, a replica that does not have the- primary's live documents copies them and then rejoins the in-sync set.- That covers a member that starts after the writes (the create entry- opens an empty replica store) and a replica removed from the in-sync- set because it missed an acknowledgement. A process that stops and- later opens the same data directory is filled the same way: documents- inserted, updated, or deleted while it was down are applied to its- replica store before the enlarged set is published. The primary sends- the live documents, drops ids the replica still has that the primary- no longer does, and publishes the enlarged in-sync set through the- Raft log. The primary holds that shard's replica lock across the copy,- so a write that arrives during the copy is replicated to the new set- when the lock is released. A later single-document index or delete is- copied to that replica with the others. A write still needs the- primary. Changing membership does not move copies.- `[cluster] enabled = false` does not do this (part of- [#1170](https://github.com/xerj-org/xerj/issues/1170)).--- With `[cluster] enabled = true`, a member compacts its Raft log once- 64 metadata entries have been applied since the previous snapshot.- The compacted prefix is stored in `{data_dir}/_raft/snapshot.meta` and- removed from `raft.log`. A peer whose log does not overlap that prefix- receives InstallSnapshot and applies those commands, which installs the- same index metadata an AppendEntries catch-up would have. The snapshot- is that command prefix, not a smaller folded image and not the- documents. A history that does not fit in 8 MiB stays in the log.- Restart replays the snapshot and then the entries after it. Copying- the documents themselves is the replica backfill entry above (part of- [#1170](https://github.com/xerj-org/xerj/issues/1170)).++- Cluster replication, nine slices of+ [#1170](https://github.com/xerj-org/xerj/issues/1170). The issue stays+ open. With `[cluster] enabled = false` every one of these paths is the+ previous local call.+ - Index create, delete, mapping and settings are proposed through the Raft+ log. The HTTP call succeeds only after this node has applied the+ committed entry. A follower forwards to the leader. No elected leader, a+ timeout, or leadership lost before commit is HTTP 503, and the index is+ not created locally. The accepting node applies index templates once and+ replicates the effective schema. Console system indices created before+ the handle is attached stay local. Document writes stay on the accepting+ node. #2257 left that log in memory. The on-disk log is the slice below+ (PR [#2257](https://github.com/xerj-org/xerj/pull/2257)).+ - The create entry names one primary per member (member ids sorted, shard+ `i` on the `i`th). `PUT` / `POST /{index}/_doc`, `PUT /{index}/_create/{id}`,+ `GET` and `DELETE /{index}/_doc/{id}` run on that primary. A search of+ one concrete index asks every owner and merges hits by per-shard score,+ then applies `from` / `size`. A forward that fails is 503 and is not+ also written locally (PR+ [#2271](https://github.com/xerj-org/xerj/pull/2271)).+ - `index.number_of_replicas` at create (nested, flat or dotted; absent+ means 0) places that many copies, capped at `members - 1`, in a hidden+ `.xerj_replica_{index}_{shard}` index so a search of the user index does+ not count the copy twice. This pull request waited for every placed+ replica before acknowledging the caller. The next slice acknowledges a+ quorum instead. GET, and a search whose primary does not answer, read a+ replica. There is no promotion: a write still needs the primary. A later+ `PUT /{index}/_settings` stores a new replica count and does not move+ copies (PR [#2287](https://github.com/xerj-org/xerj/pull/2287)).+ - With `[cluster] enabled = true`, a single-document index or delete is+ acknowledged when a quorum of the shard's copies has confirmed, not only+ when every placed replica has. Copies are the primary plus the replicas+ named by `index.number_of_replicas` at create. A quorum is+ `copies / 2 + 1`, and the primary already counts, so one replica out of- two is enough. The replica that did not confirm is removed from the- in-sync set through the Raft log and is not used for a later read.- Nothing replays the writes it missed, so it stays out.- `number_of_replicas` 0 or 1 is unchanged: there is no replica to wait- for, or that one replica must confirm. Fewer confirmations than the- quorum is still HTTP 503 `replica_not_acknowledged`: the primary has the- write, and retrying the index copies it to the replicas still in sync.- Single-node mode does not take this path (PR++ two is enough. The replica that did not confirm is removed from the++ in-sync set through the Raft log and is not used for a later read until++ the backfill slice below has copied the primary's live documents onto++ it. `number_of_replicas` 0 or 1 is unchanged: there is no replica to++ wait for, or that one replica must confirm. Fewer confirmations than++ the quorum is still HTTP 503 `replica_not_acknowledged`: the primary++ has the write, and retrying the index copies it to the replicas still++ in sync. Single-node mode does not take this path (PR+ [#2303](https://github.com/xerj-org/xerj/pull/2303)). #1170 stays open:+ there is still no `wait_for_active_shards` and no replica promotion.+ - With `[cluster] enabled = true`, the server opens an on-disk Raft log+ at `{data_dir}/_raft` and replays its committed prefix before it+ serves. A restart restores the shard plan and the in-sync set, so a+ later document write is routed to the primary again. A member that+ starts with an empty log copies the leader's log and applies it, which+ installs index metadata (and an empty replica store when this node is- a replica). It does not copy documents written before it joined. A- replica removed from the in-sync set is not filled in. The log is not- compacted; there is no InstallSnapshot. Term and vote are stored with- the log, so a restarted node does not grant a second vote in the same- term. `[cluster] enabled = false` does not open the log. This improves++ a replica). Documents written before it joined are copied by the++ backfill slice below. Term and vote are stored with the log, so a++ restarted node does not grant a second vote in the same term.++ `[cluster] enabled = false` does not open the log. Log compaction and++ InstallSnapshot are the next slice. This improves+ [#1170](https://github.com/xerj-org/xerj/issues/1170); the issue stays+ open (PR [#2313](https://github.com/xerj-org/xerj/pull/2313)).- - What #1170 still does not do: `wait_for_active_shards`; relocating or- backfilling when the replica count changes after create; `_bulk`,- `_update`, update-by-query and native `/v1` ingest (they do not route or- replicate); merging aggregations, suggest, collapse, rescore, profile,- `search_after` or scroll across owners; InstallSnapshot and copying- documents onto a member that joined late; replica promotion; replaying a- dropped replica back into the in-sync set; node-lifecycle APIs.++ - A member compacts its Raft log once 64 metadata entries have been++ applied since the previous snapshot. The compacted prefix is stored in++ `{data_dir}/_raft/snapshot.meta` and removed from `raft.log`. A peer++ whose log does not overlap that prefix receives InstallSnapshot and++ applies those commands, which installs the same index metadata an++ AppendEntries catch-up would have. The snapshot is that command prefix,++ not a smaller folded image and not the documents. A history that does++ not fit in 8 MiB stays in the log. Restart replays the snapshot and++ then the entries after it. Copying the documents themselves is the++ backfill slice below. Part of++ [#1170](https://github.com/xerj-org/xerj/issues/1170); the issue stays++ open (PR [#2320](https://github.com/xerj-org/xerj/pull/2320)).++ - A replica that does not have the primary's live documents copies them++ and then rejoins the in-sync set. That covers a member that starts++ after the writes (the create entry opens an empty replica store), a++ replica removed from the in-sync set because it missed an++ acknowledgement, and a process that stops and later opens the same++ data directory: documents inserted, updated, or deleted while it was++ down are applied to its replica store before the enlarged set is++ published. The primary sends the live documents, drops ids the replica++ still has that the primary no longer does, and publishes the enlarged++ in-sync set through the Raft log. The primary holds that shard's++ replica lock across the copy, so a write that arrives during the copy++ is replicated to the new set when the lock is released. A later++ single-document index or delete is copied to that replica with the++ others. A write still needs the primary. Changing membership does not++ move copies. `[cluster] enabled = false` does not do this. Part of++ [#1170](https://github.com/xerj-org/xerj/issues/1170); the issue stays++ open (PR [#2328](https://github.com/xerj-org/xerj/pull/2328)). The++ outage case (insert, update and delete, then reopen the same data++ directory) is covered by the test-only pull request++ [#2341](https://github.com/xerj-org/xerj/pull/2341).++ - `POST /_bulk`, `POST /{index}/_bulk` and `POST /{index}/_update/{id}`++ run on the shard primary, whichever member accepted the request. A++ bulk body is split by primary. An action whose primary is another++ member is forwarded there and is not indexed on the receiver. The++ primary then copies the stored document (or the delete) onto the++ in-sync replicas and acknowledges it with the same quorum as++ `PUT /{index}/_doc/{id}`. `_bulk` covers index, create, update and++ delete. `_update` covers a partial document and a script; the script++ runs on the primary, where the current source is. A missing `_id` on++ index or create is chosen before the owner is selected, so the stored++ id is the id that was routed. An update that does not change the++ source is not copied again. A copy that misses quorum is++ `503 replica_not_acknowledged` for that item: the primary has the++ write. Native `/v1` ingest still writes on the receiving node.++ `_update_by_query` is the next slice. A write still needs the primary.++ `[cluster] enabled = false` does not take this path. Part of++ [#1170](https://github.com/xerj-org/xerj/issues/1170); the issue stays++ open (PR [#2344](https://github.com/xerj-org/xerj/pull/2344)).++ - `POST /{index}/_update_by_query` runs on every shard primary, whichever++ member accepted the request. Each primary updates the documents in its++ own shard and copies those updates to the in-sync replicas, with the++ same quorum as `PUT /{index}/_doc/{id}`. `max_docs` is one budget for++ the index, spent across primaries in node-id order, not once per shard.++ A primary that does not answer refuses the request before any document++ is written. A copy that misses quorum is HTTP 503++ `replica_not_acknowledged`: the primaries that ran have the update, and++ the response still reports `updated` and `failures`. `?pipeline=` runs++ on the primary; a missing or unrunnable pipeline there is HTTP 400 and++ writes nothing. Pipelines are not replicated. `wait_for_completion=false`++ uses the same path. `_delete_by_query` and native `/v1` ingest still++ write on the receiving node. A write still needs the primary.++ `[cluster] enabled = false` does not take this path. Part of++ [#1170](https://github.com/xerj-org/xerj/issues/1170); the issue stays++ open (PR [#2347](https://github.com/xerj-org/xerj/pull/2347)).++ - What #1170 still does not do: `wait_for_active_shards`; replica++ promotion (a write still needs the primary); native `/v1` ingest and++ `_delete_by_query` (they stay on the receiving node); replicating++ pipelines; moving copies when membership changes; merging aggregations,++ suggest, collapse, rescore, profile, `search_after` or scroll across++ owners; node-lifecycle APIs. The snapshot is the command prefix, not++ the documents, and a history that does not fit in 8 MiB stays in the++ log.++- A DeepSeek Harness profile bundle in `dsh/` (`xerj-dsh`, Apache-2.0,+ version `1.0.0-rc.99`) inserts the README's `mcp-xerj` stdio row via+ `@deepseek-ai/dsh-mcp-client` at 0.2.1-rc.3. The row is still untested on+ DSH. The English, Korean and Simplified Chinese READMEs link the bundle.+ `landing/brandbook/xerj-mark-400.png` is a 400×400 PNG of the letter mark+ for directory submissions (PR+ [#2298](https://github.com/xerj-org/xerj/pull/2298)).+ - `xerj batch-search --input <file|->` and MCP `xerj_batch_search` retrieve+ up to 50 IDs or questions in input order through one `_msearch` call.+ Each item returns cited evidence, an explicit empty-result abstention, or+ an independent error. Exact IDs require an indexed keyword field. Optional+ whole-response token budgets preserve outcomes and at least one citation+ per matched item, or refuse explicitly. This is retrieval, not generated- answers or calibrated confidence (#1801, partial implementation).--- With `[cluster] enabled = true`, a single-document index or delete is- acknowledged when a quorum of the shard's copies has confirmed, not only- when every placed replica has. Copies are the primary plus the replicas- named by `index.number_of_replicas` at create. A quorum is- `copies / 2 + 1`, and the primary already counts, so one replica out of- two is enough. The replica that did not confirm is removed from the- in-sync set through the Raft log and is not used for a later read until- the backfill entry above has copied the primary's live documents onto- it. `number_of_replicas` 0 or 1 is unchanged: there is no replica to- wait for, or that one replica must confirm. Fewer confirmations than- the quorum is still HTTP 503- `replica_not_acknowledged` — the primary has the write, and retrying the- index copies it to the replicas still in sync. There is still no- `wait_for_active_shards` and no replica promotion. A restarted member- reloads metadata from the on-disk Raft log. A replica that missed the- write is filled by the backfill entry above (part of- [#1170](https://github.com/xerj-org/xerj/issues/1170)). Single-node mode- does not take this path.--- With `[cluster] enabled = true`, the server opens an on-disk Raft log- at `{data_dir}/_raft` and replays its committed prefix before it- serves. A restart restores the shard plan and the in-sync set, so a- later document write is routed to the primary again. A member that- starts with an empty log copies the leader's log and applies it, which- installs index metadata (and an empty replica store when this node is- a replica). Documents written before it joined are copied by the- backfill entry above. Term and vote are- stored with the log, so a restarted node does not grant a second vote in the same- term. `[cluster] enabled = false` does not open the log (part of- [#1170](https://github.com/xerj-org/xerj/issues/1170)).--- A DeepSeek Harness profile bundle in `dsh/` (`xerj-dsh`, Apache-2.0)- inserts the README's `mcp-xerj` stdio row via- `@deepseek-ai/dsh-mcp-client`. The row is still untested on DSH.- `landing/brandbook/xerj-mark-400.png` is a 400×400 PNG of the letter- mark for directory submissions.--- MCP `xerj_def` exposes local definition lookup, completing #2080 after the- `xerj_search` prefix support. It shares `xerj def --json` query construction,- mapping guards, ranking and location deduplication; accepts `symbol`,- `prefix`/`index`, `kind`, `lang`, `k` (1–50) and `max_tokens`. No match is a- successful empty hit list; invalid arguments are rejected before HTTP.++ answers or calibrated confidence. Partial implementation of++ [#1801](https://github.com/xerj-org/xerj/issues/1801) (PR++ [#2333](https://github.com/xerj-org/xerj/pull/2333), Jarvis636431).++- MCP `xerj_def` exposes local definition lookup, completing+ [#2080](https://github.com/xerj-org/xerj/issues/2080) (PR+ [#2166](https://github.com/xerj-org/xerj/pull/2166), Jarvis636431). It+ shares `xerj def --json` query construction, mapping guards, ranking and+ location deduplication; accepts `symbol`, `prefix`/`index`, `kind`,+ `lang`, `k` (1–50) and `max_tokens`. No match is a successful empty hit+ list; invalid arguments are rejected before HTTP.- MCP `xerj_search` accepts `prefix` as an alternative to `index`, matching`xerj search --prefix`: `project` searches `project-*`. Conflicting scope@@@ -128,28 -144,144 +207,191 @@@### Fixed+ - `xerj autoindex` no longer junks every PDF on an OS that rejects+ `setrlimit(RLIMIT_AS)` (macOS 27 returns `EINVAL`; a hard limit below- 1536 MiB returns `EPERM`). The address-space cap is crash isolation: the- refusal is logged once and the worker still starts. Linux still applies- the 1536 MiB cap. The same refusal is ignored for the isolated `.xls`- reader. If every PDF fails because the worker could not start, the run- finishes `ok=false exit=1 reason=pdf-worker-unavailable` instead of- looking like completed-with-junk- ([#2336](https://github.com/xerj-org/xerj/issues/2336)).--- `xerj autoindex` indexes `.sql` schema, migration, and routine files as- code. `CREATE TABLE` / `VIEW` / `FUNCTION` / `PROCEDURE` / `INDEX` /- `TRIGGER` / `TYPE` / `SCHEMA` / `SEQUENCE` become symbols, and the source- stays searchable. A comment, a quoted literal, a dollar-quoted body,- or an `INSERT`/`COPY` nested inside another statement is not a dump.- Those files used to be sniffed as an- empty SQL dump and skipped (`no records extracted`), which dropped- hand-written DDL such as a rule-engine script. A file with a top-level- `INSERT … VALUES` is still a row dump. A data-only `COPY … FROM stdin`- dump, which the row parser does not read, is skipped with that reason;- when the same file also contains schema statements, those statements are- indexed as code (#2337).--- A full process memtable budget now flushes instead of leaving `xerj autoindex`- on HTTP 429 until it gives up. The rejection requests a drain (largest- memtable first) rather than waiting for the next memory sample, and a- search issued while that breaker is engaged publishes those memtables- before it scans them. `xerj search` / `xerj def` saying `no indices named- …` names the prefixes on the node in that same line, including a prefix- recorded only on a catalog dataset document- ([#2321](https://github.com/xerj-org/xerj/issues/2321)).++ 1536 MiB returns `EPERM`)++ ([#2336](https://github.com/xerj-org/xerj/issues/2336), PR++ [#2338](https://github.com/xerj-org/xerj/pull/2338)). The address-space++ cap is crash isolation: the refusal is logged once and the worker still++ starts. Linux still applies the 1536 MiB cap. The same refusal is ignored++ for the isolated `.xls` reader. If every PDF fails because the worker++ could not start, the run finishes `ok=false exit=1++ reason=pdf-worker-unavailable` instead of looking like completed-with-junk.++++- `xerj autoindex` indexes `.sql` schema, migration and routine files as++ code++ ([#2337](https://github.com/xerj-org/xerj/issues/2337), PR++ [#2342](https://github.com/xerj-org/xerj/pull/2342)). `CREATE TABLE` /++ `VIEW` / `FUNCTION` / `PROCEDURE` / `INDEX` / `TRIGGER` / `TYPE` /++ `SCHEMA` / `SEQUENCE` become symbols, and the source stays searchable. A++ comment, a quoted literal, a dollar-quoted body, or an `INSERT` / `COPY`++ nested inside another statement is not a dump. Those files used to be++ sniffed as an empty SQL dump and skipped (`no records extracted`), which++ dropped hand-written DDL. A file with a top-level `INSERT … VALUES` is++ still a row dump. A data-only `COPY … FROM stdin` dump, which the row++ parser does not read, is skipped with that reason; when the same file++ also contains schema statements, those statements are indexed as code.++++- A full process memtable budget now flushes instead of leaving++ `xerj autoindex` on HTTP 429 until it gives up++ ([#2321](https://github.com/xerj-org/xerj/issues/2321), PR++ [#2325](https://github.com/xerj-org/xerj/pull/2325)). The rejection++ requests a drain (largest memtable first) rather than waiting for the++ next memory sample, and a search issued while that breaker is engaged++ publishes those memtables before it scans them. `xerj search` /++ `xerj def` saying `no indices named …` names the prefixes on the node in++ that same line, including a prefix recorded only on a catalog dataset++ document.++ - The default process memory cap on a host under 16 GiB is half of that- RAM, and segment merges follow it (#1122). An 8 GiB machine used to- take the 8 GiB step, so the budget was the whole machine; a merge- storm on Windows 10 stayed up only after- `XERJ_MAX_PROCESS_MEMORY_MB=4096`. That host now gets a 4 GiB cap.- A merge batch on a budget that cannot hold the historical 512 MiB- input (8× working set plus the 2 GiB memtable floor) is sized to- `budget / 64` (64 MiB at 4 GiB) and concurrent merges share a quarter- of the budget. A batch that would still cross the RSS watermark waits- for the next check; one batch still runs, because a merge is what- retires per-segment caches. Hosts at 16 GiB and above keep the 8 / 16 /- 32 GiB steps, the 512 MiB batch, and the configured merge parallelism.- A single JSON document over 50 MiB is still refused at the 8 MiB- ceiling, before it is parsed, and the rest of the bulk is indexed.++ RAM, and segment merges follow it. This improves++ [#1122](https://github.com/xerj-org/xerj/issues/1122); the issue stays++ open (PR [#2340](https://github.com/xerj-org/xerj/pull/2340)). An 8 GiB++ machine used to take the 8 GiB step, so the budget was the whole machine;++ a merge storm on Windows 10 stayed up only after++ `XERJ_MAX_PROCESS_MEMORY_MB=4096`. That host now gets a 4 GiB cap. A++ merge batch on a budget that cannot hold the historical 512 MiB input++ (8× working set plus the 2 GiB memtable floor) is sized to `budget / 64`++ (64 MiB at 4 GiB) and concurrent merges share a quarter of the budget. A++ batch that would still cross the RSS watermark waits for the next check;++ one batch still runs, because a merge is what retires per-segment caches.++ Hosts at 16 GiB and above keep the 8 / 16 / 32 GiB steps, the 512 MiB++ batch, and the configured merge parallelism. A single JSON document over++ 50 MiB is still refused at the 8 MiB ceiling, before it is parsed, and++ the rest of the bulk is indexed. The memory-ceiling class and the WSL2++ VM death are not addressed.++ - A multi-term question no longer ranks a one-word symbol definition- (`type Token`) above a hit that covers more of the question. `xerj search`,- `xerj def`, `xerj code`, and the plain-string `xerj_search` tool add a++ (`type Token`) above a hit that covers more of the question++ ([#2327](https://github.com/xerj-org/xerj/issues/2327), PR++ [#2329](https://github.com/xerj-org/xerj/pull/2329)). `xerj search`,++ `xerj def`, `xerj code` and the plain-string `xerj_search` tool add a+ coverage score when the question has three or more content tokens, and+ drop a one-term `name`+`kind` hit behind those results. A one-token+ lookup (`xerj def Token`) is unchanged. A nested test callback larger+ than a passage is no longer returned whole: the line-snapped window is+ kept, with its line. An archived path (`archive/`, `archived/`, or- `keep_archived`) is marked on the `xerj code` header and on `xerj search`- (#2327).++ `keep_archived`) is marked on the `xerj code` header and on `xerj search`.++ - Graph-mode `xerj autoindex` re-indexes a folder after files are added or- deleted. An added file that fits a frozen dataset is indexed on the rerun;- a file that needs a new dataset stays unindexed until `--fresh`. Documents,- catalog rows, and graph edges for a file that left the folder are removed,- and the run names that file, including when `--fresh` rebuilds the plan.- `xerj autoindex remove` deletes that folder's resume journal (and- `sync-snapshots`), and an explicit- `--state-dir` on `remove` deletes the journal there too. A file whose size- changes while a run is reading it is skipped with a warning instead of- aborting the run, on the graph path and on `--no-graph` snapshot sealing.- The catalog canonical/alias count refreshes and recounts before it aborts- a generation. A rerun that removes documents for files that left the folder- finishes exit 3 (`reason=files-removed`); the next unchanged rerun is exit 0- ([#2314](https://github.com/xerj-org/xerj/issues/2314)).++ deleted++ ([#2314](https://github.com/xerj-org/xerj/issues/2314), PR++ [#2317](https://github.com/xerj-org/xerj/pull/2317)). An added file that++ fits a frozen dataset is indexed on the rerun; a file that needs a new++ dataset stays unindexed until `--fresh`. Documents, catalog rows and++ graph edges for a file that left the folder are removed, and the run++ names that file, including when `--fresh` rebuilds the plan.++ `xerj autoindex remove` deletes that folder's resume journal and++ `sync-snapshots`, and an explicit `--state-dir` on `remove` deletes the++ journal there too. A file whose size changes while a run is reading it++ is skipped with a warning instead of aborting the run, on the graph path++ and on `--no-graph` snapshot sealing. The catalog canonical/alias count++ refreshes and recounts before it aborts a generation. A rerun that++ removes documents for files that left the folder finishes exit 3++ (`reason=files-removed`); the next unchanged rerun is exit 0.++ - Scoped autoindex threads and `POST /{index}/_update/{id}` no longer abort- the process when a thread stack or a large body cannot be allocated- (#1122). Indexing workers, sync replay, object-watch fetches, and mailbox- parsers start with `pthread_create` and do not map an alternate signal- stack. A spawn the OS refuses is an error: the job does not run, workers- that already started keep going, and the caller runs the work on the- calling thread or records the failure. An update body over two 8 MiB- documents plus 256 KiB of envelope is refused before `serde_json`, and- the existing document is left as it was.--- An idle node whose resident set sits flat at or above the memory watermark- no longer drains every 2 seconds for the rest of the process. The breaker- releases once RSS has not fallen by more than 4 MiB for 2 seconds, and does- not re-arm inside that band (page-sized `ri_phys_footprint` noise is not a++ the process when a thread stack or a large body cannot be allocated.++ This improves [#1122](https://github.com/xerj-org/xerj/issues/1122); the++ issue stays open (PR [#2322](https://github.com/xerj-org/xerj/pull/2322)).++ Indexing workers, sync replay, object-watch fetches and mailbox parsers++ start with `pthread_create` and do not map an alternate signal stack. A++ spawn the OS refuses is an error: the job does not run, workers that++ already started keep going, and the caller runs the work on the calling++ thread or records the failure. An update body over two 8 MiB documents++ plus 256 KiB of envelope is refused before `serde_json`, and the existing++ document is left as it was. The memory-ceiling class and the WSL2 VM++ death are not addressed.++++- An idle node whose resident set sits flat at or above the memory++ watermark no longer drains every 2 seconds for the rest of the process++ ([#1981](https://github.com/xerj-org/xerj/issues/1981), PR++ [#2232](https://github.com/xerj-org/xerj/pull/2232)). The breaker releases++ once RSS has not fallen by more than 4 MiB for 2 seconds, and does not++ re-arm inside that band (page-sized `ri_phys_footprint` noise is not a+ new working set); a climb past it engages again. While the breaker stays- engaged, drain requests double their spacing up to 15 minutes when a drain- does not lower RSS by more than 4 MiB. `corpus index` / `autoindex` report- `eta_quality=stalled` when a phase with a known total completes nothing- (including 0/N), and when a phase with no total has been silent for 10- minutes (#1981).++ engaged, drain requests double their spacing up to 15 minutes when a++ drain does not lower RSS by more than 4 MiB. `corpus index` / `autoindex`++ report `eta_quality=stalled` when a phase with a known total completes++ nothing (including 0/N), and when a phase with no total has been silent++ for 10 minutes.++ - Semantic `xerj autoindex` against `--embed-mode proxy` resumes after a+ mid-run failure and does not re-embed documents already indexed, when the- backend, configured model, endpoint, and confirmed vector width are- unchanged. The proxy digest is still the model and endpoint (#533); the- width is learned with one probe (and remembered under the data directory)- and compared on resume, so a successful probe does not change the hash an- existing index was recorded under. A proxy whose endpoint has not confirmed- a width stays non-resumable, and the refusal says to make the endpoint- reachable and rerun — already-indexed documents are kept — or to rebuild- with a new `--state-dir` and `--prefix` only to discard the corpus. A- provider that swaps weights without changing the name, endpoint, or width- is still not detectable- ([#2306](https://github.com/xerj-org/xerj/issues/2306)).--- An existing index's persisted `index.default_pipeline` runs again after a- clean restart. `GET /_settings` still reported the binding, and the- pipeline definition was still there, but an ordinary document write no- longer copied the field: the in-memory binding was filled on create and- on settings update, and opening the index from disk did not rebuild it.- Boot, a failed-index retry, and snapshot restore now copy `settings.json`- back into that map. Explicit `?pipeline=` was already unaffected- ([#2294](https://github.com/xerj-org/xerj/issues/2294)).++ backend, configured model, endpoint and confirmed vector width are++ unchanged++ ([#2306](https://github.com/xerj-org/xerj/issues/2306), PR++ [#2307](https://github.com/xerj-org/xerj/pull/2307)). The proxy digest is++ still the model and endpoint (#533); the width is learned with one probe++ (and remembered under the data directory) and compared on resume, so a++ successful probe does not change the hash an existing index was recorded++ under. A proxy whose endpoint has not confirmed a width stays++ non-resumable, and the refusal says to make the endpoint reachable and++ rerun — already-indexed documents are kept — or to rebuild with a new++ `--state-dir` and `--prefix` only to discard the corpus. A provider that++ swaps weights without changing the name, endpoint or width is still not++ detectable.++ - The node no longer aborts when a helper thread or a merge buffer cannot- be allocated (#1122). An in-process shard call starts its 8 MiB thread- with `pthread_create` and, if the OS refuses, returns- `could not start the shard call` without running the handler.- `PUT /{index}/_doc/{id}` and `PUT /{index}/_create/{id}` refuse a body- over the 8 MiB document ceiling before parsing it, the same way- `POST /{index}/_doc` already did. A merge that cannot reserve its output- buffer, document map, or the next survivor keeps the input segments and- stays up. PDF and `.xls` output readers, the autoindex progress ticker,- and the finalize-verify search use the same fallible spawn: a refusal- fails that file, skips the ticker, or runs the search on the calling- thread.--- `xerj autoindex` no longer aborts the node on one large JSON file (#1122).- A bulk whose analysis would cross the memory watermark is rejected with- HTTP 429 before the documents are parsed, so several in-flight bulks cannot- allocate their token strings together. Uncompressed JSON larger than 64 MiB- is read one value at a time; a value over the fixed 8 MiB document ceiling++ be allocated. This improves++ [#1122](https://github.com/xerj-org/xerj/issues/1122); the issue stays++ open (PR [#2315](https://github.com/xerj-org/xerj/pull/2315)). An++ in-process shard call starts its 8 MiB thread with `pthread_create` and,++ if the OS refuses, returns `could not start the shard call` without++ running the handler. `PUT /{index}/_doc/{id}` and++ `PUT /{index}/_create/{id}` refuse a body over the 8 MiB document ceiling++ before parsing it, the same way `POST /{index}/_doc` already did. A merge++ that cannot reserve its output buffer, document map, or the next survivor++ keeps the input segments and stays up. PDF and `.xls` output readers, the++ autoindex progress ticker, and the finalize-verify search use the same++ fallible spawn: a refusal fails that file, skips the ticker, or runs the++ search on the calling thread. The memory-ceiling class and the WSL2 VM++ death are not addressed.++++- `POST /_aliases` stores and enforces the alias metadata it is given:++ `filter`, routing, `is_write_index` and `is_hidden` (PR++ [#2319](https://github.com/xerj-org/xerj/pull/2319), Tong-bit-art). Those++ fields were dropped by the action parser, so a filtered alias created++ through the standard API exposed every document while the same alias++ created with `PUT /{index}/_alias/{name}` worked. `_cat/aliases` printed++ `-` for the filter; it now renders `*` for a filtered alias. Removing an++ alias, or re-adding it without a filter, clears the stored metadata, so++ a stale filter cannot outlive its definition.++++- `xerj corpus add --own` and `xerj corpus own <name>` (`--off` clears it)++ mark a corpus as your own first-party code (`"own": true` in its++ `corpus.json`)++ ([#2339](https://github.com/xerj-org/xerj/issues/2339), PR++ [#2343](https://github.com/xerj-org/xerj/pull/2343)). `xerj code` and MCP++ `xerj_code_search` still name an unidentified licence (`UNKNOWN` or++ `NONE-FOUND`) on each hit and omit the do-not-copy banner for that++ unidentified licence. A licence the detector actually named still warns.++ A local path is not marked own unless the flag is passed, and a `--from`++ manifest cannot set the marker. `xerj corpus index` prints a per-file-class++ indexed vs ignored-data summary at the end.+++- An existing index's persisted `index.default_pipeline` runs again after a+ clean restart+ ([#2294](https://github.com/xerj-org/xerj/issues/2294), PR+ [#2296](https://github.com/xerj-org/xerj/pull/2296)). `GET /_settings` still+ reported the binding, and the pipeline definition was still there, but an+ ordinary document write no longer copied the field: the in-memory binding+ was filled on create and on settings update, and opening the index from+ disk did not rebuild it. Boot, a failed-index retry, and snapshot restore+ now copy `settings.json` back into that map. Explicit `?pipeline=` was+ already unaffected.++- A bulk reserves memory for its tokens before the documents are parsed, and+ uncompressed JSON larger than 64 MiB is streamed one value at a time. This+ improves [#1122](https://github.com/xerj-org/xerj/issues/1122); the issue+ stays open (PR [#2302](https://github.com/xerj-org/xerj/pull/2302)). A bulk+ whose analysis would cross the memory watermark is rejected with HTTP 429+ before the documents are parsed, so several in-flight bulks cannot allocate+ their token strings together. A value over the fixed 8 MiB document ceilingis skipped with a note that names the file, its size, and that`--max-file-mb` and `limits.max_process_memory_mb` do not raise that- ceiling. A file over the scan cap names its size and `--max-file-mb`.+ ceiling. A file over the scan cap names its size and `--max-file-mb`. The+ memory-ceiling class and the WSL2 VM death are not addressed.- `POST /{index}/_refresh` makes recent writes searchable without waiting fora background segment merge to finish, and a multi-index or wildcard refresh@@@ -441,161 -473,7 +683,182 @@@frozen its memtable running. The refresh response names the stuck indexunder `_shards.failures` and continues with the other indices. Autoindexreports that failure instead of treating the refresh as success- ([#1635](https://github.com/xerj-org/xerj/issues/1635)).+ ([#1635](https://github.com/xerj-org/xerj/issues/1635), PR+ [#2129](https://github.com/xerj-org/xerj/pull/2129)). Flush deadlines are+ measured on the wall clock, not a tokio clock that a test can pause (PR+ [#2167](https://github.com/xerj-org/xerj/pull/2167), same issue).++- `_cat/indices` and `_cat/shards` use the bare content count, so+ `docs.count` agrees with `_count` and no longer includes file-card anchors+ (PR [#2141](https://github.com/xerj-org/xerj/pull/2141), Tong-bit-art).+ `docs.deleted` on `_cat` and the stats surfaces is the real deleted count+ (PR [#2242](https://github.com/xerj-org/xerj/pull/2242), Tong-bit-art).+ Both close [#2140](https://github.com/xerj-org/xerj/issues/2140).++- `xerj index --file <dir>` is refused before any index state is written,+ instead of dying in `mmap` with `Invalid argument` after creating an empty+ index ([#1818](https://github.com/xerj-org/xerj/issues/1818), PR+ [#2172](https://github.com/xerj-org/xerj/pull/2172), elewashy).++- Autoindex and corpus, the rest of this window:+ - A dead node is reported in full, and `_bulk` retries stop+ ([#2177](https://github.com/xerj-org/xerj/issues/2177), PR+ [#2192](https://github.com/xerj-org/xerj/pull/2192)).+ - A watched file can grow a field without failing the pass+ ([#2176](https://github.com/xerj-org/xerj/issues/2176), PR+ [#2193](https://github.com/xerj-org/xerj/pull/2193)).+ - Replacing a file drops the previous symbol generation+ ([#2139](https://github.com/xerj-org/xerj/issues/2139), PR+ [#2197](https://github.com/xerj-org/xerj/pull/2197)).+ - `xerj autoindex --watch` drops events on ignored files before they start+ a pass ([#2180](https://github.com/xerj-org/xerj/issues/2180), PR+ [#2198](https://github.com/xerj-org/xerj/pull/2198), samuelmbabhazi).+ - A changed file in a field-capped dataset is kept+ ([#1815](https://github.com/xerj-org/xerj/issues/1815), PR+ [#2215](https://github.com/xerj-org/xerj/pull/2215)).+ - `--lang` accepts a file extension and stores the language name+ ([#2205](https://github.com/xerj-org/xerj/issues/2205), PR+ [#2219](https://github.com/xerj-org/xerj/pull/2219)).+ - A dataless macOS placeholder is skipped instead of blocking the walk+ ([#2058](https://github.com/xerj-org/xerj/issues/2058), PR+ [#2223](https://github.com/xerj-org/xerj/pull/2223)).+ - A graph-path run whose catalog rows are not visible fails+ ([#1977](https://github.com/xerj-org/xerj/issues/1977), PR+ [#2224](https://github.com/xerj-org/xerj/pull/2224)).+ - `finalize-verify` stops when its target index is deleted+ ([#2222](https://github.com/xerj-org/xerj/issues/2222), PR+ [#2225](https://github.com/xerj-org/xerj/pull/2225)).+ - A resumed catalog read-back stays on the changed set. Same-generation+ resume confirms the generation with one `size: 0` count instead of+ paging every catalog document+ ([#1267](https://github.com/xerj-org/xerj/issues/1267), PR+ [#2231](https://github.com/xerj-org/xerj/pull/2231)).+ - `finalize-verify` can capture between catalog writes+ ([#1761](https://github.com/xerj-org/xerj/issues/1761), PR+ [#2237](https://github.com/xerj-org/xerj/pull/2237)).+ - Catalog phrase text is not indexed as a code symbol, and a phone-format+ syslog line parses (PR+ [#2247](https://github.com/xerj-org/xerj/pull/2247)).+ - An unreadable corpus source fails the build instead of pruning every+ stored envelope for that slug. Empty ids, and a torn final record whose+ checksums were recomputed, are refused+ ([#1110](https://github.com/xerj-org/xerj/issues/1110), PR+ [#2258](https://github.com/xerj-org/xerj/pull/2258)).++- `xerj code` and Corpus Hub, the rest of this window:+ - Lower-case `license.txt` and `License.md` are detected+ ([#2201](https://github.com/xerj-org/xerj/issues/2201), PR+ [#2202](https://github.com/xerj-org/xerj/pull/2202)).+ - Python passages cite a real start line, from symbols or the checkout+ ([#2195](https://github.com/xerj-org/xerj/issues/2195), PR+ [#2203](https://github.com/xerj-org/xerj/pull/2203)).+ - A weak nearest-neighbour page is labeled+ ([#1986](https://github.com/xerj-org/xerj/issues/1986), PR+ [#2221](https://github.com/xerj-org/xerj/pull/2221)).+ - An empty corpus ledger names the autoindex prefixes that are actually+ indexed ([#2181](https://github.com/xerj-org/xerj/issues/2181), PR+ [#2230](https://github.com/xerj-org/xerj/pull/2230)).+ - `xerj hub find` names the upstream repository (PR+ [#2249](https://github.com/xerj-org/xerj/pull/2249)).+ - A question whose topic no hub corpus covers is `NoCoverage`, not an+ ambiguous tie. `xerj ask` prints that no corpus covers the topic, points+ at `xerj autoindex` and `xerj hub find`, and exits 1. Exit 4 is unchanged+ when several corpora actually match. This is a partial fix of+ [#2179](https://github.com/xerj-org/xerj/issues/2179): the issue stays+ open, because no Phaser, pandas or charting pack was added and a slug+ that names a different project is still not explained (PR+ [#2267](https://github.com/xerj-org/xerj/pull/2267)).++### Testing+- - No test-only pull request merged in this window. The MCP tool-count- assertion was updated in the same change as local definition lookup (PR- [#2166](https://github.com/xerj-org/xerj/pull/2166)).++- A dropped replica is refilled to the primary's live set before it++ rejoins: insert, update and delete during the outage, then reopen the++ same data directory. Test only; no production change. It exercises the++ backfill in PR [#2328](https://github.com/xerj-org/xerj/pull/2328). Part++ of [#1170](https://github.com/xerj-org/xerj/issues/1170); the issue stays++ open (PR [#2341](https://github.com/xerj-org/xerj/pull/2341)).++- The MCP tool-count assertion was updated in the same change as local++ definition lookup (PR [#2166](https://github.com/xerj-org/xerj/pull/2166)).++### Documentation & site++- `/product` was rewritten against the v1.0.0-rc.98 binary (PR+ [#1926](https://github.com/xerj-org/xerj/pull/1926)). Eight answer pages+ from the 2026-10-20 agent-query captures (PR+ [#2251](https://github.com/xerj-org/xerj/pull/2251)). The Day/Night choice+ is kept across pages+ ([#1973](https://github.com/xerj-org/xerj/issues/1973), PR+ [#2169](https://github.com/xerj-org/xerj/pull/2169), samuelmbabhazi).+ Homepage `Link` headers advertise the API documentation (PR+ [#2291](https://github.com/xerj-org/xerj/pull/2291), mariomarcolongo).+ The Cline row in the English, Korean and Simplified Chinese README MCP+ tables is marked tested. Cline CLI 3.0.73 on Linux loaded the README+ `mcpServers` block against `xerj` v1.0.0-rc.98; `xerj_search` was in the+ tool list and one call ran. The IDE Configure button was not part of that+ run (PR [#2300](https://github.com/xerj-org/xerj/pull/2300)).+ The primary nav's plain GITHUB link is a stars badge: the GitHub mark and+ the star count, linking to the repository. The shipped count is 14,225,+ read 2026-10-24T02:05:55Z. `theme.js` refreshes it from the GitHub API,+ cached in the browser for 10 minutes, and keeps the shipped number if+ that call fails (PR [#2311](https://github.com/xerj-org/xerj/pull/2311)).++ The site states the MCP tool count main registers: 22 with a hub signing++ key (`xerj_def` and `xerj_batch_search` included), 19 when the three++ `xerj_hub_*` tools are dropped. The published `mcp-tools.json` already++ lists 22. The v1.0.0-rc.98 figure stays 20 and now names both tools that++ binary lacks (PR [#2350](https://github.com/xerj-org/xerj/pull/2350)).++ Canonical description, synced figures, FAQPage JSON-LD, robots++ Content-Signal, `llms.txt`, an IndexNow key, and MCP listing manifests++ (`server.json`, the mcpb manifest, and a Docker MCP Dockerfile). The++ registry manifest names the tagged release v1.0.0-rc.98 (PR++ [#2323](https://github.com/xerj-org/xerj/pull/2323)).+- A ready-to-paste DeepSeek Harness MCP config, with `env` and `cwd`+ ([#2286](https://github.com/xerj-org/xerj/issues/2286), PR+ [#2288](https://github.com/xerj-org/xerj/pull/2288)). Both Windows install+ directories are named: `~/.local/bin` for the `sh` installer, including+ Git Bash, MSYS and Cygwin, and `%LOCALAPPDATA%\Programs\xerj` for+ PowerShell+ ([#2285](https://github.com/xerj-org/xerj/issues/2285), PR+ [#2289](https://github.com/xerj-org/xerj/pull/2289)).+- AGENTS.md lists all twenty MCP tools (PR+ [#2150](https://github.com/xerj-org/xerj/pull/2150), redwolf2019). The+ Simplified Chinese README matches the English one (PR+ [#2149](https://github.com/xerj-org/xerj/pull/2149), redwolf2019). A Korean+ README translation (PR [#2164](https://github.com/xerj-org/xerj/pull/2164),+ pallidev).++### Community & field reports++- Field reports: multi-array JSON autoindex (PR+ [#2132](https://github.com/xerj-org/xerj/pull/2132)); MCP prefix isolation+ (PR [#2138](https://github.com/xerj-org/xerj/pull/2138), Jarvis636431);+ Windows 16 GB, three autoindex aborts, WAL replay restores the corpora (PR+ [#2174](https://github.com/xerj-org/xerj/pull/2174), WYSTAF); the #1940+ JSONL RSS reproduction (PR+ [#2241](https://github.com/xerj-org/xerj/pull/2241)); an rc.98 `xerj ask`+ of lz4 (PR [#2252](https://github.com/xerj-org/xerj/pull/2252)); consuming+ the published rust-vulns pack (PR+ [#2259](https://github.com/xerj-org/xerj/pull/2259)); MCP budget identity+ (PR [#2265](https://github.com/xerj-org/xerj/pull/2265), Jarvis636431);+ `corpus add` plus a hub-manifest pull request (PR+ [#2270](https://github.com/xerj-org/xerj/pull/2270), kamwoh); a Cline MCP+ setup from the README block, CLI only (PR- [#2301](https://github.com/xerj-org/xerj/pull/2301)).++ [#2301](https://github.com/xerj-org/xerj/pull/2301)); batch retrieval++ against a fresh isolated node with synthetic advisories — usage only,++ not a quality or performance evaluation (PR++ [#2334](https://github.com/xerj-org/xerj/pull/2334), Jarvis636431, written++ with OpenAI Codex).+- CLA signatures: ArkNill (#2153), pallidev (#2165), samuelmbabhazi (#2168),+ elewashy (#2173), WYSTAF (#2175), kamwoh (#2264), mgtf (#2275),- mariomarcolongo (#2292).++ mariomarcolongo (#2292). Jun516 joined the contributor list (PR++ [#2335](https://github.com/xerj-org/xerj/pull/2335)).++### Housekeeping++- Release-download counters landed as `[skip ci]` chores, not pull requests:- 2026-10-22 (30,604 assets, 25,047 binaries) and 2026-10-23 (31,411 assets,- 25,591 binaries). The figures are the commit subjects.++ 2026-10-22 (30,604 assets, 25,047 binaries), 2026-10-23 (31,411 assets,++ 25,591 binaries) and 2026-10-24 (33,978 assets, 27,993 binaries). The++ figures are the commit subjects.+## [1.0.0-rc.98] - 2026-10-21diff --cc ROADMAP.mdindex c5ea937f6,331792b9e..0c597cf4d--- a/ROADMAP.md+++ b/ROADMAP.md@@@ -2,44 -2,7 +2,59 @@@This roadmap tracks capabilities that are **planned but not yet fully implemented**, so the project's public claims stay honest about what ships today versus what is coming. Status is verified against the actual code and by real API requests to the release binary, not aspirational.- Last reviewed: 2026-10-23 (against `v1.0.0-rc.99` and `main`). Statuses trace to issues, merged PRs, the CHANGELOG, and the conformance suite; items carried forward from the 2026-07-12 review without fresh live verification are marked as such. This review line is machine-checked: `docs_capability_lists` fails the build if a release is cut without re-reviewing this file (issue #298 — closed as abandoned 2026-09-29; the machine check, not the issue, enforces the cadence now). This pass is the rc.99 release-cut roll:-Last reviewed: 2026-10-21 (against `v1.0.0-rc.98` and `main`). Statuses trace to issues, merged PRs, the CHANGELOG, and the conformance suite; items carried forward from the 2026-07-12 review without fresh live verification are marked as such. This review line is machine-checked: `docs_capability_lists` fails the build if a release is cut without re-reviewing this file (issue #298 — closed as abandoned 2026-09-29; the machine check, not the issue, enforces the cadence now). This pass is the rc.98 release-cut roll:++Last reviewed: 2026-10-24 (against `v1.0.0-rc.99` and `main`). Statuses trace to issues, merged PRs, the CHANGELOG, and the conformance suite; items carried forward from the 2026-07-12 review without fresh live verification are marked as such. This review line is machine-checked: `docs_capability_lists` fails the build if a release is cut without re-reviewing this file (issue #298 — closed as abandoned 2026-09-29; the machine check, not the issue, enforces the cadence now). This pass is the rc.99 release-cut roll:+the open-defects shortlist was re-verified against the live tracker at+cut time — **two open**: #1122 and #1170. Three closed inside the window:+#1110 (an unreadable corpus source fails the build instead of pruning, PR+[#2258](https://github.com/xerj-org/xerj/pull/2258)), #1267 (a resumed+catalog read-back stays on the changed set, PR+[#2231](https://github.com/xerj-org/xerj/pull/2231)) and #1635 (flush+admission is bounded, PR+[#2129](https://github.com/xerj-org/xerj/pull/2129), and flush deadlines use+the wall clock, PR [#2167](https://github.com/xerj-org/xerj/pull/2167)).+#1122 is partial: a helper thread that cannot be created no longer aborts+the process (PR [#2226](https://github.com/xerj-org/xerj/pull/2226)) and one+JSON document over 8 MiB is refused or streamed (PR+[#2256](https://github.com/xerj-org/xerj/pull/2256)), on Windows the+process cap follows commit space (PR+[#2236](https://github.com/xerj-org/xerj/pull/2236)), and a bulk reserves+memory before parsing while uncompressed JSON over 64 MiB is streamed (PR- [#2302](https://github.com/xerj-org/xerj/pull/2302)); the issue stays open++[#2302](https://github.com/xerj-org/xerj/pull/2302)), a shard thread or++merge buffer that cannot be allocated degrades instead of aborting (PR++[#2315](https://github.com/xerj-org/xerj/pull/2315)), scoped autoindex++threads and `POST /{index}/_update/{id}` do the same (PR++[#2322](https://github.com/xerj-org/xerj/pull/2322)), and a host under++16 GiB takes a cap of half its RAM with a smaller merge batch (PR++[#2340](https://github.com/xerj-org/xerj/pull/2340)); the issue stays open+(the memory-ceiling class and the WSL2 VM death are not addressed). #1170 is partial:+index metadata through the Raft log (PR+[#2257](https://github.com/xerj-org/xerj/pull/2257)), document routing to+the primary named in the create entry (PR+[#2271](https://github.com/xerj-org/xerj/pull/2271)), replica copies of+an acknowledged document write (PR- [#2287](https://github.com/xerj-org/xerj/pull/2287)), and acknowledgement++[#2287](https://github.com/xerj-org/xerj/pull/2287)), acknowledgement+once a quorum of those copies confirms (PR- [#2303](https://github.com/xerj-org/xerj/pull/2303)), and an on-disk Raft++[#2303](https://github.com/xerj-org/xerj/pull/2303)), an on-disk Raft+log replayed on restart (PR- [#2313](https://github.com/xerj-org/xerj/pull/2313)). Promotion, document- backfill, snapshot install, and `_bulk` / native ingest routing- stay open on #1170. The window since rc.98 is 93 merged pull requests; the- CHANGELOG lists every one. x86_64 binaries run without AVX2 (PR++[#2313](https://github.com/xerj-org/xerj/pull/2313)), a compacted Raft++snapshot installed on a lagging member (PR++[#2320](https://github.com/xerj-org/xerj/pull/2320)), document backfill++onto a replica that is behind (PR++[#2328](https://github.com/xerj-org/xerj/pull/2328), exercised by PR++[#2341](https://github.com/xerj-org/xerj/pull/2341)), `_bulk` and++`_update` on the shard primary (PR++[#2344](https://github.com/xerj-org/xerj/pull/2344)), and++`_update_by_query` on every shard primary (PR++[#2347](https://github.com/xerj-org/xerj/pull/2347)). Replica promotion,++`wait_for_active_shards`, native `/v1` ingest, `_delete_by_query`, and++moving copies when membership changes stay open on #1170. The window++since rc.98 is 115 merged pull requests; the CHANGELOG lists every one. x86_64 binaries run without AVX2 (PR+[#2253](https://github.com/xerj-org/xerj/pull/2253), which supersedes the+installer refusal in PR+[#2178](https://github.com/xerj-org/xerj/pull/2178)), and `ctutils` 0.4.5+closes RUSTSEC-2026-0385 (PR+[#2268](https://github.com/xerj-org/xerj/pull/2268)).+The rc.98 cut's record stands as written:the open-defects shortlist was re-verified against the live tracker atcut time — **five open**, unchanged: #1110, #1122, #1170, #1267, #1635. Noneclosed inside the window. The window since rc.97 is about 120 merged PRs: a@@@ -381,42 -344,30 +396,56 @@@ and the console review's), th`xerj-decide-v1` Hugging Face publication (operator credentials), and the GAbar itself — *The road to v1.0.0 GA* below.-**Open defects.** Five, all live on the tracker — the-shortlist the release-notes gate checks. From the rc.97 window:-[#1635](https://github.com/xerj-org/xerj/issues/1635) (autoindex at the-default worker count stalled at 70.9% on a 13,765-file / 1,153 MB repo,-with `_bulk` timeouts, HTTP 500s and a node that stopped answering-searches; the server logs point at admission control, not yet-instrumented). From the rc.92 window:-[#1267](https://github.com/xerj-org/xerj/issues/1267) (the finalize-slow-query residual after #1260: the catalog_generation read-back walk-brute-pages `term run_id` + `_id` sort at ~5.2 s per 1,000-doc page —-641 pages ≈ 35 min on the 402,814-doc catalog whenever a resume-rewrote everything — and doc-shaped verify windows with `size > 0`-still brute-scan the data indexes at 7–81 s per window, one exceeding-the client's 300 s budget mid-crawl; PR-[#1270](https://github.com/xerj-org/xerj/pull/1270) bounded the fast-agg-verify window, the walk and doc-lane residual stay open).-From the rc.81/82 windows:+**Open defects.** Two, both live on the tracker — the+shortlist the release-notes gate checks.[#1122](https://github.com/xerj-org/xerj/issues/1122) (reopened2026-10-05 when the reference node died at its memory ceiling with no-panic line). From the cluster-mode testing:-[#1170](https://github.com/xerj-org/xerj/issues/1170) (the Raft ring is-never connected to the engine). Filed from the corpus-program work:-[#1110](https://github.com/xerj-org/xerj/issues/1110) (the-generalization proof: second-domain pack + fresh-machine replay).+panic line). Partial in the rc.99 window: a helper thread that cannot+be created no longer aborts the process (PR+[#2226](https://github.com/xerj-org/xerj/pull/2226)), and a single JSON+document over 8 MiB is refused or streamed (PR+[#2256](https://github.com/xerj-org/xerj/pull/2256)), and on Windows the+process cap follows commit space rather than physical RAM alone (PR+[#2236](https://github.com/xerj-org/xerj/pull/2236)), and a bulk reserves+memory before parsing while uncompressed JSON over 64 MiB is streamed- (PR [#2302](https://github.com/xerj-org/xerj/pull/2302)). The memory-ceiling++(PR [#2302](https://github.com/xerj-org/xerj/pull/2302)), a shard thread++or merge buffer that cannot be allocated degrades instead of aborting++(PR [#2315](https://github.com/xerj-org/xerj/pull/2315)), scoped++autoindex threads and `POST /{index}/_update/{id}` do the same (PR++[#2322](https://github.com/xerj-org/xerj/pull/2322)), and a host under++16 GiB takes a cap of half its RAM with a smaller merge batch (PR++[#2340](https://github.com/xerj-org/xerj/pull/2340)). The memory-ceiling+class and the WSL2 VM death stay open.+[#1170](https://github.com/xerj-org/xerj/issues/1170) (cluster+replication). Partial in the rc.99 window: index metadata through the+Raft log (PR [#2257](https://github.com/xerj-org/xerj/pull/2257)),+document writes and search routed to the primary named in the create+entry (PR [#2271](https://github.com/xerj-org/xerj/pull/2271)), an+acknowledged document write copied onto replicas placed at create (PR- [#2287](https://github.com/xerj-org/xerj/pull/2287)), and that write++[#2287](https://github.com/xerj-org/xerj/pull/2287)), that write+acknowledged once a quorum of the copies confirms (PR- [#2303](https://github.com/xerj-org/xerj/pull/2303)), and an on-disk Raft++[#2303](https://github.com/xerj-org/xerj/pull/2303)), an on-disk Raft+log at `{data_dir}/_raft` replayed before the node serves (PR- [#2313](https://github.com/xerj-org/xerj/pull/2313)). Promotion,- document backfill, snapshot install, `_bulk` and native ingest stay- open.++[#2313](https://github.com/xerj-org/xerj/pull/2313)), a compacted Raft++snapshot installed on a lagging member (PR++[#2320](https://github.com/xerj-org/xerj/pull/2320)), the primary's live++documents copied onto a replica that is behind (PR++[#2328](https://github.com/xerj-org/xerj/pull/2328)), `_bulk` and++`_update` on the shard primary (PR++[#2344](https://github.com/xerj-org/xerj/pull/2344)), and++`_update_by_query` on every shard primary (PR++[#2347](https://github.com/xerj-org/xerj/pull/2347)). Replica promotion,++`wait_for_active_shards`, native `/v1` ingest, `_delete_by_query`, and++moving copies when membership changes stay open.+**Closed inside the rc.99 window and recorded in the CHANGELOG, not+carried here:** #1110 (an unreadable corpus source fails the build+instead of pruning, PR+[#2258](https://github.com/xerj-org/xerj/pull/2258)), #1267 (a resumed+catalog read-back stays on the changed set, PR+[#2231](https://github.com/xerj-org/xerj/pull/2231)) and #1635 (bounded+flush admission and wall-clock flush deadlines, PRs+[#2129](https://github.com/xerj-org/xerj/pull/2129) and+[#2167](https://github.com/xerj-org/xerj/pull/2167)).**Closed inside the rc.97 window and recorded in the CHANGELOG, notcarried here:** #1094 (decision flywheel write-back froze once the historyindex had BM25 support: with the local decide tier armed, a split history