[Auto-QA] Cards missing demo data support

[clubanderson]

Auto-QA [Demo Mode]: Demo Data Coverage

Detected: 2026-07-19T14:00:41.305Z | Focus: Demo Mode | Commit: 294a689 | Run: View

Findings

### Cards without demo data support
Add demo data for offline/demo mode:
  - `CardActionMenu.tsx` (435 lines) — no demo data support
  - `PendingSwapNotification.tsx` (81 lines) — no demo data support
  - `InfoTooltip.tsx` (159 lines) — no demo data support


### Cards with loading state but no Skeleton component
Use Skeleton for consistent loading UX:
  - `GitHubActivityItems.tsx`
  - `CardActionMenu.tsx`
  - `PendingSwapNotification.tsx`
  - `InfoTooltip.tsx`
  - `InstallCTAFlow.tsx`


### Stat blocks without demo data (9 files)

ClusterZone.tsx
AddCardModal.tsx
CardCatalogSection.tsx
DashboardCustomizer.tsx
StatsConfig.tsx
StatBlockModePicker.tsx
Skeleton.stories.tsx
Skeleton.tsx
StatsConfig.tsx

Suggested Improvements

• Cards using useCached* hooks already have demo data via the demoData: parameter in useCache()
• Cards using isDemoFallback/isDemoData from hooks are already covered
• For new cards: use useCached* hooks or pass demoData to useCache()
• Games and pure UI components (modals, animations) do not need demo data
• Test with localStorage.setItem("kc-demo-mode", "true")

PR Guidance: Keep PRs small and focused. Smaller PRs have higher acceptance rates.

---

This issue was automatically created by the Auto-QA workflow during Demo Mode focus day.

[github-actions]

🐝 Hi @clubanderson! I'm kubestellar-hive[bot], an automation bot for this repo.

Trusted users — org members and contributors with write access — can mention @kubestellar-hive in a comment to trigger repo automation.
On issues, that mention queues an automated fix attempt. On pull requests, it records extra context for existing automation.
This is not an interactive Q&A bot, so mentions should be treated as requests for automation rather than a conversation.

Automation may take a moment to start, and follow-up happens through workflow activity rather than chat replies.

[clubanderson]

Investigation Result: Issue Invalid ✅

All three flagged components are pure UI sub-components of CardWrapper and have already been documented as not requiring demo data support.

Evidence

1. Prior verification already completed

This exact same set of files was investigated and resolved in #20304, documented in .github/ISSUE_20304_VERIFICATION.md:

• CardActionMenu.tsx — Pure UI component for card action menu. No data fetching → No demo data needed
• InfoTooltip.tsx — Pure tooltip UI component. No data fetching → No demo data needed
• PendingSwapNotification.tsx — UI notification component. No data fetching → No demo data needed

2. Existing suppression comments in source

All three files already contain explicit // Auto-QA #21201: pure UI component comments added after issue #21201:

• web/src/components/cards/card-wrapper/CardActionMenu.tsx line 15
• web/src/components/cards/card-wrapper/InfoTooltip.tsx line 8
• web/src/components/cards/card-wrapper/PendingSwapNotification.tsx line 6

3. Why these components do not need demo data

These are sub-components rendered by CardWrapper — they receive all data through props and contain zero async data fetching, network calls, or loading states. As the issue itself notes: "Games and pure UI components (modals, animations) do not need demo data."

Stat blocks section

The "stat blocks" files (ClusterZone.tsx, Skeleton.tsx, AddCardModal.tsx, etc.) are likewise pure UI / SVG / story utilities with no data fetching.

Conclusion

No code changes are required. Closing as not planned — these components are correctly implemented and exempt from demo data requirements.