[Auto-QA] Stale data and freshness indicator issues

[clubanderson]

Auto-QA [Data Freshness]: Stale Data

Detected: 2026-06-14T02:14:30.748Z | Focus: Data Freshness | Commit: 3130137 | Run: View

Findings

### Components with caching but no freshness indicator
Users should know when data was last updated:
  - `EnterpriseSidebar.tsx`
  - `ClusterCardCompact.tsx`
  - `ClusterCardFull.tsx`
  - `NamespaceResources.tsx`
  - `ClusterCardList.tsx`
  - `ClusterDetailModal.tsx`
  - `BlueprintInfoPanels.tsx`
  - `ProjectDetailPanel.tsx`
  - `AppErrorBoundary.tsx`
  - `AuthCallback.test.tsx`
  - `AuthCallback.contract.test.tsx`
  - `Layout.tsx`
  - `KeepAliveOutlet.tsx`


### Cards with data fetching but no demo mode subscription
May not respond to demo mode toggle:
  - `CloudEventsStatus.tsx`
  - `InstallCTAFlow.tsx`
  - `CardErrorFallback.tsx`

Suggested Improvements

• Add "Last updated X ago" timestamps to cached data displays
• Use useDemoMode/useCardDemoState to respond to demo mode toggle
• Replace "Loading..." text with Skeleton components
• Add TTL validation to localStorage reads
• Show visual indicators when data may be stale

PR Guidance: Keep changes under 50 lines (size S) for best acceptance rate. Split larger fixes into multiple PRs.

---

This issue was automatically created by the Auto-QA workflow during Data Freshness 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.