docs(ui): federated fleet intelligence operator-consent page

[RealDiligent]

Summary

• Adds apps/loopover-ui/content/docs/federated-fleet-intelligence.mdx covering exported aggregate fields (Implement signed, anonymized signature-bundle export for federated fleet intelligence #6478), .loopover.yml opt-in / opt-out (Implement signed, anonymized signature-bundle export for federated fleet intelligence #6478/Opt-in collector client for federated fleet intelligence (push/pull transport) #6479), and operator-verifiable trust-gating from Design: trust-gating/anti-poisoning scoring rules for federated signal-bundle import #6477 (allowlist/collector as trust boundary, median, abuse recovery).
• Wires the page through the existing fumadocs-mdx thin route + docs nav / Maintainers index / command palette so /docs/federated-fleet-intelligence is discoverable.
• Documents shipped HMAC export signing; notes receive-side import/validation (Implement signature-bundle import + trust-gating validation for federated fleet intelligence #6480) may still be landing.
• Supersedes closed docs(ui): federated fleet intelligence operator-consent page #6598 (prettier lint on the command-palette entry; fixed before this reopen).

Closes #6482

Test plan

• Prior preview of /docs/federated-fleet-intelligence rendered on docs(ui): federated fleet intelligence operator-consent page #6598
• CI validate / validate-code green on this branch tip
• Sidebar link under Maintainers → Self-hosting: release & security
• Maintainers card on /docs lists the page

Made with Cursor

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-16 16:45:26 UTC}

6 files · 1 AI reviewer · no blockers · readiness 86/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This PR adds a docs-only page (federated-fleet-intelligence.mdx) plus the standard thin TanStack Router wiring (route file, generated routeTree, nav/palette/index links) matching the existing pattern used by every other docs page in this repo. The content accurately reflects the shipped code in src/orb/federated-collector.ts (opt-in gating via resolveCollectorEndpoint, no default collector, SSRF-safe URL check, shape-only bundle validation with no trust/signature verification yet) and is honest about #6480 not having landed. The routeTree.gen.ts diff is machine-generated (as with every other route addition in this file) and the `as any` cast at line 337 is a pre-existing pattern repeated for the new route, not a new risk.

Nits — 6 non-blocking

• The routeTree.gen.ts `as any` casts (e.g. apps/loopover-ui/src/routeTree.gen.ts:337) are pre-existing codegen boilerplate, but worth confirming this file is truly auto-generated and not hand-edited, since hand-editing it would be a real risk.
• No test coverage is added for the new route file (apps/loopover-ui/src/routes/docs.federated-fleet-intelligence.tsx), though this matches the apparent convention of the other docs.*.tsx route files, which also appear untested.
• The MDX claims collectorUrl must pass 'the same SSRF-safe URL rules as other manifest URL fields' — worth double-checking that federatedIntelligence.collectorUrl is actually validated at manifest-parse time (not just at collector-call time via isSafeHttpUrl in federated-collector.ts) so the doc's config-time claim matches reality.
• The docs promise `collectorMode: both` as the default when collectorUrl is set — confirm this matches resolveCollectorEndpoint's `config.collectorMode ?? "both"` fallback (it does, per the provided source), so no drift there, but keep an eye on this doc/code contract if the default ever changes.
• Consider adding a one-line note in the MDX pointing directly to the FederatedSignalBundleBody type definition file for readers who want the authoritative schema rather than a hand-copied table.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.

Decision drivers

• ✅ Code review — No blockers (1 reviewer)
• ✅ Gate result — Passing (No configured blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ Linked	#6598, #6482
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	❌ 8/20	High review scope from cached public metadata (2 linked issues).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 357 registered-repo PR(s), 174 merged, 32 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	RealDiligent; Gittensor profile; 357 PR(s), 32 issue(s).
Improvement	ℹ️ None detected	risk: low · value: none · LLM: moderate

Linked issue satisfaction

Addressed
The PR adds the federated-fleet-intelligence.mdx content covering exported fields, opt-in/out via .loopover.yml, and trust-gating design as the issue asked, and wires it into the docs route, nav, Maintainers index, and command palette so it's discoverable, matching the issue's stated scope.

Review context

• Author: RealDiligent
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 357 PR(s), 32 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Add a concise scope and risk note.
• Then work through the remaining 1 step in the Signals table above.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

Visual preview

Route	Viewport	Before (production)	After (this PR's preview)	Diff
/docs/federated-fleet-intelligence	desktop	before /docs/federated-fleet-intelligence	after /docs/federated-fleet-intelligence	—
/docs/federated-fleet-intelligence	mobile	before /docs/federated-fleet-intelligence (mobile)	after /docs/federated-fleet-intelligence (mobile)	—
/docs	desktop	before /docs	after /docs	—
/docs	mobile	before /docs (mobile)	after /docs (mobile)	—

Click any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.