feat(miner-ui): add a build-time-flagged demo mode (no backend, no credentials)#7209
Merged
Conversation
…edentials) apps/loopover-miner-ui only exists as something an individual AMS miner builds and runs locally -- there's no way to show anyone what it looks like without them self-hosting it first, and #5229's open decision about whether hosted AMS reuses this dashboard is currently being made with no working prototype to point at. The 12 local API plugins that back this dashboard's real data are Vite dev/preview-server-only (configureServer/configurePreviewServer hooks) -- they never run in a built, deployed context at all, so "swap the plugin for a mock" can't work for an eventual static/Worker deploy. The mock has to live at the frontend fetch-client layer instead. Adds VITE_DEMO_MODE (mirrors loopover-ui's signInPreview() build-time-flag mechanism) gating a demo branch in the five REST fetchers backing the three main dashboard routes (run-history, ledgers, portfolio-queue + its release/requeue actions, governor). Governor pause/resume and queue release/requeue mutate real in-memory (browser-session-only) state rather than a static read-only view -- harmless to simulate, and a control that visibly does nothing is a worse demo than one that responds. A visible "Demo — sample data, no live backend" badge keeps this honest; every fixture value is entirely synthetic. Scoped deliberately to this mock layer only -- discover/attempt/chat (which trigger a real coding-agent iteration or ground against a live MCP connection) and the CI build+deploy workflow are follow-up work, not this change. Advances #5963
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | 7328476 | Commit Preview URL Branch Preview URL |
Jul 18 2026, 09:11 PM |
Bundle ReportBundle size has no change ✅ |
loopover-orb
Bot
added
the
gittensor:feature
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apps/loopover-miner-uionly exists today as something an individual AMS miner builds and runs locally — there's no way to show anyone what it looks like without them self-hosting it first, and Spec: client-surface strategy for hosted AMS (web dashboard vs. mobile/desktop apps vs. CLI-only) #5229's open decision about whether hosted AMS reuses this dashboard is currently being made with no working prototype to point at.configureServer/configurePreviewServerhooks, no build-time hooks) — they never run in a built, deployed context at all. This rules out "swap the plugin for a mock" as an approach for an eventual static/Worker deploy; the mock has to live at the frontend fetch-client layer instead.VITE_DEMO_MODE(mirrors loopover-ui'ssignInPreview()build-time-flag mechanism — same mechanism family, just covering N fabricated API responses instead of one fake session object) gating a demo branch in the five REST fetchers backing the three main dashboard routes: run-history, ledgers, portfolio-queue + its release/requeue actions, governor.Scoped deliberately to this mock layer only:
discover/attempt/chat(which trigger a real coding-agent iteration or ground against a live MCP connection) are not covered — fabricating a convincing multi-minute agent run is a separate, much larger content-design task than tabular summary data.Advances #5963 (a scoped first slice, not the full issue — see above)
Test plan
npm run typecheck(miner-ui workspace) — cleannpm run lint(miner-ui workspace) — clean (0 errors, only pre-existing unrelated warnings)npx vitest runinapps/loopover-miner-ui) — 320/320 passingdemo-data.test.ts(fixture shape invariants, governor pause/resume state transitions, queue-item removal), plus a demo-mode test added to each of the 5 fetcher test files confirming the demo branch never calls the injectedfetchImplVITE_DEMO_MODE=1Safety
apps/**is outside Codecov's patch-coverage scope entirely (repocodecov.yml'signorelist), so no coverage obligation here — verified against the actual config rather than assumed. Zero behavior change for the real (non-demo) self-host build:import.meta.env.VITE_DEMO_MODEis a build-time constant, so the "off" branch (realfetchcalls) is what every production/self-host build ships, byte-identical to before this PR.