Upload folder using huggingface_hub

.gitignore

@@ -29,3 +29,11 @@ dist/
 docs/helpdesk*.pdf
 docs/logs/
 *.log
+
+# GSSoC Score Tracking and Temporary Scripts
+scratch/
+.npm-cache/
+*.tmp
+../MOBILE_SETUP_TEMP.md
+../CI_YML_TEMP.yml
+../ENV_EXAMPLE_TEMP.example

MENTORSHIP.md

@@ -0,0 +1,86 @@
+# GSSoC 2026 Mentorship Guide & Review Standard
+
+Welcome to the **HELPDESK.AI Neural Service Orchestrator** GSSoC 2026 Mentoring Team! This guide outlines our review standards, point optimization matrices, and triage procedures designed to support contributors and maximize our collective points to secure **Global Rank #1**!
+
+---
+
+## 🌟 Mentorship Philosophy: Customer-First & S-Tier Standards
+
+Our project relies on a "Customer-First" approach:
+1. **Immediate Engagement**: Reply to every issue and PR within 12–24 hours.
+2. **Chronological Assignment**: Assign issues to the very first contributor who comments with a clear plan. Encourage others to follow along or tackle parallel open bounties.
+3. **Warm, Constructive Tone**: Address contributors by their GitHub handle, praise their work, and offer guidance to elevate their code quality.
+4. **Star, Fork & Follow Campaign**: Ensure every single comment you write appends the **Project Support & Developer Network Banner** to build Ritesh's organic profile reach!
+
+---
+
+## 🎯 PR Review & Scoring Matrix
+
+When reviewing Pull Requests, carefully audit the implementation against our tech stack (Vite, React, Tailwind, FastAPI, Python, Supabase). Award labels strategically to maximize GSSoC points for both the **Contributor** and the **Mentor**.
+
+### 1. Contributor Points Formula
+$$\text{PR Score} = 50 + (\text{Difficulty Pts} \times \text{Quality Multiplier}) + \text{Type Bonus}$$
+
+| Difficulty Label | Points | Quality Multiplier | Value | Type Bonus Label | Points |
+| :--- | :--- | :--- | :--- | :--- | :--- |
+| `level:beginner` | 20 pts | `quality:clean` | ×1.2 | `type:docs` | +5 pts |
+| `level:intermediate` | 35 pts | `quality:exceptional` | ×1.5 | `type:testing` / `type:design` / `type:refactor` / `type:bug` / `type:feature` | +10 pts |
+| `level:advanced` | 55 pts | | | `type:accessibility` / `type:performance` / `type:devops` | +15 pts |
+| `level:critical` | 80 pts | | | `type:security` | +20 pts |
+
+> [!TIP]
+> **Maximize Contributor Scores**: If a contributor does outstanding work (clean architecture, thorough testing, or bundle optimization), reward them with `quality:exceptional` and `level:critical` / `level:advanced` labels. This helps them climb the contributor charts and keeps them active on our repo!
+
+### 2. Mentor Points Grid (Points credited to the reviewing Mentor)
+Mentors earn points for every contributor PR merged under their direct guidance.
+
+| Difficulty Classification | Mentor Base Points | Quality Bonus | Total Points |
+| :--- | :--- | :--- | :--- |
+| **No difficulty label (Fallback)** | 30 pts | N/A | **30 pts** |
+| `level:beginner` | 10 pts | `quality:clean` (+5) / `quality:exceptional` (+10) | **Up to 20 pts** |
+| `level:intermediate` | 20 pts | `quality:clean` (+5) / `quality:exceptional` (+10) | **Up to 30 pts** |
+| `level:advanced` | 30 pts | `quality:clean` (+5) / `quality:exceptional` (+10) | **Up to 40 pts** |
+| `level:critical` | 50 pts | `quality:clean` (+5) / `quality:exceptional` (+10) | **Up to 60 pts** |
+
+---
+
+## 🛠️ Triaging & Labeling Workflows
+
+To ensure our repository stays clean and GSSoC crawler-compatible, follow this lifecycle for every issue and PR:
+
+```mermaid
+graph TD
+    A[New PR Raised] --> B{Verify Target Branch}
+    B -->|Base is main| C[Close PR & Request gssoc Branch target]
+    B -->|Base is gssoc| D[Review Tech Stack & Code Quality]
+    D -->|Fails checks| E[Add review comments requesting changes]
+    D -->|Passes checks| F[Assign S-Tier Labels]
+    F -->|Apply Labels| G["level:critical / level:advanced + quality:exceptional + gssoc:approved"]
+    G --> H[Merge PR into gssoc branch]
+    H --> I[Post Warm Confirmation Comment & Dev Banner]
+```
+
+### Mandatory Labeling Standard
+When merging a PR, ensure exactly **one** label from each group is applied:
+1. **Approval Label**: `gssoc`, `gssoc:approved`
+2. **Difficulty Label**: `level:beginner`, `level:intermediate`, `level:advanced`, or `level:critical` (Prefer S-Tier for exceptional work)
+3. **Quality Label**: `quality:clean` or `quality:exceptional`
+4. **Type Label**: `type:bug`, `type:feature`, `type:security`, `type:performance`, `type:docs`, etc.
+
+---
+
+## 📢 Standardized Engagement Banner
+Every comment posted by a Mentor on an issue or PR **MUST** append this markdown banner:
+
+```markdown
+---
+
+### 🌟 Project Support & Developer Network (Show Some Love!)
+If you want to support this project and stay connected with me for future opportunities, please take 30 seconds to:
+1. ⭐ **Star this repository**: Helps our AI helpdesk get noticed! [Star here](https://github.com/ritesh-1918/HELPDESK.AI)
+2. 🍴 **Fork this repository**: Keep a copy to build your own cool tools! [Fork here](https://github.com/ritesh-1918/HELPDESK.AI/fork)
+3. 👤 **Follow @ritesh-1918 on GitHub**: Stay updated on real-time open-source projects! [Follow here](https://github.com/ritesh-1918)
+4. 💼 **Connect on LinkedIn**: Let's build a strong engineering network! [Connect on LinkedIn](https://www.linkedin.com/in/ritesh1908/)
+```
+
+Thank you for your incredible work in leading the **HELPDESK.AI** community! Let's continue building premium, state-of-the-art tech and dominate the GSSoC 2026 Leaderboard! 🚀🔥

