[Klaud Cold] docs: refer to InferenceX-e2e in MODELS doc / MODELS 文档改用 InferenceX-e2e 名称

[functionstackx]

Summary

Follow-up to #2343: the intro line of MODELS.md / MODELS_zh.md now says the doc tracks models benchmarked by InferenceX-e2e instead of InferenceX. GitHub PR URLs are untouched.

Docs-only change — head commit carries [skip-sweep].

中文说明

作为 #2343 的后续：MODELS.md / MODELS_zh.md 的引言改为记录 InferenceX-e2e 基准测试覆盖的模型（原为 InferenceX）。GitHub PR 链接保持不变。

仅文档变更 — head commit 带有 [skip-sweep] 标记。

🤖 Generated with Claude Code

[claude]

🟡 MODELS.md and MODELS_zh.md now say the doc tracks models benchmarked by "InferenceX-e2e" instead of "InferenceX", but this term appears nowhere else in the repo (README.md, AGENTS.md, and 28+ other docs all use the unsuffixed "InferenceX") and is not defined anywhere. Worth confirming this rename is intentional (and should propagate elsewhere) before merging, since it could just as easily be an automation artifact.

Extended reasoning...

What changed

The diff swaps a single word in the intro sentence of MODELS.md/MODELS_zh.md: "benchmarked by InferenceX" → "benchmarked by InferenceX-e2e". Nothing else in either file, or anywhere else in the repo, changes.

Why this is worth flagging despite being the PRs stated intent

The PR title and description do say this substitution is the entire point of the change ("MODELS doc now says ... InferenceX-e2e instead of InferenceX"), so on its face this is not an accidental typo the author overlooked mid-edit — it is the deliberate diff. I take that objection seriously and it is the reason I am not marking this normal.

But "the PR description matches the diff" is a different question from "the term is correct." A grep across the entire repository for InferenceX-e2e returns exactly the two lines this PR touches — zero other hits. Meanwhile the canonical name InferenceX appears 225+ times across README.md (# InferenceX™, Open Source Continuous Inference Standard), AGENTS.md ("InferenceX is an open-source automated benchmarking system..."), CONTRIBUTING.md, and every other doc in the repo. Results are published to inferencex.com, and the repo itself is SemiAnalysisAI/InferenceX. No workflow, script, or doc anywhere defines an entity called "InferenceX-e2e" or explains how it would differ from InferenceX (e.g., a distinct end-to-end test harness vs. the umbrella benchmarking project).

This PR is tagged [Klaud Cold], i.e., produced by an automated docs-maintenance agent, not a human author making a considered product-naming decision. For that class of change, "the diff matches the PR description" only tells you the agent executed its own plan faithfully — it does not tell you the plan itself was sound. A one-word rename to a brand/product name that (a) is unique to two lines in the whole repo, (b) has no definition anywhere, and (c) contradicts the same name used in README.md and AGENTS.md is a classic shape for an LLM-introduced hallucination/drift that happens to be internally consistent with its own PR description, since the agent wrote both.

Step-by-step proof

1. grep -rn "InferenceX-e2e" . → only MODELS.md:5 and MODELS_zh.md:5 (this PRs two changed lines).
2. grep -rn "InferenceX" README.md | head -1 → # InferenceX™, Open Source Continuous Inference Standard — confirms the canonical, trademarked name has no -e2e suffix.
3. grep -n "InferenceX is" AGENTS.md → InferenceX is an open-source automated benchmarking system... — the repos own architecture doc, unmodified by this PR, still uses the unsuffixed name.
4. No file/workflow defines InferenceX-e2e, so a reader of MODELS.md landing on this sentence has no way to resolve what makes it different from the InferenceX defined two clicks away in README.md.

Suggested resolution

Before merging, confirm whether "InferenceX-e2e" is an intentional new term that should be introduced (with a definition) and propagated consistently, or whether it should simply read "InferenceX" to match the rest of the repo. Given the total absence of the term elsewhere, reverting to "InferenceX" is the safer default absent an explicit definition.