Skip to content

armgit / xerj

Public Imported from GitHub
0

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.

test(hub): assert the plan's 90/80 routing targets; note Poetry scope gap

xerj-org1e420df0dcbb
diff --git a/engine/crates/xerj-hub/src/router.rs b/engine/crates/xerj-hub/src/router.rs
index edec466d9..c4a317f82 100644
--- a/engine/crates/xerj-hub/src/router.rs
+++ b/engine/crates/xerj-hub/src/router.rs
@@ -445,6 +445,11 @@ fn parse_requirements(text: &str) -> Vec<String> {
out
}
+// KNOWN SCOPE GAP: only PEP 621 `[project].dependencies` is parsed. Poetry's
+// `[tool.poetry.dependencies]` table (a map keyed by name, not a PEP 508 list)
+// is NOT read, so a pure-Poetry project contributes no dependency hints to
+// routing. Left unimplemented deliberately — PEP 621 is the cross-tool standard;
+// Poetry support is a separate change, not part of this fix.
fn parse_pyproject(text: &str) -> Vec<String> {
#[derive(Deserialize)]
struct PyProject {
diff --git a/engine/crates/xerj-hub/tests/routing.rs b/engine/crates/xerj-hub/tests/routing.rs
index 084fd21e1..2fa204cff 100644
--- a/engine/crates/xerj-hub/tests/routing.rs
+++ b/engine/crates/xerj-hub/tests/routing.rs
@@ -13,8 +13,9 @@
//! corpus's description — and routes every question twice: once with the line's
//! dependencies present in the working directory (a synthetic `Cargo.lock`), and
//! once with none. It asserts top-1 accuracy (a `Confident` verdict for the
-//! expected slug, or the expected slug first in an `Ambiguous` list) of at least
-//! 85% with dependencies and 70% without.
+//! expected slug, or the expected slug first in an `Ambiguous` list) against the
+//! plan's targets (`docs/CORPUS_HUB_V2_IMPLEMENTATION.md` §5): at least 90% with
+//! dependencies and 80% without.
//!
//! Only the crate's public API is used, so this exercises the router exactly as
//! the CLI will.
@@ -297,13 +298,13 @@ fn routing_fixture_meets_accuracy_targets() {
);
assert!(
- acc_with >= 0.85,
- "with-deps top-1 accuracy {:.1}% is below the 85% target",
+ acc_with >= 0.90,
+ "with-deps top-1 accuracy {:.1}% is below the 90% target",
acc_with * 100.0
);
assert!(
- acc_without >= 0.70,
- "without-deps top-1 accuracy {:.1}% is below the 70% target",
+ acc_without >= 0.80,
+ "without-deps top-1 accuracy {:.1}% is below the 80% target",
acc_without * 100.0
);
}