feat: add AI chatbot with contextual memory and persistent chat history

[Aayush20253534]

Summary

Added an AI-powered DevTrack chatbot with Groq integration, dashboard-aware responses, contextual memory, and persistent user-specific chat history.

Closes #416

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor / code cleanup

Changes Made

• Added Groq-powered chatbot backend API route.
• Added persistent user-specific chatbot history using Supabase.
• Added contextual memory using recent chat history.
• Added chatbot history fetch API route.
• Updated chatbot UI to restore previous conversations.
• Added markdown-rendered AI responses.
• Integrated dashboard metrics into chatbot context.
• Updated Supabase schema with chatbot_messages table.

How to Test

Steps for the reviewer to verify this works:

1. Add GROQ_API_KEY to .env.local.
2. Run the updated Supabase schema or manually create the chatbot_messages table.
3. Start the app using npm run dev.
4. Log in with GitHub.
5. Open the dashboard chatbot.
6. Ask a dashboard-related question such as What are my top repositories?.
7. Send a contextual message.
8. Ask a follow up.
9. Refresh the page and reopen the chatbot.
10. Verify that previous chat history is restored.

Screenshots (if UI change)

Checklist

• Linked issue in summary
• npm run lint passes locally
• No TypeScript errors (npm run type-check)
• Self-reviewed the diff
• Added/updated tests if applicable

[vercel]

@Aayush20253534 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[github-actions]

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

• Make sure CI is passing (type-check + lint)
• Double-check the PR description is filled out and the issue is linked
• Feel free to ask questions in Discussions if you need help

[Priyanshu-byte-coder]

Production-breaking bug: hardcoded http://localhost:3000.

The getMetric helper fetches http://localhost:3000${path} — this does not work on Vercel or any cloud deployment where serverless functions cannot reach localhost:3000. The chatbot will silently return no context data in production and the AI will answer with empty metrics. Fix: call the underlying service functions/utilities directly instead of making self-HTTP calls.

Additional required fixes:

1. Wrong user ID key — session.user.email || session.user.name || 'unknown-user' is used to key chatbot_messages. GitHub OAuth email can be null/private; display names are not unique. Two users with the same display name and no public email share chat history. Use session.githubId / resolveAppUser like every other route.

2. No message length validation — message is stored in Supabase and forwarded to Groq with no size limit. Add a max length (e.g., 2000 chars).

3. Session data leaking to LLM — session.user is dumped into the system prompt context wholesale. This may include accessToken or other sensitive fields that should not be sent to Groq. Whitelist only what's needed (e.g., githubLogin).

4. GROQ_API_KEY missing env var returns "GROQ_API_KEY is missing" verbatim to the client — leaks internal implementation detail. Return a generic error message.

5. Missing Supabase migration — chatbot_messages is added to schema.sql but no timestamped migration file exists. Existing deployments won't get this table.

6. Missing EOF newline on supabase/schema.sql.

[Aayush20253534]

@Priyanshu-byte-coder

Implemented and addressed all requested review fixes:

• Removed localhost-based self-fetching and replaced it with production-safe direct metric helpers
• Added centralized chatbot analytics helpers in chatbot-metrics.ts
• Added persistent chatbot history with contextual conversation memory
• Added frontend + backend message length validation
• Sanitized LLM context by whitelisting only safe session fields (githubLogin)
• Replaced internal GROQ env leakage with generic service error handling
• Added Supabase migration for chatbot_messages
• Added missing EOF newline in schema.sql
• Improved chatbot formatting, analytics coverage, and follow-up context handling

The chatbot now supports:

• repository analytics
• PR summaries
• contribution streak insights
• contextual follow-up questions
• persistent user-wise memory
• production-safe deployment behavior

[Aayush20253534]

@Priyanshu-byte-coder Please Review the changes by me , I have implemented them successfully along with the production bugs I was supposed to fix.

[Priyanshu-byte-coder]

Two blockers:

1. lucide-react ^1.16.0 does not exist — the latest lucide-react is in the 0.x range. ^1.16.0 will fail to install. Check the actual latest version on npmjs.com and use that.

2. lucide-react is not in the project's current dependencies — adding it requires updating both package.json and package-lock.json consistently, and using the correct version.

Please fix the version and verify the install works before pushing.

[Aayush20253534]

@Priyanshu-byte-coder
All requested fixes have now been addressed.

Completed fixes include:

• Removed production-breaking localhost metric fetching
• Moved chatbot metric retrieval to reusable server-side utilities
• Fixed invalid App Router route exports causing production build failure
• Added safer chatbot metric architecture
• Added message length validation
• Reduced session data exposure to LLM context
• Fixed Lucide version problem as well.
• Added missing Supabase migration
• Fixed dependency installation consistency
• Verified npm run type-check
• Verified npm run lint
• Verified successful production build using npm run build

The remaining lint warnings are pre-existing unrelated warnings (next/image optimization suggestions and existing hook dependency lint warnings).

[Aayush20253534]

@Priyanshu-byte-coder I have fixed that lucide react problem , The latest version is indeed version
1.16.0 oh so that wasnt the issue still i uninstalled and reinstalled the latest lucide react version along with that there were a few production level issues which I have all fixed so please take a look to it.

[Priyanshu-byte-coder]

Several issues:

1. 3 missing EOF newlines on changed files
2. Extensive hardcoded colors — replace with CSS vars:
   • text-slate-*, bg-slate-*, border-slate-* → use var(--foreground), var(--muted-foreground), var(--card-muted), var(--border)
   • from-blue-600 to-indigo-700, bg-blue-600, bg-blue-500, border-blue-500 → var(--accent)
   • text-white → var(--foreground)
   • Hardcoded rgba() in shadow utilities → use var(--border) where possible
3. lucide-react: "^1.16.0" — this version does not exist on npm (latest stable is 0.x). Remove or use the already-installed version from the root package.json
4. Assets/ images committed — demo/design images don't belong in the repo; host externally or remove