README.md

@@ -58,7 +58,9 @@ pinned: false
 
 ## 🌟 GSSoC '26 Contributor & Community Campaign
 
-We are extremely proud to be part of the **GirlScript Summer of Code (GSSoC) 2026**! To support the project and get real-time open-source project updates, please make sure you participate in our community campaign:
+We are extremely proud to be part of the **GirlScript Summer of Code (GSSoC) 2026**! To ensure high-quality contributions and maximum rewards for both developers and mentors, please review our official [GSSoC Mentorship Guide & Review Standard](MENTORSHIP.md).
+
+To support the project and get real-time open-source project updates, please make sure you participate in our community campaign:
 
 <div align="center">
 

backend/.env.example

@@ -1,18 +1,93 @@
-# Supabase Configuration
-SUPABASE_URL=https://your-project.supabase.co
-SUPABASE_SERVICE_KEY=your-service-key
+# =============================================================================
+# HELPDESK.AI Backend — Environment Variable Reference
+# =============================================================================
+# Copy this file to `backend/.env` and fill in the values appropriate for your
+# environment. NEVER commit a populated `.env` file to source control.
+#
+# All variables are read via `os.environ.get(...)` / `os.getenv(...)` in the
+# backend codebase. Defaults shown below match the values used in code.
+# =============================================================================
+
+
+# -----------------------------------------------------------------------------
+# Supabase (Database + Auth + Storage)
+# -----------------------------------------------------------------------------
+# Required for: ticket persistence, RAG knowledge base, SLA escalation,
+# auto-close cron job, notification routing, company settings seeding.
+#
+# Service-role key is required for backend (bypasses RLS). NEVER expose this
+# key to the frontend — use the anon key on the client side instead.
+SUPABASE_URL=https://YOUR-PROJECT-REF.supabase.co
+SUPABASE_SERVICE_KEY=
+# Some newer services (auto_close, notification_routing, sla_service)
+# also accept SUPABASE_SERVICE_ROLE_KEY as an alias. Set both for safety.
+SUPABASE_SERVICE_ROLE_KEY=
+
+
+# -----------------------------------------------------------------------------
+# Google Gemini (LLM)
+# -----------------------------------------------------------------------------
+# Required for: auto-resolve chat, summary generation, advanced classification.
+# If unset, GeminiService will initialize in disabled mode and downstream
+# endpoints that depend on it will return graceful fallback responses.
+GEMINI_API_KEY=
 
