[iduhtheman]

Summary

• Implement key holder concentration heatmap on key detail page #1245 - Holder concentration heatmap: donut chart with whale/midTier/retail
  tiers, unique holder count, and a top-5 holder table, backed by a new
  GET /keys/:keyId/holders/concentration endpoint. Added alongside the
  existing top-10 bar chart (HolderConcentrationChart), which doesn't cover
  tiers, unique counts, or a dedicated endpoint.
• Implement key holder exit notification banner for deprecation and retirement #1246 - Exit notice banner: amber styling for deprecation, red for
  retirement, with a live countdown and buyback price shown only for
  retirement. Added isRetiring/retirementBuybackPriceStroops/
  retirementNoticeExpiresAt to Course, following the existing
  isFrozen/freezeExpiresAt (Build key freeze status banner and trading block UI #1121) pattern. Shown on the key detail page
  (replacing the deprecation banner when retiring) and on portfolio holding
  rows.
• Build key support ticket UI for creator and holder dispute resolution #1250 - Key support tickets: Report Issue button on the key detail page
  and portfolio holding rows, opening a dialog to report frozen trading, a
  balance dispute, an incorrect fee, or another issue, optionally with a
  transaction hash. Tickets are listed in a new "My Tickets" section in
  account settings.
• Add key social sharing cards for discovery and portfolio positions #1251 - Social sharing: Share button on the key detail page, portfolio
  holding rows, and earned badge cards, opening a modal with pre-filled
  Twitter and Telegram share intents (key name, price, 24h change for keys;
  badge name and criteria for badges) plus a Copy Link action.

Test plan

• npx tsc -b: clean, no errors.
• npx eslint on all new/changed files: clean.
• New unit/component tests (54 passing): supportTicket.utils,
  socialShare.utils, SupportTicketDialog, ReportIssueButton,
  SocialShareModal, SocialShareButton, MyTicketsSection,
  HolderConcentrationHeatmap, ExitNoticeBanner.
• Re-ran existing PortfolioHoldingRow suites (29 tests) after wrapping them
  in QueryClientProvider, now required since the row renders the new
  Report Issue / Share buttons; all pass.
• Verified two pre-existing failures (WalletPortfolioPage percent-formatting
  assertions, CreatorDetailPage early-access/trade-confirmation-modal tests)
  reproduce identically on a clean upstream/dev checkout, unrelated to this
  change.

closes #1245
closes #1246
closes #1250
closes #1251

[drips-wave]

@iduhtheman Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits