Repository navigation
docs(llms): tool inventory = the released thirteen-tool MCP registry - #1078
Merged
Merged
Conversation
The MCP registry grew twice without llms.txt or llms-full.txt noticing: xerj_code_search + xerj_plan landed via #1005/#1076 and xerj_map via #1074 (merge f0b96d6). Both files still said the mcp-tools.json registry holds 'ten tools (the six HTTP operations plus the four brain tools)' and llms-full's own verify example printed the wrong count (jq '.tools | length' -> 10). The 'seventh canonical operation' arithmetic in the anthropic-tools.json line leaned on a seven-op numbering that no longer describes the surface (/_ask is HTTP since #1076; the catalog read always was). What changed, all outside the generated article tree (hand-written regions per scripts/seo/README.md): - llms.txt: mcp-tools.json line says thirteen and names all seven additions; anthropic line states the six-op files are the HTTP-core surface BY DESIGN (not 'everything else is CLI-only') and says 'xerj mcp' serves all thirteen - llms.txt: endpoint map gains POST /_ask (validated DSL out, 422 naming ungrounded phrases, deterministic not-LLM) — it was entirely undocumented - llms.txt: llms-full section pointer no longer claims 'all seven operations' - llms-full.txt: section 3 retitled 'THE CORE AGENT OPERATIONS' (TOC + header; 'NOT an eighth operation' ordinals de-numbered), the schema paragraph carries thirteen + the full composition, and the jq verify example now reads -> 13 Checked against what is released, not asserted: the 13 names in landing/docs/agents/schemas/mcp-tools.json (pinned to tool_specs() by tests/published_schema_drift.rs) are exactly the 13 both files now name; all 13 appear by name across the two files; seo_lint 0 gate violations (30 pre-existing warnings, same as main). Scope deliberately excluded (the queued llms rewrite, one job per PR): the obligation-language block in llms-full section 9, capability branching, last-updated stamp. The first-time-agent harness rerun binds that rewrite, not an inventory correction. Follow-up from plan #1054 items #1055/#1056.
neoneye
pushed a commit
to agent-memory-atlas-archive/xerj-org--xerj
that referenced
this pull request
Oct 1, 2026
The rc.80 release PR, docs-only on top of main (all engine code rides the merged window PRs; nothing here touches engine/crates or xerj-ux). rc.79 was folded into this cut by direction; no rc.79 tag exists. - CHANGELOG: [Unreleased] cut over to ## [1.0.0-rc.80] - 2026-09-30 with the measured-gates theme (three gates passed outright, three failed and ship opt-in/behind a flag with numbers published, one split); xerj-org#1095's own entry moves from [Unreleased] into the section unchanged; adds the citations the coverage gate was missing (xerj-org#1078 tool inventory, xerj-org#1079 ask-plan latency arm 1.129 ms, xerj-org#1083 egress-inventory classification, xerj-org#1089 console UX review) plus xerj-org#1097 (merged with no entry of its own). - ROADMAP: review line bumped to 2026-09-30 against rc.80; the ten-item program (xerj-org#1054, xerj-org#1055-xerj-org#1064) recorded as executed with every verdict; the semantic-detections row rewritten (the 'no alerting' text was false since xerj-org#1082); Next release -> v1.0.0 GA with the rc.80 cut record and a live-verified five-defect shortlist (xerj-org#1091-xerj-org#1094, xerj-org#1100) — xerj-org#1098/xerj-org#1099 were fixed and closed by xerj-org#1095 inside this release. - landing: all 53 V1.0.0-RC.78 stamps -> RC.80 (landing-constants-guard matches the tree version); data-latest-tag rc.78 -> rc.80. - llms.txt + llms-full.txt: the watcher caveat rewritten to the rc.80 reality (one real watch shape, everything else 501) with the earlier-version note kept in the open. - content/answers/does-xerj-support-s3-alerting-plugins.md: the alerting half rewritten (PARTIAL since xerj-org#1082) and the packs half corrected (record packs real since rc.78); updated bumped to 2026-09-30. - release-notes-gate.sh: an empty open-defects shortlist is a real state (tracker emptied 2026-09-29) — distinguish 'section moved' from 'section lists none'; verified against the live tracker. - engine/Cargo.toml 1.0.0-rc.78 -> 1.0.0-rc.80; Cargo.lock version strings only (no dependency moves — xerj-org#1095/xerj-org#1097 added none). docs_capability_lists: 15 passed, 0 failed. landing-constants-guard: all checks passed. release-notes-gate: PASS, all window PRs cited.
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.
Follow-up to #1074 + #1076 (plan #1054 items #1055/#1056). One job: make every tool/operation count in
landing/llms.txtandlanding/llms-full.txtmatch the released MCP registry.Why. The registry grew twice without the agent-facing docs noticing. Both files said
mcp-tools.jsonholds "ten tools (the six HTTP operations plus the four brain tools)" and llms-full's own verify example printedjq '.tools | length'→ 10. The real registry is thirteen (xerj_search,xerj_semantic_search,xerj_vector_search,xerj_hybrid_search,xerj_memory_store,xerj_memory_recall,xerj_brain_ego/link/unlink/overview,xerj_map,xerj_code_search,xerj_plan) — the study's own §8 lesson ("mcp-tools.json was stale at six tools … agent-facing docs must be generated from, or checked against, what is released") repeating verbatim.Changed (hand-written regions only, outside the generated article tree):
mcp-tools.jsonline says thirteen and names all seven additions; the anthropic line now says the six-op files are the HTTP-core surface by design (the old "the seventh canonical operation is CLI-only" arithmetic no longer describes the surface —POST /_askis HTTP since feat(api): POST /_ask + xerj_plan MCP tool — prompt in, validated DSL out (#1056) #1076 and the catalog read always was) and thatxerj mcpserves all thirteenPOST /_ask— it was entirely undocumented in either fileChecked against what is released, not asserted: all 13 names in
landing/docs/agents/schemas/mcp-tools.json(pinned totool_specs()bytests/published_schema_drift.rs) appear by name across the two files;scripts/seo/seo_lint.py→ 0 gate violations (30 pre-existing warnings, identical to main).Deliberately out of scope (the queued llms rewrite per
docs/research/llms-txt-2026-09/§9 — one job per PR, one open llms PR at a time): the obligation-language block in llms-full §9, capability branching, MCP per-client registration, last-updated stamp. The first-time-agent-harness rerun binds that rewrite, not an inventory correction; the study README was read before editing per the standing directive.