fix: resolve issues #390 and #391 in CustomerDashboard

[khushig159]

Closes #390
Closes #391

Summary

• Fix missing toast import causing event registration and cancellation to crash (Fixes [BUG] Missing toast import in CustomerDashboard.jsx - event registration and cancellation broken #390)
• Fix broken cancellation modal — Confirm button was never rendered due to missing refundInfo prop, modal not closing after confirm (Fixes [BUG] Multiple ReferenceErrors in CustomerDashboard.jsx - Browse Events and cancellation features completely broken #391)
• Fix duplicate lucide-react imports (Calendar, MapPin, Ticket)
• Fix duplicate fetchAvailableEvents useCallback declaration
• Add missing debouncedSearch via useDebounce hook
• Add missing socketRef, highlightTimeoutsRef, joinedEventIdsRef useRef declarations
• Add missing CATEGORIES constant
• Wrap Browse Events section in activeTab === 'Browse Events' conditional (was rendering on all tabs)

Files Changed

• Frontendd/src/pages/dashboard/CustomerDashboard.jsx
• Frontendd/src/components/ui/confirmation-modal.jsx
• backend/src/routes/registrationRoutes.js

Test Plan

• Event registration shows success/error toast
• Cancel Registration button opens modal with correct message and visible Confirm button
• Confirming cancellation closes modal and updates ticket status
• Browse Events section only appears on the Browse Events tab
• Category filter buttons render correctly

[vercel]

Someone is attempting to deploy a commit to the anubhav12302387's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

❌ PR Format Check — Failed — Please Fix Below

Hi @khushig159! Please fix the issues below before your PR can proceed to mentor review.

❌ Must Fix Before Proceeding

❌ Issue #390 is not assigned to you (@khushig159) — You must be assigned to the issue before submitting a PR.

Comment /assign on Issue #390 or ask a maintainer to assign it to you.

❌ Issue #391 is not assigned to you (@khushig159) — You must be assigned to the issue before submitting a PR.

Comment /assign on Issue #391 or ask a maintainer to assign it to you.

⚠️ Warnings (recommended)

⚠️ No testing steps mentioned — Add how reviewers can verify your changes

---

📋 EventOne PR Guidelines (click to expand)

Title format — Conventional Commits:
feat: · fix: · docs: · style: · refactor: · test: · chore: · perf:

Always link an issue: Closes #number

Use a feature branch — never PR directly from main

Write your own description — AI-generated content = gssoc:ai-slop label

EventOne × GSSoC Pipeline — Stage 1 Automated Check

[github-actions]

👋 Thanks for opening a PR, @khushig159!

Your PR has entered the 🎯 EventOne GSSoC PR Review Pipeline.

🟢 GSSoC PR detected — your PR will be routed to an approved GSSoC mentor for Stage 2 review.

What happens next

Stage	Reviewer	Checks
Stage 1 — Automated Validation	🤖 Bot	Title format · Issue link · AI Slop · Branch check
Stage 2 — Mentor Review	🧑‍🏫 GSSoC Mentor	Code + Quality Review
Stage 3 — Admin Final Gate	🔑 @anubhavxdev	Label check + Final Merge Decision

A pipeline status comment will appear below and update automatically as your PR progresses.

---

While you wait

• Sign all commits using git commit -s
• Link your issue with Closes #123
• Use a feature branch — not main
• Avoid unrelated changes in the same PR
• Write your own description — no AI-generated content

This comment is posted only once.

EventOne × GSSoC Automated Pipeline