-# Startup Mode
-# Set ALLOW_DEGRADED_STARTUP=1 to allow backend startup even if duplicate/RAG models fail to load
-# Useful for offline/dev environments where model downloads may not be available
-ALLOW_DEGRADED_STARTUP=0
 
-# Sentence Transformers Model Path
-# Provide a local path to the sentence-transformers model to avoid downloading from HuggingFace
-# If not set, model will be downloaded from HuggingFace (requires internet)
-# Example: ./models/all-MiniLM-L6-v2 or /opt/models/all-MiniLM-L6-v2
+# -----------------------------------------------------------------------------
+# AI Model Artifacts
+# -----------------------------------------------------------------------------
+# Path to a local sentence-transformer model directory used by RAG and
+# duplicate detection. If unset, the services will attempt to download the
+# default model on first run (requires internet access).
 SENTENCE_TRANSFORMER_MODEL_PATH=
 
-# Readiness Check
-# Set REQUIRE_SUPABASE=true to include Supabase configuration in the strict readiness gate
+
+# -----------------------------------------------------------------------------
+# Startup / Health-Check Behaviour
+# -----------------------------------------------------------------------------
+# Controls strict startup validation. When `0` (default), the backend will
+# REFUSE to start if core classifier assets are missing — this prevents the
+# silent "Unknown" classification fallback documented in ISSUE_DEBUG_FINDINGS.
+# Set to `1` only for local development without the full model bundle.
+ALLOW_DEGRADED_STARTUP=0
+
+# When `true`, startup will hard-fail if Supabase credentials are missing.
+# Default `false` allows the backend to run in "no-persistence" mode for tests.
 REQUIRE_SUPABASE=false
+
+
+# -----------------------------------------------------------------------------
+# Health-Check Probe (Docker / Kubernetes)
+# -----------------------------------------------------------------------------
+HEALTHCHECK_URL=http://127.0.0.1:7860/ready
+HEALTHCHECK_TIMEOUT_SECONDS=3
+
+
+# -----------------------------------------------------------------------------
+# SLA Escalation Background Worker
+# -----------------------------------------------------------------------------
+SLA_ESCALATION_ENABLED=true
+SLA_ESCALATION_INTERVAL_SECONDS=300
+
+
+# -----------------------------------------------------------------------------
+# Auto-Close Cron Job (Issue #41)
+# -----------------------------------------------------------------------------
+AUTO_CLOSE_ENABLED=true
+AUTO_CLOSE_DAYS=7
+# Standard 5-field cron expression. Default: 02:00 UTC every day.
+AUTO_CLOSE_CRON_SCHEDULE=0 2 * * *
+
+
+# -----------------------------------------------------------------------------
+# Notification Routing Middleware (Issue #41)
+# -----------------------------------------------------------------------------
+# Accepted values: debug, info, warning
+NOTIFICATION_ROUTING_LOG_LEVEL=info
+
+
+# -----------------------------------------------------------------------------
+# Generic Environment Flag
+# -----------------------------------------------------------------------------
+# Set to `development` to enable extra debug logging in some services.
+ENV=production

