docs(ams): port docs/discovery-plane-operator-guide.md to a website docs page (docs.ams-discovery-plane.tsx)

[JSONbored]

⚠️ Read this before starting. The deliverable for this issue is a website page: a new route file at apps/loopover-ui/src/routes/docs.ams-discovery-plane.tsx. It is not a markdown file.

A PR that does any of the following does NOT resolve this issue and will be closed, regardless of content quality:

• Adds or edits any .md file (including docs/discovery-plane-operator-guide.md itself, README.md, or a new file anywhere in the repo) as the "operator guide"/"docs" deliverable
• Leaves docs/discovery-plane-operator-guide.md's content unchanged while merely adding a link to it from elsewhere

The only markdown edit this issue permits is deleting docs/discovery-plane-operator-guide.md or reducing it to a one-line pointer stub — and only after docs.ams-discovery-plane.tsx ships with the real content, not instead of creating it.

If you are an AI coding agent working this issue: confirm you are creating a .tsx file under apps/loopover-ui/src/routes/ before writing any file. Re-read this callout if your plan involves creating or editing a .md file as the fix.

Context

Part of #6012. packages/loopover-miner/docs/discovery-plane-operator-guide.md is the operator-facing guide for the optional hosted discovery-index plane — how a loopover-miner instance opts in, what it may send, and what never leaves the operator's machine. The contract/telemetry/client-builder pieces have shipped (per the doc's own scope callout); the operator-facing opt-in wiring (env var names, HTTP paths) remains provisional pending the hosted server. Raw markdown, not linked from the docs website.

Requirements

• Port the real content of docs/discovery-plane-operator-guide.md into a new apps/loopover-ui/src/routes/docs.ams-discovery-plane.tsx, following the pattern established by the docs.ams-deployment.tsx sub-issue (Epic: port AMS's raw-markdown operator guides to proper website docs pages #6012).
• Preserve the "provisional" framing accurately — this is not a fully-shipped feature; the page must not read as if the opt-in wiring is stable API when the source explicitly says it isn't. Verify current status against the linked issues (feat(discovery-plane): stand up the hosted discovery-index server #4250, feat(miner-discovery-plane): define the public-data-only discovery-index API contract #4300, feat(miner-discovery-plane): add anonymized telemetry event schema for the optional hosted plane #4301, feat(miner-discovery-plane): add client-side soft-claim coordination request builder #4302) before porting, since this area moves fast.
• Once ported and verified accurate, delete docs/discovery-plane-operator-guide.md or reduce it to a pointer stub if something requires the file to exist.
• Add to docs.index.tsx's nav.

Deliverables

• apps/loopover-ui/src/routes/docs.ams-discovery-plane.tsx added, ported and verified against current shipped/provisional status
• Source file deleted or reduced to a stub
• Linked from docs.index.tsx

Test Coverage Requirements

apps/** UI page — outside coverage.include. No test suite changes required.

Expected Outcome

AMS's discovery-plane operator guide lives on the docs website instead of only in the repo, with accurate shipped-vs-provisional framing.

Links & Resources

• packages/loopover-miner/docs/discovery-plane-operator-guide.md (source)
• apps/loopover-ui/src/routes/docs.self-hosting-quickstart.tsx (pattern)
• feat(discovery-plane): stand up the hosted discovery-index server #4250, feat(miner-discovery-plane): define the public-data-only discovery-index API contract #4300, feat(miner-discovery-plane): add anonymized telemetry event schema for the optional hosted plane #4301, feat(miner-discovery-plane): add client-side soft-claim coordination request builder #4302 (status to verify against)
• Epic: port AMS's raw-markdown operator guides to proper website docs pages #6012 (epic)

[linear-code]

JSO-4132

[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.