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.

docs: record catalog namespace verification receipts

Jarvised5b53ef7726
diff --git a/tools/catalog-map/VERIFICATION.md b/tools/catalog-map/VERIFICATION.md
new file mode 100644
index 000000000..7cee50c9e
--- /dev/null
+++ b/tools/catalog-map/VERIFICATION.md
@@ -0,0 +1,118 @@
+# Catalog namespace verification — 2026-10-26
+
+OpenAI Codex, operated by Jarvis636431. macOS arm64 / Rust 1.97.1.
+Implementation `9d02f048`, independently based on upstream `9cf3f29c`; independent of the
+data-directory PR #2414, Codex-import PR #2413 and batch benchmark #2384.
+The generated schema and final transport controls are in `1f03e684`.
+The two diagnostics branches compose without conflicts via `git merge-tree`;
+their local execution receipts are separate, not a combined-runtime claim.
+
+## Commands and observed results
+
+From `engine/`:
+
+```sh
+cargo +1.97.1 fmt --all -- --check
+cargo +1.97.1 build --locked --offline --release -j 32 \
+ -p xerj-autoindex -p xerj-mcp -p xerj-server -p es-yaml-runner
+TMPDIR=/private/tmp cargo +1.97.1 test --locked --offline -p xerj-autoindex -- \
+ --test-threads=1 \
+ --skip content::tests::lossy_display_collisions_keep_distinct_alias_identities \
+ --skip corpus_data_skip_tests::corpus_index_summary_splits_indexed_extensions_from_ignored_data \
+ --skip inventory_delta_tests::a_non_utf8_excluded_name_is_matched_on_disk_via_path_id
+RUST_MIN_STACK=16777216 TMPDIR=/private/tmp cargo +1.97.1 test --locked --offline \
+ -p xerj-mcp -- --test-threads=1 \
+ --skip loopback_ignores_an_unreachable_proxy_and_a_proxied_503_names_the_proxy
+cargo +1.97.1 clippy --locked --offline --no-deps \
+ -p xerj-autoindex -p xerj-mcp --all-targets -- -D warnings -A dead_code
+cargo +1.97.1 clippy --locked --offline --no-deps \
+ -p xerj-mcp --all-targets -- -D warnings
+```
+
+- Scoped release build, fmt/whitespace and both Clippy commands passed.
+ The autoindex command-line dead-code allowance is for the existing
+ `resolve_reporting` warning; no source-level suppression was added.
+- Autoindex: **1,839 passed, 0 failed, 5 existing ignored, 3 filtered** across
+ unit/integration/doc-test invocations. The platform filters and earlier
+ baseline reproductions are documented in
+ [the existing import verification](../session-import/VERIFICATION.md#why-the-three-filters-exist).
+- MCP: **167 passed, 0 failed, 1 filtered** across unit/integration/doc-test
+ invocations, including **148 library tests** and published-schema drift.
+ Two new library tests check empty/positive maps and actual HTTP 404/403
+ tool-error classification; the existing description test gains scope checks.
+- The initial full MCP run hit a Tokio worker stack overflow in `local_def`.
+ Setting a 16 MiB minimum test-thread stack allowed all 5 local-def tests
+ to pass. This is an explicit local test environment setting, not a product
+ thread-stack or memory claim.
+- The proxy integration above failed at its phase-2 search against
+ `127.0.0.2:9`. It was then run alone on an unmodified detached **9cf3f29c**
+ checkout with the same stack setting and failed with the same diagnostic.
+ The cause was not diagnosed or patched here. Only that local invocation is
+ filtered; no test, assertion or CI skip changed. Other MCP tests passed.
+
+## CLI/MCP and generated schema
+
+From the repository root:
+
+```sh
+python3 tools/catalog-map/smoke.py --binary engine/target/release/xerj
+bash scripts/mcp-schema-check.sh --write
+bash scripts/mcp-schema-check.sh
+```
+
+Source-built `xerj v1.0.0-rc.99` was copied to a private executable snapshot:
+SHA-256 `e4aa924e5cc5d1f3cfde3dc4fb490054245106e139e51d6e4b1d11dd3c4b758f`.
+That same snapshot served transport checks, schema generation/check and the
+fresh-node ES-YAML gate. No production Rust changed after the release build.
+
+The old map implementation failed exactly **4 empty/missing CLI/MCP scope
+checks**; its **6 positive/401/403 controls passed**. The old executable's map
+and catalog source was compared against 9cf3f29c and is unchanged; it is an
+existing source-built executable, not a claimed clean full-baseline rebuild.
+The candidate passed **all 10 CLI/MCP cases**. CLI `--json` stdout also remained
+empty on failures and parsed correctly for populated datasets. Requests stayed
+within read-only root/search/mapping routes on a private loopback fixture.
+No live corpus registry or existing node was used to claim availability.
+
+The generator/check served **22 tools**. Only `xerj_map.description` changed in
+the generated JSON; no tool/input schema was removed or manually rewritten.
+
+## Conformance and website gates
+
+On a separate fresh private node using the snapshot:
+
+```sh
+engine/target/release/es-yaml-runner --url "$PRIVATE_NODE_URL" \
+ --dir engine/tests/es-compat-yaml/yaml
+```
+
+Observed **230 files; 1,447 passed, 0 failed, 10 skipped, 1,457 total; exit 0**.
+The unchanged policy reported 75 catch-lenient cases; node shutdown exited 0.
+No YAML, runner or catch-lenient policy changed.
+
+All 14 website checks passed: article-schema, URL-map and field-report tests;
+article/sitemap/head/link/OG generator checks; SEO lint; factcheck self-test,
+fixture-check and error gate; full audit; landing-constants guard. These are
+the commands in `.github/workflows/seo.yml` plus the constants guard. Non-gating
+warnings remain in untouched content/HTML; no HTML was regenerated or edited.
+Workflow-timeout guard and Python compilation also passed. New Markdown's
+final ignore match is `!tools/**/*.md`.
+
+## Review and scope
+
+Audited against `docs/CONTRIBUTION_REVIEW.md`: existing catalog queries,
+filtering, pagination, positive output and CLI exit codes are preserved.
+`search_present` uses the same request/retry path and classifies only HTTP 404
+as absence; 401/403 and transport/server failures remain errors. MCP 404 keeps
+`isError=true` and the raw engine body. Empty successes keep `matched:0` and
+`indexes:[]`, adding explanatory metadata rather than dataset rows. No managed
+corpus existence or name equivalence is inferred. The static hint triggers no
+registry request, fallback search or indexing.
+
+No persistent format, mapping, journal, ownership, mutation or recovery path
+changes. Durable-state migrations, failure atomicity of writes, distributed
+state, optional optimizations, models and performance benchmarking are not
+applicable to this read-only hint change. No speed/quality claim is made.
+Not tested: Linux/Windows execution, real managed corpus availability,
+production registry configurations or fixes to ranking/identity discovery.
+The known proxy fixture failure remains unresolved; hosted CI is separate.