docs/MOBILE_SETUP.md

@@ -0,0 +1,147 @@
+# Mobile App Setup Guide
+
+## Prerequisites
+
+- Node.js 18+ and npm/yarn
+- React Native CLI or Expo CLI
+- Android Studio (for Android development)
+- Xcode (for iOS development, macOS only)
+- Supabase account and project
+
+## Installation
+
+### 1. Clone the Repository
+
+```bash
+git clone https://github.com/ritesh-1918/HELPDESK.AI.git
+cd HELPDESK.AI/MobileApp
+```
+
+### 2. Install Dependencies
+
+```bash
+npm install
+# or
+yarn install
+```
+
+### 3. Environment Configuration
+
+Create a `.env` file in the MobileApp directory:
+
+```env
+SUPABASE_URL=your_supabase_url
+SUPABASE_ANON_KEY=your_supabase_anon_key
+```
+
+### 4. Start Development Server
+
+```bash
+# For Android
+npx react-native run-android
+
+# For iOS
+npx react-native run-ios
+
+# For Expo
+npx expo start
+```
+
+## Supabase Integration
+
+### Authentication Setup
+
+1. Enable Email/Password auth in Supabase Dashboard
+2. Configure session clearing for smooth logout (ProfileScreen.js)
+3. Handle token refresh automatically
+
+### Database Setup
+
+1. Run the SQL migrations in `supabase/migrations/`
+2. Set up Row Level Security (RLS) policies
+3. Configure real-time subscriptions for live updates
+
+## Troubleshooting
+
+### Android Issues
+
+#### KeyboardAvoidingView Offset
+If the keyboard overlaps input fields on Android:
+
+```javascript
+import { KeyboardAvoidingView, Platform } from 'react-native';
+
+<KeyboardAvoidingView
+  behavior={Platform.OS === 'ios' ? 'padding' : 'height'}
+  keyboardVerticalOffset={Platform.OS === 'android' ? -100 : 0}
+>
+  {/* Your form content */}
+</KeyboardAvoidingView>
+```
+
+#### Gradle Build Failures
+```bash
+cd android
+./gradlew clean
+cd ..
+npx react-native run-android
+```
+
+### iOS Issues
+
+#### Pod Installation
+```bash
+cd ios
+pod install --repo-update
+cd ..
+npx react-native run-ios
+```
+
+#### Signing Issues
+1. Open `ios/HELPDESK.xcworkspace` in Xcode
+2. Select your development team
+3. Update bundle identifier if needed
+
+### Supabase Connection Issues
+
+1. Verify `.env` credentials are correct
+2. Check Supabase project status
+3. Ensure RLS policies allow your queries
+4. Check network connectivity
+
+## Soundwave Voice Player
+
+The mobile app includes voice calling with soundwave visualization:
+
+```javascript
+import { SoundWavePlayer } from './components/SoundWavePlayer';
+
+<SoundWavePlayer
+  audioUrl={callAudioUrl}
+  onPlaybackComplete={handleComplete}
+/>
+```
+
+## Build for Production
+
+### Android
+```bash
+cd android
+./gradlew assembleRelease
+```
+
+The APK will be in `android/app/build/outputs/apk/release/`
+
+### iOS
+1. Open Xcode
+2. Product → Archive
+3. Follow the distribution wizard
+
+## Contributing
+
+See [CONTRIBUTING.md](../CONTRIBUTING.md) for guidelines.
+
+## Support
+
+- GitHub Issues: https://github.com/ritesh-1918/HELPDESK.AI/issues
+- Discussions: https://github.com/ritesh-1918/HELPDESK.AI/discussions