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: make operational audit checklist explicit

buger7060bffa016a
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index c86002dbc..4c882faa9 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -31,10 +31,11 @@
- [ ] New ES-compatible behaviour has a matching YAML case under `engine/tests/es-compat-yaml/yaml/`
- [ ] Docs updated if user-visible behaviour changed
- [ ] For non-trivial changes: the applicable audit in [`docs/CONTRIBUTION_REVIEW.md`](../docs/CONTRIBUTION_REVIEW.md)
-- [ ] Operational docs/recipe audit records ordered success and failure execution,
- lifecycle/readiness/cleanup, persistent-data transitions/reindex,
- generated-copy propagation, and the scoped verifier (or explicitly records it
- as not applicable)
+- [ ] Operational docs/recipe audit is complete: it records ordered success and
+ failure execution, lifecycle/readiness/cleanup, persistent-data
+ transitions/reindex, generated-copy propagation, and the declared
+ inventory/completeness scope; each inapplicable item is marked `N/A` with a
+ reason.
**Not run:** <!-- name any check above you skipped, and why. This is expected and fine; hiding it is not. -->
diff --git a/docs/CONTRIBUTION_REVIEW.md b/docs/CONTRIBUTION_REVIEW.md
index 8835ac212..c6d43287c 100644
--- a/docs/CONTRIBUTION_REVIEW.md
+++ b/docs/CONTRIBUTION_REVIEW.md
@@ -60,7 +60,7 @@ product does not implement.
When a document is published through multiple paths, trace the publication
topology from its source through generated pages, indexes, navigation, and
-agent-facing copies. Reuse the repository release verifier for shipped-artifact
+agent-facing copies. Reuse `scripts/verify-release.sh` for shipped-artifact
claims rather than replacing it with a partial check. For docs-only changes,
run the scoped documentation/link/render verifier and record Cargo and ES-YAML
as not applicable; do not imply that an unrelated engine suite validated prose.