Operator-consent + privacy docs for federated fleet intelligence opt-in

[JSONbored]

Context

#1970 (opt-in federated fleet intelligence) requires "explicit operator-consent + privacy docs" per its own Deliverables. This issue is that documentation. Blocked by #6477 (the trust-gating design) — the docs need to accurately describe what the poisoning-resistance mechanism actually does, which isn't decided yet.

⚠️ Read this before starting. The deliverable is an MDX content page under apps/loopover-ui/content/docs/, following the pattern already proven out by the fumadocs-mdx migration (#6037, landed) and the existing pages in that directory (e.g. self-hosting-unified-ams-orb.mdx). It is not a hand-built docs.*.tsx route (the old pattern, now retired) and not a new root-level or docs/-directory markdown file. A PR that adds a .md file anywhere, or a new docs.*.tsx route component, does NOT resolve this issue and will be closed.

Requirements

• New .mdx file under apps/loopover-ui/content/docs/ (exact filename following this directory's existing kebab-case convention, e.g. federated-fleet-intelligence.mdx).
• Content must explicitly cover, in plain operator-facing language: what data is exported (referencing the enumerated-fields list from Implement signed, anonymized signature-bundle export for federated fleet intelligence #6478's implementation), what "opt-in" actually means procedurally (the exact .loopover.yml toggle from Implement signed, anonymized signature-bundle export for federated fleet intelligence #6478/Opt-in collector client for federated fleet intelligence (push/pull transport) #6479), the trust-gating/poisoning-resistance guarantee from Design: trust-gating/anti-poisoning scoring rules for federated signal-bundle import #6477 in terms an operator can verify for themselves (not marketing language), and how to opt back out.
• Add the new page to the content source's page tree / nav so it's actually discoverable — do not leave it orphaned outside the generated navigation (fumadocs-core's page-tree source, not a hand-maintained array like the retired docs.index.tsx's AUDIENCES).
• No wallet/hotkey/reward/trust-score wording, matching this repo's existing public-surface constraints.

Deliverables

• apps/loopover-ui/content/docs/federated-fleet-intelligence.mdx (or equivalent kebab-case name), reachable from the docs nav.
• Content reviewed against the actual shipped behavior of Implement signed, anonymized signature-bundle export for federated fleet intelligence #6478/Opt-in collector client for federated fleet intelligence (push/pull transport) #6479/Implement signature-bundle import + trust-gating validation for federated fleet intelligence #6480 (not the aspirational design) — file a follow-up correction issue if any deliverable shipped differently than originally scoped, don't silently document the wrong behavior.

Test Coverage Requirements

This is docs/UI work under apps/loopover-ui/**, outside coverage.include — Codecov's patch gate does not apply.

Expected Outcome

An operator considering opting into federated fleet intelligence has a real, accurate, discoverable page explaining exactly what's shared, how consent works, and what protects them from a poisoned peer bundle.

Links & Resources

• Opt-in federated fleet intelligence across self-hosted instances #1970 (parent — federated fleet intelligence)
• Design: trust-gating/anti-poisoning scoring rules for federated signal-bundle import #6477 (blocking — trust-gating design this page must accurately describe)
• Spike: prototype fumadocs-mdx + Scalar docs pipeline on TanStack Start #6037 (docs pipeline migration — the proven .mdx/fumadocs-core pattern to follow)
• apps/loopover-ui/content/docs/self-hosting-unified-ams-orb.mdx (example of an existing self-hosting-focused page in the same style)

[linear-code]

JSO-4448