docs(ams): decide + possibly port BENCHMARKS.md to a website docs page

[JSONbored]

Context

Part of #6012, lowest-confidence item in that epic — deliberately scoped as an evaluation-first issue, not a blind port. packages/loopover-miner/BENCHMARKS.md is a small, committed micro-benchmark for two purely local hot paths (discovery fan-out ranking, local SQLite read/write) with no network dependency, so its numbers are comparable across runs on the same machine. Unlike the other 10 files under #6012, this reads more like a repo-internal contributor artifact (how to run and interpret the benchmark) than an operator-facing guide — but it's genuinely ambiguous, which is why it's last in the sequence: the other 9 sub-issues will have established a real precedent for what "AMS docs on the website" looks like by the time this one is picked up.

⚠️ This issue explicitly does NOT presuppose the answer. Do not port this to a .tsx page as your first step. Decide first, port (or don't) second.

Requirements

• Step 1 — decide, and state your reasoning in the PR: does BENCHMARKS.md's content belong on the public LoopOver docs website (a page like docs.ams-benchmarks.tsx, if operators/evaluators would genuinely want to see these numbers), or is it correctly a repo-internal contributor artifact that should stay as markdown (if its real audience is someone about to modify the hot paths it covers, checking they haven't regressed)? Look at how the other 9 docs.ams-*.tsx pages from Epic: port AMS's raw-markdown operator guides to proper website docs pages #6012 turned out and whether any of them already surfaces performance/sizing information (the docs.ams-sizing.tsx sub-issue is a related but distinct "capacity" framing, not a "run this benchmark" framing) — don't duplicate.
• If the decision is "port it": follow the same pattern as the other Epic: port AMS's raw-markdown operator guides to proper website docs pages #6012 sub-issues — apps/loopover-ui/src/routes/docs.ams-benchmarks.tsx, <DocsPage> primitives, delete or stub BENCHMARKS.md, add to docs.index.tsx's nav.
• If the decision is "keep as markdown": close this issue with a comment explaining why, referencing the reasoning above. That is a legitimate, complete resolution of this issue — it does not need to result in a .tsx file to be done.

Deliverables

• A stated decision (in the PR or a closing comment) on whether this belongs on the website, with reasoning
• If ported: apps/loopover-ui/src/routes/docs.ams-benchmarks.tsx added, BENCHMARKS.md deleted/stubbed, linked from docs.index.tsx
• If not ported: issue closed with reasoning, BENCHMARKS.md left as-is

Test Coverage Requirements

If ported: apps/** UI page, outside coverage.include, no test suite changes required. If not ported: no code changes at all.

Expected Outcome

A deliberate, reasoned decision on this file's placement — not a default port just because the other 10 files in #6012 were ported.

Links & Resources

• packages/loopover-miner/BENCHMARKS.md (source)
• apps/loopover-ui/src/routes/docs.self-hosting-quickstart.tsx (pattern, if porting)
• Epic: port AMS's raw-markdown operator guides to proper website docs pages #6012 (epic)

[linear-code]

JSO-4135

[JSONbored]

Paused pending #6037. We've decided to move loopover's (and metagraphed's) docs to a shared MDX-based pipeline (fumadocs-mdx + Scalar for API reference) instead of hand-built TanStack routes per page — this issue's current approach (a new docs.*.tsx route file) would be rework the moment that lands. Marked maintainer-only to prevent new PRs against the current instructions while #6037 (the integration spike) is in progress.

Once #6037 lands with a proven pattern, this issue's Requirements will be rewritten to target an .mdx content file instead of a hand-built route, and maintainer-only will be removed. No action needed here until then.

[oktofeesh1]

Decision: keep as markdown, do not port

Read packages/loopover-miner/BENCHMARKS.md and evaluated it against the epic's own audience precedent from the other 9 sub-issues (#6022-#6031).

Reasoning:

• Its real audience is a contributor about to modify one of the two hot paths it covers (opportunity-ranker.js's rankCandidateIssues(), or the SQLite read/write path in local-store.js/portfolio-queue.js) — they run npm run benchmark:miner locally before/after their own change to check for a regression. That's a repo-internal contributor workflow, not something an operator or evaluator browsing the public docs site would consult.
• The command only works from a local checkout of the repo with the workspace installed — a website visitor has no way to run it regardless of whether the numbers are published.
• It doesn't overlap with docs.ams-sizing.tsx (docs(ams): port docs/sizing.md to a website docs page (docs.ams-sizing.tsx) #6026): that page is operator-facing capacity planning from measured, deployment-relevant CPU/RAM/disk numbers across laptop/fleet mode. This file is a "did my code change regress this specific hot path" dev sanity-check with no fixed pass/fail threshold, explicitly informational and machine-dependent.
• None of the site's existing audience groups (Miners, Maintainers, Repo owners, Operators, Agent authors) map onto "contributor modifying miner internals" — that's what the package's own README/BENCHMARKS.md already correctly serve.

Per this issue's own instructions, closing with this reasoning is a complete resolution — BENCHMARKS.md is left as-is, no .tsx page, no code changes.