fix(ui): adopt LoadingState in docs route Suspense fallbacks

[galuis116]

Summary

• 46 docs.*.tsx route files under apps/loopover-ui/src/routes/ each hand-rolled the identical literal <Suspense fallback={<p className="text-token-sm text-muted-foreground">Loading…</p>}> instead of the shared LoadingState component (@/components/site/state-views, re-exported from @loopover/ui-kit) that every other consumer in this app already uses (see changelog.tsx's <LoadingState title="Loading from npm…" />).
• Replaced the fallback in all 46 files with <Suspense fallback={<LoadingState />}> and added the matching import. LoadingState's default title is exactly "Loading…", so the visible text is unchanged — the only difference is the shared component's role="status"/aria-live="polite" accessible markup and spinner icon, in place of a plain, non-semantic <p>.
• Two files that also match the docs.*.tsx glob were deliberately left untouched: docs.index.tsx (a static landing page with no MDX content or Suspense boundary) and docs.fumadocs-spike-api-reference.tsx (wraps ClientOnly, not Suspense, for an unrelated Scalar API-reference spike, Spike: prototype fumadocs-mdx + Scalar docs pipeline on TanStack Start #6037). docs.tsx (the shared parent layout route) was also out of scope.
• No change to Suspense's boundary placement or the content component itself, per the issue's explicit scope.

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked a currently open issue this PR resolves.

Closes #6982

Validation

• git diff --check
• npm run typecheck (via npm run ui:typecheck, which builds @loopover/ui-kit then typechecks @loopover/ui and @loopover/ui-miner) — clean, no errors.
• npm run ui:lint — 0 errors (pre-existing, unrelated react-refresh/only-export-components warnings on other files are untouched baseline noise).
• npm run ui:test — full workspace run: @loopover/ui (65 files / 373 tests), @loopover/ui-miner (25 files / 291 tests), @loopover/miner-extension (5 files / 33 tests) — all passing, including the two new tests in docs-routes-loading-state.test.tsx.
• npm run test:workers / npm run build:mcp / npm run test:mcp-pack / npm run ui:openapi:check (not applicable — this PR only touches apps/loopover-ui/src/routes/**, no API/schema/worker/MCP surface)
• npm audit --audit-level=moderate (no dependency changes)
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries — apps/** is outside Codecov's strict patch gate, but a new regression test asserts LoadingState's accessible role="status" markup renders while suspended, plus a second test that all 46 in-scope docs.*.tsx files import and use LoadingState as their sole Suspense fallback (guarding against a future file re-adding the old inline <p> pattern).

If any required check was skipped, explain why:

• npm run ui:build currently fails on this sandbox with an unrelated pre-existing error (Rolldown failed to resolve import "@scalar/api-reference" from docs.fumadocs-spike-api-reference.tsx, a file this PR does not touch) — reproduced identically on a clean main checkout before starting this change, confirming it's a local dependency-install gap, not something this diff introduces.
• A live browser navigation to a docs route in this sandbox's dev server currently throws an unrelated pre-existing "CodeBlock is not defined" error from the MDX content provider — reproduces on every docs route regardless of whether the page has code fences, confirming it's a systemic dev-environment/MDX-provider wiring issue unrelated to this diff (no MDX component, docs-mdx-components.tsx, or docs-client-loader.tsx file was touched). See the UI Evidence section below for how screenshot evidence was captured instead.

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests. (N/A — no auth/cookie/CORS/session changes.)
• API/OpenAPI/MCP behavior is updated and tested where needed. (N/A — no API/OpenAPI/MCP surface.)
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks. (N/A — this PR only changes which shared loading-state primitive a static Suspense fallback renders, not any data-fetch behavior.)
• Visible UI changes include a UI Evidence section below with JPG/JPEG or PNG screenshots.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

UI Evidence

Captured by navigating Playwright to the real running app (so the actual compiled Tailwind stylesheet and dark theme are loaded exactly as production serves them), then rendering both fallback markups side by side — the old hand-rolled <p> and the new LoadingState output (same DOM shape LoadingState actually renders: Shell + Spinner), since a live docs-route navigation is blocked in this sandbox by the unrelated pre-existing MDX error noted above.

[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-18 06:25:21 UTC}

47 files · 1 AI reviewer · no blockers · readiness 88/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
Mechanical, well-scoped swap of a hand-rolled `<p>Loading…</p>` Suspense fallback for the shared `LoadingState` component across 46 docs.*.tsx route files, closing #6982. The change is purely additive (one new import + one JSX line per file), preserves the visible 'Loading…' text since that's LoadingState's default title, and correctly excludes the three out-of-scope files (docs.index.tsx, docs.fumadocs-spike-api-reference.tsx, docs.tsx) with documented reasoning. The included test both renders LoadingState's accessible markup and asserts all 46 files were touched consistently, which is a reasonable belt-and-suspenders check for a mechanical repo-wide edit.

Nits — 3 non-blocking

• docs-routes-loading-state.test.tsx:29-33 hardcodes the count 46 and the out-of-scope filename set — if a new docs.*.tsx route is added later without updating this test, it'll either silently pass at a new count or fail with a confusing message; consider deriving intent from a comment near the route generator/scaffold instead of a magic number.
• The per-file diffs are pure mechanical repetition (46x identical two-line change) — fine for a codemod-style PR, but worth confirming this was done via find/replace tooling rather than by hand to rule out a stray typo in any of the 46 files (none apparent from the shown diffs).
• Consider adding a lint rule or codemod script reference in CONTRIBUTING.md so future new docs.*.tsx routes are scaffolded with LoadingState by default, preventing regression to the old hand-rolled pattern.

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	#6982
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 (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 1963 registered-repo PR(s), 1287 merged, 52 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	galuis116; Gittensor profile; 1963 PR(s), 52 issue(s).
Improvement	✅ Minor	risk: clean · value: minor

Review context

• Author: galuis116
• 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: 1963 PR(s), 52 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/ai-summaries	desktop	before /docs/ai-summaries	after /docs/ai-summaries	—
/docs/ai-summaries	mobile	before /docs/ai-summaries (mobile)	after /docs/ai-summaries (mobile)	—
/docs/ams-config-precedence	desktop	before /docs/ams-config-precedence	after /docs/ams-config-precedence	—
/docs/ams-config-precedence	mobile	before /docs/ams-config-precedence (mobile)	after /docs/ams-config-precedence (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