added send link retry. Backend PR as well

.cursorrules

@@ -1,25 +1,42 @@
-# @dev Add cursor rules here. This goes in the LLM context window on every query when using cursor.
+# peanut-ui Development Rules
 
-## Random
+**Version:** 0.0.1 | **Updated:** October 17, 2025
 
-- never open SVG files, it crashes you. Only read jpeg, png, gif, or webp.
-- never run jq command, it crashes you.
+## 🚫 Random
 
-## Code quality
+- **Never open SVG files** - it crashes you. Only read jpeg, png, gif, or webp.
+- **Never run jq command** - it crashes you.
+- **Never run sleep** from command line - it hibernates pc.
 
-- Use explicit imports where possible
-- Make a best effort to keep code quality high. Reuse existing components and functions, dont hardcode hacky solutions.
-- When making changes, ensure you're not breaking existing functionality, and if there's a risk, explicitly WARN about it.
-- If you notice an opportunity to refactor or improve existing code, mention it. DO NOT make any changes you were not explicitly told to do. Only mention the potential change to the user.
-- Performance is important. Cache where possible, make sure to not make unnecessary re-renders or data fetching.
-- Separate business logic from interface. This is important for readability, debugging and testability.
+## 💻 Code Quality
 
-## Testing
+- **Boy scout rule**: leave code better than you found it.
+- **Use explicit imports** where possible
+- **Reuse existing components and functions** - don't hardcode hacky solutions.
+- **Warn about breaking changes** - when making changes, ensure you're not breaking existing functionality, and if there's a risk, explicitly WARN about it.
+- **Mention refactor opportunities** - if you notice an opportunity to refactor or improve existing code, mention it. DO NOT make any changes you were not explicitly told to do. Only mention the potential change to the user.
+- **Performance is important** - cache where possible, make sure to not make unnecessary re-renders or data fetching.
+- **Separate business logic from interface** - this is important for readability, debugging and testability.
+- **Flag breaking changes** - always flag if changes done in Frontend are breaking and require action on Backend (or viceversa)
 
-- Where tests make sense, test new code. Especially with fast unit tests.
-- tests should live where the code they test is, not in a separate folder
+## 🧪 Testing
 
-## Documentation
+- **Test new code** - where tests make sense, test new code. Especially with fast unit tests.
+- **Tests live with code** - tests should live where the code they test is, not in a separate folder
 
-- document major changes in docs.md/CHANGELOG.md
-- if you add any other documentation, the best place for it to live is usually docs/
+## 📁 Documentation
+
+- **All docs go in `docs/`** (except root `README.md`)
+- **Keep it concise** - docs should be kept quite concise. AI tends to make verbose logs. No one reads that, keep it short and informational.
+- **Check existing docs** before creating new ones - merge instead of duplicate
+- **Log significant changes** in `docs/CHANGELOG.md` following semantic versioning
+
+## 🚀 Performance
+
+- **Cache where possible** - avoid unnecessary re-renders and data fetching
+- **Fire simultaneous requests** - if you're doing multiple sequential awaits and they're not interdependent, fire them simultaneously
+
+## 📝 Commits
+
+- **Be descriptive**
+- **Use emoji prefixes**: ✨ features, 🐛 fixes, 📚 docs, 🚀 infra, ♻️ refactor, ⚡ performance

docs/CHANGELOG.md

@@ -8,6 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 
 ### Added
+
 - **Points System V2** with tier-based progression (0-4 Tier)
 - **QR Payment Perks** with tier-based eligibility and merchant promotions
 - Hold-to-claim interaction for perks with progressive screen shake animation
@@ -17,13 +18,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Dev tools page (`/dev/shake-test`) for testing animations and haptics
 
 ### Changed
+
 - QR payment flow now fetches payment locks in parallel with KYC checks for latency reduction
 - Perk claiming uses optimistic UI updates for instant feedback (claim happens in background)
 - Dev pages excluded from production builds for faster compile times
 - Removed Points V1 legacy fields from `Account` and `IUserProfile` interfaces
 
 ### Fixed
+
 - BigInt type handling in points balance calculations (backend)
 - Perk status now correctly reflects `PENDING_CLAIM` vs `CLAIMED` states in activity feed
 - Modal focus outline artifacts on initial load
 - `crypto.randomUUID` polyfill for older Node.js environments in SSR
+- **"Malformed link" race condition**: Added retry logic using TanStack Query (3 attempts with 1-2s delays) on claim side when opening very fresh links. Keeps showing loading state instead of immediate error. Uses existing TanStack Query dependency for automatic retry with linear backoff.
+- **Auto-refreshing balance**: Balance now automatically refreshes every 30 seconds and when app regains focus
+- **Real-time transaction history**: New transactions appear instantly via WebSocket integration with TanStack Query cache
+- **Optimistic updates**: Sending money now shows instant UI feedback with automatic rollback on error