Skip to content

FinceptTerminal is a modern finance application offering advanced market analytics, investment research, and economic data tools, designed for interactive exploration and data-driven decision-making in a user-friendly environment.

build updates

tilakpatel2247668e2b91cb
diff --git a/.gitignore b/.gitignore
index 26e9ad074..cd1e8c4b4 100644
--- a/.gitignore
+++ b/.gitignore
@@ -11,11 +11,12 @@ build.txt
cmder
reqgen.py
fincept_env
+*.md
*.db
# Allow specific markdown files
!README.md
-!CLAUDE.md
!docs/**/*.md
+!.github/**/*.md
python
treeview.py
testing
diff --git a/CLAUDE.md b/CLAUDE.md
deleted file mode 100644
index b4c66ffe1..000000000
--- a/CLAUDE.md
+++ /dev/null
@@ -1,400 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-**Fincept Terminal** is an open-source, Bloomberg-inspired financial analysis platform built with Tauri (Rust) + React + TypeScript. The goal is to create a data powerhouse for financial professionals by integrating 100+ data sources, AI agents, MCP connectors, and cutting-edge analysis tools - making institutional-grade financial analysis accessible to everyone.
-
-**Vision**: One-stop solution for financial professionals integrating stocks, forex, crypto, commodities, economic data, trade data, supply chain analytics, research papers, and real-time analysis with AI-powered insights.
-
-## Core Technology Stack
-
-- **Frontend**: React 19 + TypeScript + Vite + TailwindCSS v4
-- **Backend**: Tauri 2.0 (Rust) for native desktop wrapper
-- **Python Integration**: Embedded Python runtime for API wrappers and data processing
-- **UI Components**: Custom library based on Radix UI primitives (shadcn/ui inspired)
-- **Data Storage**: SQLite (via tauri-plugin-sql), IndexedDB (Dexie), localStorage
-- **State Management**: React Context API (AuthContext, ThemeContext)
-
-## Development Commands
-
-### Essential Commands
-```bash
-# Navigate to the main app directory first
-cd fincept-terminal-desktop
-
-# Install dependencies
-npm install
-
-# Development mode (Vite dev server + Tauri)
-npm run tauri dev
-
-# Build frontend only
-npm run build
-
-# Build production binary
-npm run tauri build
-
-# Run Vite dev server only (for frontend debugging)
-npm run dev
-```
-
-### Project Structure Locations
-```
-fincept-terminal-desktop/
-├── src/ # React frontend
-│ ├── components/
-│ │ ├── auth/ # Login, Register, Help, ForgotPassword
-│ │ ├── dashboard/ # Main terminal dashboard
-│ │ ├── payment/ # Payment processing screens
-│ │ ├── tabs/ # Financial terminal tabs
-│ │ │ ├── MarketsTab.tsx # Real-time market data
-│ │ │ ├── DashboardTab.tsx # Bloomberg-style overview
-│ │ │ ├── ChatTab.tsx # AI chat interface
-│ │ │ ├── agents/ # AI agent management
-│ │ │ ├── mcp/ # MCP server marketplace
-│ │ │ └── data-sources/ # Data source connectors
-│ │ ├── ui/ # Reusable UI components
-│ │ ├── common/ # Header, Footer, BackgroundPattern
-│ │ └── info/ # Legal pages
-│ ├── contexts/ # React contexts
-│ ├── services/ # API service layers
-│ ├── hooks/ # Custom React hooks
-│ └── stockBrokers/ # Broker integrations
-├── src-tauri/
-│ ├── src/ # Rust backend code
-│ │ ├── main.rs # Entry point
-│ │ ├── lib.rs # Library setup
-│ │ ├── commands/ # Tauri commands
-│ │ └── data_sources/ # Data source modules
-│ ├── resources/
-│ │ └── scripts/ # Python API wrappers
-│ │ ├── polygon_data.py # Polygon.io wrapper
-│ │ ├── yfinance_data.py # Yahoo Finance wrapper
-│ │ ├── fred_data.py # FRED economic data
-│ │ └── econdb_data.py # EconDB economic indicators
-│ ├── Cargo.toml # Rust dependencies
-│ └── tauri.conf.json # Tauri configuration
-└── package.json # Node dependencies
-
-legacy-python-depreciated/ # OLD DearPyGUI implementation (DO NOT USE)
-```
-
-## Architecture Deep Dive
-
-### 1. Python Integration Architecture
-
-**Embedded Python Runtime**: The project uses an embedded Python environment to run data fetching scripts that interface with various financial APIs.
-
-**Location**: `fincept-terminal-desktop/src-tauri/resources/scripts/`
-
-**Pattern**: All Python scripts follow a CLI-based JSON I/O pattern:
-- Input: Command-line arguments
-- Output: JSON to stdout
-- Rust invokes via `Command::new("python").arg("script.py")`
-
-**Example Python Wrapper Structure**:
-```python
-# Standard structure for all API wrappers
-import sys
-import json
-
-def get_data(symbol, **kwargs):
- """Fetch data from API"""
- try:
- # API call logic
- return {"success": True, "data": result}
- except Exception as e:
- return {"error": str(e)}
-
-def main():
- if len(sys.argv) < 2:
- print(json.dumps({"error": "Usage info"}))
- sys.exit(1)
-
- command = sys.argv[1]
- # Route to appropriate function
- result = get_data(sys.argv[2])
- print(json.dumps(result, indent=2))
-
-if __name__ == "__main__":
- main()
-```
-
-### 2. Data Source Integration Pattern
-
-**Current Data Sources** (in `resources/scripts/`):
-- `polygon_data.py` - Polygon.io API (stocks, crypto, forex)
-- `yfinance_data.py` - Yahoo Finance (quotes, historical, financials)
-- `fred_data.py` - Federal Reserve Economic Data
-- `econdb_data.py` - EconDB global economic indicators
-
-**Adding New Data Sources**:
-1. Create Python wrapper in `resources/scripts/`
-2. Follow the CLI JSON I/O pattern
-3. Support commands: `quote`, `historical`, `info`, etc.
-4. Add Rust command in `src-tauri/src/commands/`
-5. Expose to frontend via Tauri invoke
-
-### 3. Frontend Architecture
-
-**Tab-Based Bloomberg-Style Interface**:
-- Dashboard: Bloomberg-inspired 3-panel overview
-- Markets: Real-time market data with customizable watchlists
-- Chat: AI-powered financial assistant (Ollama integration)
-- Agents: AI agent orchestration and management
-- MCP: Model Context Protocol server marketplace
-- Data Sources: Connector management UI
-- Docs: In-app documentation browser
-
-**State Management**:
-- `AuthContext` (`src/contexts/AuthContext.tsx`): User authentication, subscription, session
-- Guest mode (24-hour device-based sessions) + Registered users (email/password)
-- Payment integration with Razorpay
-- Session persistence via localStorage
-
-**UI Consistency**: All tabs use Bloomberg color scheme:
-```javascript
-const BLOOMBERG_ORANGE = '#FFA500';
-const BLOOMBERG_WHITE = '#FFFFFF';
-const BLOOMBERG_RED = '#FF0000';
-const BLOOMBERG_GREEN = '#00C800';
-const BLOOMBERG_GRAY = '#787878';
-const BLOOMBERG_DARK_BG = '#1a1a1a';
-const BLOOMBERG_PANEL_BG = '#000000';
-```
-
-### 4. API Service Pattern
-
-All API services (`src/services/`) follow a consistent pattern:
-
-```typescript
-interface ApiResponse<T> {
- success: boolean;
- data?: T;
- error?: string;
- status_code?: number;
-}
-
-const makeApiRequest = async <T>(
- endpoint: string,
- options: RequestInit
-): Promise<ApiResponse<T>> => {
- // Comprehensive error handling
- // CORS support
- // API key authentication
- // Structured logging
-};
-```
-
-**Key Services**:
-- `authApi.tsx` - Authentication, registration, session management
-- `paymentApi.tsx` - Subscription plans, payment processing
-- `forumApi.tsx` - Community forum features
-- `marketDataService.tsx` - Market data fetching and caching
-
-## Key Features & Implementation Status
-
-### ✅ Completed Features
-- Tauri 2.0 desktop application framework
-- Authentication system (guest + registered users)
-- Payment integration (Razorpay)
-- Bloomberg-style UI with tab navigation
-- Function key shortcuts (F1-F12)
-- Forum tab with real functionality
-- Python wrapper framework
-- Basic market data integration (yfinance)
-- SQLite caching layer
-
-### 🚧 In Progress
-- Real-time WebSocket market data streaming
-- AI agent framework with Ollama
-- MCP server marketplace
-- Advanced charting (lightweight-charts)
-- Data source connector UI
-- Economic data integration (FRED, EconDB)
-
-### 📋 Planned Features
-- Broker integrations (Zerodha, Fyers, etc.)
-- Multi-language support
-- Plugin system
-- Mobile companion app
-- Custom indicator development
-- Backtesting engine
-
-## Development Guidelines
-
-### Adding New Financial Data Sources
-
-**Step 1: Create Python Wrapper** (`resources/scripts/new_source_data.py`)
-```python
-import sys
-import json
-import requests
-
-class NewSourceAPI:
- def __init__(self, api_key: str):
- self.api_key = api_key
- self.base_url = "https://api.newsource.com"
-
- def get_data(self, symbol: str):
- # Implementation
- pass
-
-def main():
- # CLI interface
- pass
-
-if __name__ == "__main__":
- main()
-```
-
-**Step 2: Add Rust Command** (`src-tauri/src/commands/new_source.rs`)
-```rust
-use tauri::command;
-use std::process::Command;
-
-#[command]
-pub async fn fetch_new_source_data(symbol: String) -> Result<String, String> {
- let output = Command::new("python")
- .arg("resources/scripts/new_source_data.py")
- .arg("quote")
- .arg(symbol)
- .output()
- .map_err(|e| e.to_string())?;
-
- let result = String::from_utf8_lossy(&output.stdout).to_string();
- Ok(result)
-}
-```
-
-**Step 3: Register Command** (in `src-tauri/src/lib.rs`)
-```rust
-mod commands;
-use commands::new_source::fetch_new_source_data;
-
-#[cfg_attr(mobile, tauri::mobile_entry_point)]
-pub fn run() {
- tauri::Builder::default()
- .invoke_handler(tauri::generate_handler![
- fetch_new_source_data,
- // ... other commands
- ])
- .run(tauri::generate_context!())
- .expect("error while running tauri application");
-}
-```
-
-**Step 4: Create Frontend Service** (`src/services/newSourceService.ts`)
-```typescript
-import { invoke } from '@tauri-apps/api/core';
-
-export const newSourceService = {
- async getQuote(symbol: string) {
- const result = await invoke<string>('fetch_new_source_data', { symbol });
- return JSON.parse(result);
- }
-};
-```
-
-### Adding New UI Tabs
-
-1. Create component in `src/components/tabs/NewTab.tsx`
-2. Follow Bloomberg color scheme
-3. Use existing UI components from `src/components/ui/`
-4. Add to tab list in `DashboardScreen.tsx`
-5. Assign function key shortcut (F1-F12)
-
-### Working with Authentication
-
-**Guest Users**: Automatically created on first launch, 24-hour sessions
-**Registered Users**: Email/password + API key authentication
-
-```typescript
-const { user, isAuthenticated, login, logout } = useAuth();
-
-// Check subscription status
-if (user?.subscription_plan === 'free') {
- // Limited features
-}
-```
-
-## Important Notes
-
-### DO NOT Modify
-- `legacy-python-depreciated/` - Old DearPyGUI implementation (archived)
-- Existing CLAUDE.md - Already contains legacy project context
-
-### Python Environment
-- Python scripts run via embedded interpreter
-- Dependencies managed separately from main project
-- Must be cross-platform compatible
-
-### Rust Backend
-- Keep lightweight - heavy processing in Python or frontend
-- Use for: File I/O, native integrations, performance-critical paths
-- Tauri commands are the bridge to frontend
-
-### Data Caching Strategy
-- **Short-term**: localStorage for UI state
-- **Medium-term**: SQLite for market data (10-15 min cache)
-- **Long-term**: IndexedDB for historical data
-
-## Testing & Debugging
-
-### Frontend Debugging
-```bash
-npm run dev # Vite dev server with hot reload
-```
-
-### Full App Debugging
-```bash
-npm run tauri dev # Opens app with DevTools
-```
-
-### Python Script Testing
-```bash
-cd fincept-terminal-desktop/src-tauri
-python resources/scripts/yfinance_data.py quote AAPL
-```
-
-### Rust Backend Debugging
-- Enable console in `tauri.conf.json` (development mode)
-- Check Rust output in terminal running `tauri dev`
-
-## GitHub Repository & Contribution
-
-**Repository**: https://github.com/Fincept-Corporation/FinceptTerminal/
-**Stars**: 376+ (as of 2025)
-**License**: MIT
-
-**Contribution Areas**:
-1. **Python API Wrappers** - Add new financial data sources
-2. **React Components** - UI improvements and new features
-3. **Rust Performance** - High-computation modules
-4. **Documentation** - Guides and tutorials
-5. **Analysis Models** - Statistical models and indicators
-
-## Intern Onboarding
-
-This project welcomes interns in three tracks:
-
-1. **Python Developers** - Build API wrappers for financial data providers
-2. **TypeScript/React Developers** - Enhance UI and create new features
-3. **Rust Developers** - Performance optimization and native integrations
-
-See dedicated intern guides:
-- `PYTHON_INTERN_GUIDE.md`
-- `TYPESCRIPT_INTERN_GUIDE.md`
-- `RUST_INTERN_GUIDE.md`
-
-## Resources & Documentation
-
-- **Tauri Docs**: https://tauri.app/
-- **React 19 Docs**: https://react.dev/
-- **Radix UI**: https://www.radix-ui.com/
-- **TailwindCSS v4**: https://tailwindcss.com/
-- **Yahoo Finance (yfinance)**: Python library for market data
-- **Polygon.io API**: Financial data API
-- **FRED API**: Federal Reserve economic data
diff --git a/fincept-terminal-desktop/FIX_ICONS.md b/fincept-terminal-desktop/FIX_ICONS.md
deleted file mode 100644
index d56a58dec..000000000
--- a/fincept-terminal-desktop/FIX_ICONS.md
+++ /dev/null
@@ -1,155 +0,0 @@
-# Fix Icon Display Issue
-
-## Problem
-After building, the installer/executable shows a generic CD icon instead of your custom icon.
-
-## Root Causes
-1. **Windows Icon Cache** - Windows caches icons aggressively
-2. **ICO File Format** - The `.ico` file must contain multiple embedded resolutions
-3. **Build Cache** - Tauri may cache old icons
-
-## Solution
-
-### Step 1: Regenerate icon.ico with all sizes
-
-You need to regenerate `icon.ico` to ensure it contains all required sizes:
-- 16x16
-- 32x32
-- 48x48
-- 64x64
-- 128x128
-- 256x256
-
-**Option A: Use Tauri CLI (Recommended)**
-```bash
-npm install -g @tauri-apps/cli
-
-# This will regenerate all icon sizes from icon.png
-npx @tauri-apps/cli icon src-tauri/icons/icon.png
-```
-
-**Option B: Use Online Tool**
-1. Go to https://www.icoconverter.com/ or https://convertico.com/
-2. Upload your `src-tauri/icons/icon.png`
-3. Select all sizes: 16, 32, 48, 64, 128, 256
-4. Download the generated `icon.ico`
-5. Replace `src-tauri/icons/icon.ico`
-
-**Option C: Use ImageMagick (if installed)**
-```bash
-magick convert icon.png -define icon:auto-resize=256,128,64,48,32,16 icon.ico
-```
-
-### Step 2: Clear Build Cache
-
-```bash
-# Clean Tauri build cache
-npm run tauri build -- --clean
-
-# Or manually delete the target folder
-rmdir /s /q src-tauri\target
-```
-
-### Step 3: Clear Windows Icon Cache
-
-**Method 1: Using Task Manager**
-1. Open Task Manager (Ctrl+Shift+Esc)
-2. Find "Windows Explorer" process
-3. Right-click → "Restart"
-
-**Method 2: Using Command Prompt (Administrator)**
-```cmd
-cd /d %userprofile%\AppData\Local
-attrib -h IconCache.db
-del IconCache.db
-start explorer
-```
-
-**Method 3: Delete Icon Cache Files (Most thorough)**
-```powershell
-# Run PowerShell as Administrator
-taskkill /f /im explorer.exe
-cd $env:LOCALAPPDATA
-del IconCache.db /a
-cd Microsoft\Windows\Explorer
-del *.db /a
-start explorer
-```
-
-### Step 4: Rebuild the Application
-
-```bash
-# Full clean rebuild
-npm run build
-npm run tauri build
-```
-
-### Step 5: Test the New Installer
-
-1. Find the installer in `src-tauri/target/release/bundle/nsis/` or `msi/`
-2. **Right-click the installer file → Properties → Check if icon shows correctly**
-3. Install on a clean/different machine if possible (icons cache on development machines)
-4. After install, check:
- - Desktop shortcut icon
- - Start menu icon
- - Installed app icon in Programs & Features
-
-## Verification Checklist
-
-- [ ] `icon.ico` contains multiple sizes (check file size > 30KB)
-- [ ] Cleared Windows icon cache
-- [ ] Deleted `src-tauri/target` folder
-- [ ] Rebuilt with `npm run tauri build`
-- [ ] Checked installer file icon (right-click → Properties)
-- [ ] Tested installer on different machine if available
-
-## Additional Tips
-
-### If Icon Still Doesn't Show:
-
-1. **Check icon.ico file size**
- - Should be > 30KB (contains multiple sizes)
- - If < 10KB, it likely only has one size
-
-2. **Verify icon is embedded in .exe**
- ```bash
- # Check if icon is in the built executable
- cd src-tauri/target/release
- # Icon should appear in file properties
- ```
-
-3. **Test on Clean Windows Installation**
- - Use Windows Sandbox or VM
- - This eliminates cache issues completely
-
-4. **Double-check paths in tauri.conf.json**
- ```json
- "icon": [
- "icons/32x32.png",
- "icons/64x64.png",
- "icons/128x128.png",
- "icons/icon.icns",
- "icons/icon.ico"
- ]
- ```
-
-5. **Ensure icon.ico is properly formatted**
- - Must be true `.ico` format, not renamed `.png`
- - Must contain multiple embedded bitmaps
-
-## Quick Test Command
-
-```bash
-# One-liner to clean and rebuild
-npm run build && rmdir /s /q src-tauri\\target && npm run tauri build
-```
-
-## Common Mistakes to Avoid
-
-❌ Don't just rename `icon.png` to `icon.ico` - it won't work
-❌ Don't skip clearing the Windows icon cache
-❌ Don't test on the same machine without clearing cache
-✅ Do regenerate icon.ico with all sizes embedded
-✅ Do test on a clean machine or VM
-✅ Do clear build cache before rebuilding
diff --git a/fincept-terminal-desktop/PORTFOLIO_IMPLEMENTATION_GUIDE.md b/fincept-terminal-desktop/PORTFOLIO_IMPLEMENTATION_GUIDE.md
deleted file mode 100644
index df8d0d4e2..000000000
--- a/fincept-terminal-desktop/PORTFOLIO_IMPLEMENTATION_GUIDE.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Portfolio Tab - Complete Implementation Guide
-
-## Overview
-This guide provides complete implementations for all portfolio views. Due to size constraints, implement these files as needed.
-
-## File Structure
-```
-src/components/tabs/portfolio/
-├── utils.ts (✓ Created)
-├── PositionsView.tsx (✓ Created)
-├── HistoryView.tsx (Create this)
-├── SectorsView.tsx (Create this)
-├── AnalyticsView.tsx (Create this)
-├── PerformanceView.tsx (Create this)
-├── RiskMetricsView.tsx (Create this)
-├── AlertsView.tsx (Create this)
-├── ReportsView.tsx (Create this)
-└── index.ts (Create this - exports all views)
-```
-
-## Currency Fix Applied
-- All formatCurrency() calls now respect portfolio.currency
-- Supports: USD ($), EUR (€), GBP (£), INR (₹), JPY (¥), etc.
-- utils.ts has complete currency formatting logic
-
-## Next Steps
-
-### 1. Create HistoryView.tsx
-Shows transaction history with proper currency formatting.
-
-### 2. Create SectorsView.tsx
-Pie chart showing sector allocation using recharts library.
-
-### 3. Create AnalyticsView.tsx
-Key metrics dashboard with charts:
-- Portfolio value over time (line chart)
-- Asset allocation (pie chart)
-- Top performers (bar chart)
-- Risk metrics cards
-
-### 4. Create PerformanceView.tsx
-Time-series performance charts:
-- Portfolio value history
-- Benchmark comparison
-- Returns by period
-
-### 5. Create RiskMetricsView.tsx
-Risk analysis dashboard:
-- Sharpe Ratio
-- Beta
-- Volatility
-- Max Drawdown
-- Value at Risk (VaR)
-
-### 6. Create AlertsView.tsx
-Price alert management:
-- Set target prices
-- Stop-loss levels
-- Alert history
-- Notifications
-
-### 7. Create ReportsView.tsx
-Tax and financial reports:
-- Capital gains (short/long term)
-- Dividend income
-- Transaction summary
-- Tax liability calculation
-- Export to PDF
-
-### 8. Update Main PortfolioTab.tsx
-Import all views and use them based on selectedView state.
-
-## Install Required Dependencies
-```bash
-npm install recharts
-npm install jspdf jspdf-autotable # For PDF export
-```
-
-## Implementation Priority
-1. HistoryView (essential)
-2. SectorsView (visual appeal)
-3. AnalyticsView (comprehensive)
-4. RiskMetricsView (professional)
-5. PerformanceView (advanced)
-6. ReportsView (compliance)
-7. AlertsView (trading features)
-
diff --git a/fincept-terminal-desktop/VERSION_UPDATE_GUIDE.md b/fincept-terminal-desktop/VERSION_UPDATE_GUIDE.md
deleted file mode 100644
index cda35cc36..000000000
--- a/fincept-terminal-desktop/VERSION_UPDATE_GUIDE.md
+++ /dev/null
@@ -1,121 +0,0 @@
-# Version Update Guide
-
-## Current Version: 3.0.0
-
-## How to Update Version
-
-When releasing a new version, update the following files:
-
-### 1. Configuration Files (Required for Build)
-
-Update these 3 files with the new version number:
-
-1. **`src-tauri/tauri.conf.json`** (line 4)
- ```json
- "version": "3.0.0"
- ```
-
-2. **`src-tauri/Cargo.toml`** (line 3)
- ```toml
- version = "3.0.0"
- ```
-
-3. **`package.json`** (line 4)
- ```json
- "version": "3.0.0"
- ```
-
-### 2. UI Display Constant (Required for In-App Display)
-
-4. **`src/constants/version.ts`** (line 5)
- ```typescript
- export const APP_VERSION = '3.0.0';
- ```
-
-## Version Display Locations
-
-The version is automatically displayed in:
-
-1. **Command Bar** - Shows `v3.0.0` in green next to the timestamp
-2. **Help Menu** - "About Finxept v3.0.0" menu item
-3. **Installer Filename** - `Fincept-Terminal_3.0.0_x64-setup.exe`
-4. **Windows Program Properties** - Version info in installed apps
-
-## Version Numbering Convention
-
-Follow **Semantic Versioning** (SemVer):
-
-- **Major.Minor.Patch** format (e.g., 3.0.0)
-- **Major**: Breaking changes or major features (3.0.0 → 4.0.0)
-- **Minor**: New features, backwards compatible (3.0.0 → 3.1.0)
-- **Patch**: Bug fixes, minor improvements (3.0.0 → 3.0.1)
-
-### Examples:
-- `3.0.0` → `3.0.1` - Bug fix release
-- `3.0.0` → `3.1.0` - New feature added
-- `3.0.0` → `4.0.0` - Major redesign or breaking changes
-
-## Microsoft Store Versioning
-
-For Microsoft Store submissions:
-- Use 4-part versioning: `Major.Minor.Build.Revision`
-- Example: `3.0.0.0` or `3.0.1.5`
-- Each submission must have a higher version than the previous
-- Store may take 24-48 hours for review
-
-## Build Commands
-
-After updating version:
-
-```bash
-# Development build
-npm run tauri dev
-
-# Production build (creates installers with version in filename)
-npm run tauri build
-```
-
-## Version Update Checklist
-
-- [ ] Update `src-tauri/tauri.conf.json`
-- [ ] Update `src-tauri/Cargo.toml`
-- [ ] Update `package.json`
-- [ ] Update `src/constants/version.ts`
-- [ ] Test development build: `npm run tauri dev`
-- [ ] Build production installers: `npm run tauri build`
-- [ ] Test installers on clean machine
-- [ ] Verify version displays correctly in app
-- [ ] Create git tag: `git tag v3.0.0`
-- [ ] Push tag: `git push origin v3.0.0`
-- [ ] Create GitHub release with installers
-
-## Quick Version Bump Script (Optional)
-
-You can create a script to update all files at once:
-
-```bash
-# Example: bump-version.sh
-NEW_VERSION="3.1.0"
-
-# Update tauri.conf.json
-sed -i 's/"version": "[^"]*"/"version": "'$NEW_VERSION'"/' src-tauri/tauri.conf.json
-
-# Update Cargo.toml
-sed -i 's/version = "[^"]*"/version = "'$NEW_VERSION'"/' src-tauri/Cargo.toml
-
-# Update package.json
-sed -i 's/"version": "[^"]*"/"version": "'$NEW_VERSION'"/' package.json
-
-# Update version.ts
-sed -i "s/APP_VERSION = '[^']*'/APP_VERSION = '$NEW_VERSION'/" src/constants/version.ts
-
-echo "✅ Version updated to $NEW_VERSION"
-```
-
-## Notes
-
-- The **`tauri.conf.json`** version is the primary source for installers
-- The **`src/constants/version.ts`** file is used for UI display only
-- Keep all versions in sync to avoid confusion
-- Always test after version updates
-- Version is embedded in installer filename automatically
diff --git a/fincept-terminal-desktop/src-tauri/resources/scripts/CLAUDE.md b/fincept-terminal-desktop/src-tauri/resources/scripts/CLAUDE.md
deleted file mode 100644
index e50eec72d..000000000
--- a/fincept-terminal-desktop/src-tauri/resources/scripts/CLAUDE.md
+++ /dev/null
@@ -1,421 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with API wrapper files in this repository.
-
-## Overview
-
-This directory contains Python API wrapper files that provide modular, fault-tolerant interfaces to various financial and economic data providers. Each wrapper follows a consistent design pattern and CLI interface for seamless integration with the Rust backend via Tauri commands.
-
-## Architecture Pattern
-
-### Core Design Principles
-
-1. **Modular Endpoint Design**: Each API endpoint is implemented as an independent method with isolated error handling
-2. **Fault Tolerance**: Failed endpoints don't crash the entire wrapper - errors are contained and reported
-3. **CLI-First Interface**: All wrappers expose a command-line interface that outputs JSON for Rust integration
-4. **Consistent Error Handling**: Standardized error format across all wrappers
-5. **Rate Limiting**: Built-in rate limiting for APIs with usage restrictions
-6. **Flexible Parameters**: Support for optional parameters with sensible defaults
-
-### File Structure Pattern
-
-```
-<provider>_data.py
-├── Header Documentation
-├── Imports
-├── Constants & Configuration
-├── Error Classes
-├── Main Wrapper Class
-│ ├── Initialization & Configuration
-│ ├── Private Helper Methods
-│ ├── Individual Endpoint Methods
-│ └── Composite Methods (optional)
-└── CLI Interface (main function)
-```
-
-## Required Components
-
-### 1. Header Documentation
-```python
-"""
-Provider Name Data Fetcher
-Brief description of the API and its capabilities
-Returns JSON output for Rust integration
-
-API Documentation:
-- Base URL: https://api.example.com/v2
-- Authentication: API key required
-- Rate limits: X requests per minute
-"""
-```
-
-### 2. Standard Imports
-```python
-import sys
-import json
-import os
-import requests
-from datetime import datetime, timedelta
-from typing import Dict, Any, Optional, List, Union
-```
-
-### 3. Error Class Pattern
-```python
-class ProviderError:
- """Error handling wrapper for API responses"""
- def __init__(self, endpoint: str, error: str, status_code: Optional[int] = None):
- self.endpoint = endpoint
- self.error = error
- self.status_code = status_code
- self.timestamp = int(datetime.now().timestamp())
-
- def to_dict(self) -> Dict[str, Any]:
- return {
- "success": False,
- "error": self.error,
- "endpoint": self.endpoint,
- "status_code": self.status_code,
- "timestamp": self.timestamp
- }
-```
-
-### 4. Main Wrapper Class
-```python
-class ProviderWrapper:
- """Modular Provider API wrapper with fault tolerance"""
-
- def __init__(self, api_key: Optional[str] = None):
- self.api_key = api_key or os.environ.get('PROVIDER_API_KEY', '')
- self.base_url = "https://api.provider.com/v2"
- self.session = requests.Session()
- self.session.headers.update({
- 'User-Agent': 'Fincept-Terminal/1.0',
- 'Authorization': f'Bearer {self.api_key}' if self.api_key else ''
- })
-
- # Rate limiting (if applicable)
- self.last_request_time = 0
- self.min_request_interval = 1.0 # seconds
-
- def _rate_limit(self):
- """Implement rate limiting for API"""
- # Implementation varies by provider limits
- pass
-
- def _make_request(self, endpoint: str, params: Optional[Dict] = None) -> Dict[str, Any]:
- """Centralized request handler with comprehensive error handling"""
- # Standard implementation for all API calls
- pass
-```
-
-### 5. Endpoint Method Pattern
-
-#### Individual Endpoint Method
-```python
-def get_<endpoint_name>(self, required_param: str, optional_param: str = "default") -> Dict[str, Any]:
- """Brief description of what this endpoint does
-
- Args:
- required_param: Description of required parameter
- optional_param: Description of optional parameter with default
-
- Returns:
- JSON response with data or error information
- """
- try:
- # Parameter validation
- if not required_param:
- return ProviderError('<endpoint_name>', 'Required parameter missing').to_dict()
-
- # Build request
- params = {
- 'param1': required_param,
- 'param2': optional_param
- }
-
- # Make API call
- result = self._make_request(endpoint, params)
-
- if "error" in result:
- return ProviderError('<endpoint_name>', result['error']).to_dict()
-
- # Process and format response data
- processed_data = self._process_response(result)
-
- return {
- "success": True,
- "endpoint": "<endpoint_name>",
- "data": processed_data,
- "parameters": {
- "required_param": required_param,
- "optional_param": optional_param
- },
- "timestamp": int(datetime.now().timestamp())
- }
-
- except Exception as e:
- return ProviderError('<endpoint_name>', str(e)).to_dict()
-```
-
-#### Composite Method Pattern
-```python
-def get_comprehensive_data(self, symbol: str) -> Dict[str, Any]:
- """Get comprehensive data from multiple endpoints - fails gracefully"""
- result = {
- "success": True,
- "symbol": symbol,
- "timestamp": int(datetime.now().timestamp()),
- "endpoints": {},
- "failed_endpoints": []
- }
-
- # Define endpoints to try
- endpoints = [
- ('quote', lambda: self.get_quote(symbol)),
- ('info', lambda: self.get_info(symbol)),
- ('historical', lambda: self.get_historical(symbol))
- ]
-
- overall_success = False
-
- for endpoint_name, endpoint_func in endpoints:
- try:
- endpoint_result = endpoint_func()
- result["endpoints"][endpoint_name] = endpoint_result
-
- if endpoint_result.get("success"):
- overall_success = True
- else:
- result["failed_endpoints"].append({
- "endpoint": endpoint_name,
- "error": endpoint_result.get("error", "Unknown error")
- })
-
- except Exception as e:
- result["failed_endpoints"].append({
- "endpoint": endpoint_name,
- "error": str(e)
- })
-
- result["success"] = overall_success
- return result
-```
-
-### 6. CLI Interface Pattern
-
-```python
-def main():
- """CLI interface for Provider Data Fetcher"""
- if len(sys.argv) < 2:
- print(json.dumps({
- "error": "Usage: python provider_data.py <command> <args>",
- "available_commands": [
- "quote <symbol>",
- "info <symbol>",
- "historical <symbol> <start_date> <end_date>",
- "comprehensive <symbol>",
- "search <query>"
- ]
- }))
- sys.exit(1)
-
- command = sys.argv[1]
- wrapper = ProviderWrapper()
-
- try:
- if command == "quote":
- if len(sys.argv) < 3:
- print(json.dumps({"error": "Usage: python provider_data.py quote <symbol>"}))
- sys.exit(1)
-
- symbol = sys.argv[2]
- result = wrapper.get_quote(symbol)
- print(json.dumps(result, indent=2))
-
- elif command == "info":
- # Similar pattern for other commands
- pass
-
- else:
- print(json.dumps({
- "error": f"Unknown command: {command}",
- "available_commands": [
- "quote <symbol>",
- "info <symbol>",
- "historical <symbol> <start_date> <end_date>",
- "comprehensive <symbol>",
- "search <query>"
- ]
- }))
- sys.exit(1)
-
- except KeyboardInterrupt:
- print(json.dumps({"error": "Operation cancelled by user"}))
- sys.exit(1)
- except Exception as e:
- print(json.dumps({"error": f"Unexpected error: {str(e)}"}))
- sys.exit(1)
-
-if __name__ == "__main__":
- main()
-```
-
-## Response Format Standards
-
-### Success Response
-```json
-{
- "success": true,
- "endpoint": "endpoint_name",
- "data": [
- {
- "symbol": "AAPL",
- "price": 150.25,
- "change": 1.50,
- "timestamp": 1694918400
- }
- ],
- "parameters": {
- "symbol": "AAPL"
- },
- "metadata": {
- "total_records": 1,
- "source": "Provider API"
- },
- "timestamp": 1694918400
-}
-```
-
-### Error Response
-```json
-{
- "success": false,
- "error": "API rate limit exceeded",
- "endpoint": "quote",
- "status_code": 429,
- "timestamp": 1694918400
-}
-```
-
-## Common Endpoint Types
-
-### 1. Quote/Price Data
-- Real-time or delayed pricing information
-- Volume, change, percentage change
-- High/low/open/close data
-
-### 2. Historical Data
-- Time series data with date ranges
-- OHLCV data for financial instruments
-- Economic indicator historical values
-
-### 3. Company/Entity Information
-- Company profiles, descriptions
-- Sector, industry classifications
-- Market cap, employee counts
-
-### 4. Search/Discovery
-- Symbol lookup by name or ISIN
-- Instrument filtering by criteria
-- Market/sector browsing
-
-### 5. Economic Data
-- GDP, inflation, unemployment rates
-- Central bank data
-- Trade balance, interest rates
-
-## Implementation Guidelines
-
-### Authentication
-- Use environment variables for API keys: `os.environ.get('PROVIDER_API_KEY', '')`
-- Support both API key and bearer token authentication
-- Include API key in session headers for all requests
-
-### Rate Limiting
-- Implement provider-specific rate limits
-- Use time-based throttling when required
-- Track last request time to avoid limits
-
-### Data Normalization
-- Convert all timestamps to Unix timestamps
-- Standardize currency codes (ISO 4217)
-- Normalize country/region codes
-- Handle missing/null values consistently
-
-### Error Handling
-- Catch all exceptions and return structured errors
-- Include HTTP status codes when available
-- Provide meaningful error messages
-- Never let exceptions propagate to CLI
-
-### Date Handling
-- Accept dates in YYYY-MM-DD format
-- Support relative dates (e.g., "1y", "6m")
-- Convert all dates to Unix timestamps in output
-- Handle timezone conversions when needed
-
-## Testing & Validation
-
-### Command-Line Testing
-```bash
-# Test basic functionality
-python provider_data.py quote AAPL
-
-# Test with parameters
-python provider_data.py historical AAPL 2023-01-01 2023-12-31
-
-# Test error handling
-python provider_data.py quote INVALID_SYMBOL
-```
-
-### Expected Output
-- All commands output valid JSON
-- Success responses include "success": true
-- Error responses include "success": false and error details
-- Output is properly formatted with indentation
-
-## Integration with Rust Backend
-
-### Tauri Command Pattern
-```rust
-#[tauri::command]
-pub async fn fetch_provider_data(symbol: String) -> Result<String, String> {
- let output = Command::new("python")
- .arg("resources/scripts/provider_data.py")
- .arg("quote")
- .arg(symbol)
- .output()
- .map_err(|e| e.to_string())?;
-
- let result = String::from_utf8_lossy(&output.stdout).to_string();
- Ok(result)
-}
-```
-
-### Error Propagation
-- Rust should parse JSON responses
-- Handle both success and error cases
-- Log errors appropriately
-- Return user-friendly error messages
-
-## Best Practices
-
-1. **Documentation**: Include comprehensive docstrings for all methods
-2. **Validation**: Validate all input parameters before API calls
-3. **Caching**: Consider local caching for expensive API calls
-4. **Logging**: Add debug logging for troubleshooting (optional)
-5. **Type Hints**: Use proper type hints for all method signatures
-6. **Constants**: Define API URLs and constants at module level
-7. **Dependencies**: Keep external dependencies minimal
-8. **Compatibility**: Ensure Python 3.7+ compatibility
-
-## Example Implementation Template
-
-See existing files for complete examples:
-- `yfinance_data.py` - Basic market data wrapper
-- `alphavantage_data.py` - Advanced wrapper with rate limiting
-- `fred_data.py` - Economic data wrapper
-- `worldbank_data.py` - International data wrapper
-- `imf_data.py` - Complex multi-dataset wrapper
-
-Each new wrapper should follow these patterns while adapting to the specific API's requirements and data structures.
\ No newline at end of file
diff --git a/fincept-terminal-desktop/src/components/tabs/agents/DYNAMIC_CONNECTIONS_SUMMARY.md b/fincept-terminal-desktop/src/components/tabs/agents/DYNAMIC_CONNECTIONS_SUMMARY.md
deleted file mode 100644
index 0b800c122..000000000
--- a/fincept-terminal-desktop/src/components/tabs/agents/DYNAMIC_CONNECTIONS_SUMMARY.md
+++ /dev/null
@@ -1,384 +0,0 @@
-# Dynamic Unlimited Connections - Implementation Complete ✅
-
-## 🎉 Achievement Unlocked: Truly Unlimited Connections!
-
-The Agents Tab now supports **unlimited dynamic connections** with intelligent auto-expansion. Connect 10, 50, 100+ data sources to a single agent!
-
----
-
-## 🚀 What's New
-
-### 1. **Dynamic Handle Generation**
-```
-Before: Fixed 2-3 handles per agent
-After: Unlimited handles that grow with connections
-```
-
-**Algorithm:**
-- Minimum: 2 handles (always shown)
-- Base: Current connections + 1 spare
-- Hover: Expands to show at least 5 handles
-
-### 2. **Real-Time Connection Tracking**
-
-**Visual Badges:**
-```
-📥 [3]/5 ← 3 inputs connected, 5 handles available
-📤 [8]/9 ← 8 outputs connected, 9 handles available
-```
-
-**Badge Features:**
-- ✅ Green/Blue when connected
-- ⚪ Gray when empty
-- 🔄 Updates automatically
-- 📊 Shows capacity utilization
-
-### 3. **Smart Auto-Expand**
-
-**Normal State:**
-```
-Agent with 3 connections
-├─ Shows 4 handles (3 + 1 spare)
-└─ Badge: 📥 3/4
-```
-
-**Hover State:**
-```
-Agent with 3 connections (hovered)
-├─ Shows 5 handles (expanded)
-├─ Badge: 📥 3/5
-└─ Tooltip: "💡 Hover to see more handles"
-```
-
----
-
-## 🎯 Real-World Examples
-
-### Example 1: Multi-Source Data Hub
-```
-Yahoo Finance ─────┐
-Alpha Vantage ─────┤
-Polygon.io ────────┤
-Finnhub ───────────┤
-IEX Cloud ─────────┤
-Twelve Data ───────┼─► Data Aggregator ──► AI Analysis
-Binance ───────────┤ 📥 10/11 📤 1/2
-Coinbase ──────────┤
-CoinGecko ─────────┤
-Kraken ────────────┤
-Marketstack ───────┘
-
-✨ Automatically shows 11 input handles!
-✨ Hover to add more sources instantly!
-```
-
-### Example 2: Portfolio Diversification
-```
- ┌─► Conservative Portfolio
- ├─► Growth Portfolio
- ├─► Value Portfolio
-Warren Buffett Agent ────┼─► Income Portfolio
-📥 2/3 📤 15/16 ├─► Tax-Advantaged Portfolio
- ├─► Retirement Portfolio
- ├─► College Fund
- ├─► Emergency Fund
- ├─► Real Estate Portfolio
- ├─► Crypto Portfolio
- ├─► Commodities Portfolio
- ├─► International Portfolio
- ├─► ESG Portfolio
- ├─► Dividend Portfolio
- └─► Speculative Portfolio
-
-✨ Handles 15 portfolios effortlessly!
-✨ Add more portfolios anytime!
-```
-
-### Example 3: Multi-Strategy Consensus
-```
-Technical Analysis ─────┐
-Fundamental Analysis ───┤
-Sentiment Analysis ─────┤
-Macro Analysis ─────────┤
-News Analysis ──────────┤
-Insider Analysis ───────┤
-Options Flow Analysis ──┼─► Signal Generator ──► Execute
-Volume Profile ─────────┤ 📥 20/21 📤 1/2
-Market Microstructure ──┤
-Order Book Analysis ────┤
-Social Media Analysis ──┤
-... │
-[10 more analysis] ─────┘
-
-✨ Combines 20+ analysis sources!
-✨ Make data-driven decisions!
-```
-
----
-
-## 🔧 Technical Implementation
-
-### Key Code Changes
-
-#### 1. Dynamic Handle Calculation
-```typescript
-// OLD: Static count
-const inputHandleCount = 3; // Fixed!
-
-// NEW: Dynamic based on connections
-const connectedInputs = data.connectedInputs || 0;
-const baseInputHandles = Math.max(2, connectedInputs + 1);
-const inputHandleCount = isHovered
- ? Math.max(baseInputHandles, 5)
- : baseInputHandles;
-```
-
-#### 2. Automatic Connection Tracking
-```typescript
-// Updates all nodes when edges change
-useEffect(() => {
- setNodes(nodes => nodes.map(node => ({
- ...node,
- data: {
- ...node.data,
- connectedInputs: edges.filter(e => e.target === node.id).length,
- connectedOutputs: edges.filter(e => e.source === node.id).length,
- }
- })));
-}, [edges]);
-```
-
-#### 3. Visual Badge System
-```typescript
-// Shows connection status with color coding
-<span style={{
- backgroundColor: connectedInputs > 0 ? '#84cc16' : '#404040',
- color: connectedInputs > 0 ? 'black' : '#737373',
- padding: '2px 6px',
- borderRadius: '3px',
- fontWeight: 'bold',
-}}>
- {connectedInputs}
-</span>
-<span>/{inputHandleCount}</span>
-```
-
----
-
-## 📊 Performance Characteristics
-
-| Connections | Handle Count | Render Time | User Experience |
-|------------|--------------|-------------|-----------------|
-| 0-10 | 2-11 | < 1ms | ⚡ Instant |
-| 10-50 | 11-51 | 1-5ms | ⚡ Excellent |
-| 50-100 | 51-101 | 5-15ms | ✅ Great |
-| 100-200 | 101-201 | 15-30ms | ✅ Good |
-| 200+ | 201+ | 30ms+ | ⚠️ Consider aggregators |
-
-**Memory per handle:** ~100 bytes
-**1000 handles:** ~100 KB total (very efficient!)
-
----
-
-## 🎨 Visual Design
-
-### Handle Distribution Formula
-```typescript
-position = ((index + 1) * 100) / (totalHandles + 1)
-```
-
-**Example with 10 handles:**
-- Handle 0: 9.09% from top
-- Handle 1: 18.18%
-- Handle 2: 27.27%
-- Handle 3: 36.36%
-- Handle 4: 45.45%
-- Handle 5: 54.54% (center)
-- Handle 6: 63.63%
-- Handle 7: 72.72%
-- Handle 8: 81.81%
-- Handle 9: 90.91% from top
-
-Perfectly distributed with smooth transitions!
-
----
-
-## 💡 Usage Tips
-
-### ✅ Best Practices
-
-1. **Organize Visually**
- - Keep connected nodes close
- - Use vertical alignment
- - Minimize line crossing
-
-2. **Use Aggregators for Many Sources**
- ```
- Sources 1-10 → Aggregator A ┐
- Sources 11-20 → Aggregator B ┼→ Main Agent
- Sources 21-30 → Aggregator C ┘
- ```
-
-3. **Hover for Quick Access**
- - Hover to see all available handles
- - Makes connecting new sources easy
- - No scrolling needed
-
-4. **Monitor Capacity**
- - Check connection badges: 📥 15/16
- - Green/blue = actively used
- - Gray = available for use
-
-### ⚠️ When to Split Workflows
-
-- **50-100 connections**: Still optimal
-- **100-200 connections**: Consider splitting
-- **200+ connections**: Definitely split into sub-workflows
-
----
-
-## 📈 Comparison: Before vs After
-
-### Before (Fixed Handles)
-```
-❌ Maximum 3 connections per side
-❌ Limited workflow complexity
-❌ Need multiple intermediate nodes
-❌ Messy workarounds required
-```
-
-### After (Dynamic Handles)
-```
-✅ Unlimited connections
-✅ Clean, scalable workflows
-✅ Direct connections possible
-✅ Automatic handle management
-✅ Visual feedback with badges
-✅ Hover for quick expansion
-```
-
----
-
-## 🔥 Advanced Use Cases Enabled
-
-### 1. Real-Time Market Dashboard
-Connect 50+ market data sources to one monitoring agent
-
-### 2. Multi-Strategy Hedge Fund
-Run 20+ strategies in parallel with automatic aggregation
-
-### 3. Global Sentiment Analysis
-Aggregate news from 100+ sources across all regions
-
-### 4. Comprehensive Risk Assessment
-Combine 30+ risk factors into one risk score
-
-### 5. Portfolio Optimization
-Manage allocations across 50+ asset classes
-
----
-
-## 🛠️ Files Modified
-
-1. **AgentsTab.tsx** (Lines 35-303)
- - Added dynamic handle generation
- - Implemented connection tracking
- - Added visual badges
- - Added hover expansion
-
-2. **Updated Info Bar**
- - New message: "Unlimited connections: Handles auto-expand..."
-
-3. **Documentation Created**
- - UNLIMITED_CONNECTIONS.md
- - DYNAMIC_CONNECTIONS_SUMMARY.md
-
----
-
-## 🎓 Learning Resources
-
-### Quick Start
-1. Add an agent
-2. Connect a data source
-3. Watch the badge update: 📥 1/3
-4. Add more connections
-5. Badges auto-update: 📥 5/6
-6. Hover for even more handles!
-
-### Documentation
-- **README.md** - Basic overview
-- **MULTI_CONNECTION_GUIDE.md** - Connection patterns
-- **UNLIMITED_CONNECTIONS.md** - Deep dive (this is amazing!)
-- **IMPLEMENTATION_SUMMARY.md** - Technical details
-
----
-
-## 🎉 Success Metrics
-
-✅ **Unlimited connections per node**
-✅ **Dynamic handle generation**
-✅ **Real-time connection tracking**
-✅ **Visual capacity indicators**
-✅ **Hover-to-expand functionality**
-✅ **Automatic updates on changes**
-✅ **No TypeScript errors**
-✅ **Smooth performance**
-✅ **Comprehensive documentation**
-
----
-
-## 🚀 What's Next?
-
-### Potential Enhancements
-
-1. **Connection Groups**
- - Bundle related connections
- - Collapse/expand groups
- - Named connection sets
-
-2. **Connection Analytics**
- - Data flow visualization
- - Throughput metrics
- - Bottleneck detection
-
-3. **Smart Suggestions**
- - Recommend aggregator insertion
- - Optimal workflow layout
- - Performance warnings
-
-4. **Connection Templates**
- - Save common patterns
- - Quick-apply to new nodes
- - Share with team
-
----
-
-## 🙌 Acknowledgments
-
-**Problem:** "What if I need to connect 10 data sources?"
-
-**Solution:** Dynamic unlimited connections with intelligent auto-expansion!
-
-**Result:** Build workflows of any complexity with zero artificial limits! 🎯
-
----
-
-## 📞 Support
-
-Having issues or questions?
-
-1. Check the documentation files
-2. Look at the example workflows
-3. Hover over nodes to see available handles
-4. Monitor connection badges for capacity
-5. Use aggregators for super-large workflows
-
----
-
-**🎊 Congratulations! You now have truly unlimited connection capabilities! 🎊**
-
-Build the most sophisticated agent workflows ever created. The only limit is your imagination! 🚀
-
----
-
-*Dynamic Connections System v2.0 - Implemented January 2025*
diff --git a/fincept-terminal-desktop/src/components/tabs/agents/IMPLEMENTATION_SUMMARY.md b/fincept-terminal-desktop/src/components/tabs/agents/IMPLEMENTATION_SUMMARY.md
deleted file mode 100644
index 8d2d124ec..000000000
--- a/fincept-terminal-desktop/src/components/tabs/agents/IMPLEMENTATION_SUMMARY.md
+++ /dev/null
@@ -1,255 +0,0 @@
-# Agents Tab - Multi-Connection Implementation Summary
-
-## ✅ Completed Features
-
-### 1. Multi-Connection Support
-- **Multiple Input Handles**: Each agent can have 2-3 input connection points
-- **Multiple Output Handles**: Each agent can have 2-3 output connection points
-- **Dynamic Handle Count**: Based on agent category
- - Data/Analysis agents: 3 input handles
- - Hedge Fund/Trader agents: 3 output handles
- - Standard agents: 2 input/output handles
-
-### 2. Visual Differentiation
-- **Color-Coded Connections**: Different colors for different data types
- - 🟢 Green (#84cc16) - Data flows from Data agents
- - 🟣 Purple (#8b5cf6) - Analysis outputs
- - 🔵 Blue (#3b82f6) - Trading signals from Trader/Hedge Fund agents
- - 🟢 Green (#10b981) - Execution commands (thicker 3px)
- - 🟠 Orange (#ea580c) - Generic connections
-
-### 3. Connection Labels
-- **Automatic Labels**: Connections show their type
- - 📊 Data - From data agents
- - 📈 Analysis - From analysis agents
- - 💡 Signal - From trader/hedge fund agents
- - ⚡ Execute - From execution agents
-
-### 4. Enhanced Node UI
-- **Connection Count Display**: Shows available inputs/outputs
- - "📥 3 inputs" indicator
- - "📤 3 outputs" indicator
-- **Handle Positioning**: Evenly distributed along node edges
-- **Handle Tooltips**: "Input 1", "Output 2", etc.
-
-### 5. Smart Connection Handling
-- **Unique Connection IDs**: Each connection has unique identifier
-- **Source/Target Validation**: Checks node existence before creating
-- **Category-Based Styling**: Different visual treatment per agent category
-
-## 🎨 Visual Features
-
-### Node Handle Layout
-
-```
-Data Agent (3 inputs, 3 outputs):
- ○ Input 0 (25% from top) Output 0 (25% from top) ○
- ○ Input 1 (50% from top) Output 1 (50% from top) ○
- ○ Input 2 (75% from top) Output 2 (75% from top) ○
-
-Standard Agent (2 inputs, 2 outputs):
- ○ Input 0 (33% from top) Output 0 (33% from top) ○
- ○ Input 1 (66% from top) Output 1 (66% from top) ○
-```
-
-### Connection Styles
-
-| Category | Color | Width | Animated | Label |
-|----------|-------|-------|----------|-------|
-| Data | #84cc16 | 2.5px | Yes | 📊 Data |
-| Analysis | #8b5cf6 | 2.5px | Yes | 📈 Analysis |
-| Signal | #3b82f6 | 2.5px | Yes | 💡 Signal |
-| Execution | #10b981 | 3px | Yes | ⚡ Execute |
-| Default | #ea580c | 2px | Yes | - |
-
-## 📊 Agent Categories & Handle Counts
-
-| Category | Input Handles | Output Handles | Purpose |
-|----------|---------------|----------------|---------|
-| Data | 3 | 3 | Multi-source aggregation |
-| Analysis | 3 | 2 | Complex analysis from multiple inputs |
-| Hedge Fund | 2 | 3 | Strategy signals to multiple destinations |
-| Trader | 2 | 3 | Investment style to multiple portfolios |
-| Execution | 2 | 2 | Signal aggregation and execution |
-| Monitoring | 2 | 2 | Multi-source monitoring |
-
-## 🔧 Technical Implementation
-
-### Key Components
-
-#### 1. AgentNode Component (Updated)
-```typescript
-// Dynamic handle count based on category
-const inputHandleCount = data.category === 'data' || data.category === 'analysis' ? 3 : 2;
-const outputHandleCount = data.category === 'data' || data.category === 'hedge-fund' || data.category === 'trader' ? 3 : 2;
-
-// Multiple handles with dynamic positioning
-Array.from({ length: inputHandleCount }).map((_, index) => {
- const topOffset = ((index + 1) * 100) / (totalHandles + 1);
- return (
- <Handle
- id={`input-${index}`}
- type="target"
- position={Position.Left}
- style={{ top: `${topOffset}%` }}
- />
- );
-});
-```
-
-#### 2. Connection Handler (Enhanced)
-```typescript
-const onConnect = useCallback((params: Connection) => {
- const sourceNode = nodes.find(n => n.id === params.source);
- const targetNode = nodes.find(n => n.id === params.target);
-
- // Category-based styling
- let edgeColor = '#ea580c';
- if (sourceNode.data.category === 'data') edgeColor = '#84cc16';
- if (sourceNode.data.category === 'analysis') edgeColor = '#8b5cf6';
- // ... more categories
-
- const newEdge = {
- ...params,
- id: `edge_${params.source}_${params.sourceHandle}_${params.target}_${params.targetHandle}_${Date.now()}`,
- animated: true,
- style: { stroke: edgeColor, strokeWidth },
- label: '📊 Data', // Dynamic label
- };
-
- setEdges(eds => addEdge(newEdge, eds));
-}, [setEdges, nodes]);
-```
-
-### Files Modified
-
-1. **AgentsTab.tsx** (Lines 76-280)
- - Added multi-handle support
- - Enhanced connection validation
- - Added connection styling
- - Added handle count display
-
-2. **types.ts** (No changes needed)
- - Existing types support multi-connections
-
-3. **agentConfigs.ts** (No changes needed)
- - Agent configs remain unchanged
-
-## 📈 Use Cases Enabled
-
-### 1. Multi-Source Data Aggregation
-```
-Source 1 ──┐
-Source 2 ──┼─► Data Aggregator ──► Analysis
-Source 3 ──┘
-```
-
-### 2. Strategy Diversification
-```
- ┌─► Portfolio 1
-Strategy Agent ─┼─► Portfolio 2
- └─► Portfolio 3
-```
-
-### 3. Parallel Analysis
-```
- ┌─► Technical Analysis ──┐
-Data ───┼─► Fundamental Analysis ─┼─► Signal Generator
- └─► Sentiment Analysis ───┘
-```
-
-### 4. Signal Consensus
-```
-Strategy 1 ──┐
-Strategy 2 ──┼─► Consensus Agent ──► Execution
-Strategy 3 ──┘
-```
-
-## 🎯 Benefits
-
-### For Users
-1. **Flexibility**: Create complex workflows without limitations
-2. **Clarity**: Visual indicators show connection types
-3. **Organization**: Handles are positioned to minimize crossing
-4. **Scalability**: Support for large, complex agent networks
-
-### For Development
-1. **Extensible**: Easy to add more handle configurations
-2. **Type-Safe**: TypeScript ensures correct connections
-3. **Maintainable**: Clean separation of concerns
-4. **Performant**: Efficient rendering with React Flow
-
-## 🚀 Performance Characteristics
-
-- **Handle Rendering**: O(n) where n = handle count per node
-- **Connection Creation**: O(1) per connection
-- **Connection Validation**: O(1) lookup in node array
-- **Visual Updates**: Optimized with React Flow's internal batching
-
-## 🔜 Future Enhancements
-
-### Phase 1 (Immediate)
-- ✅ Multi-connection support
-- ✅ Color-coded connections
-- ✅ Connection labels
-- ✅ Handle positioning
-
-### Phase 2 (Planned)
-- [ ] Connection grouping (bundle related connections)
-- [ ] Connection validation rules
-- [ ] Connection tooltips showing data flow
-- [ ] Connection analytics (data volume, frequency)
-
-### Phase 3 (Advanced)
-- [ ] Dynamic handle addition/removal
-- [ ] Connection load balancing
-- [ ] Connection failover support
-- [ ] Real-time data flow visualization
-
-## 📝 Testing Checklist
-
-- [x] Single connection works
-- [x] Multiple connections from one output
-- [x] Multiple connections to one input
-- [x] Connections have correct colors
-- [x] Connection labels display correctly
-- [x] Handle tooltips show
-- [x] Handle count indicator displays
-- [x] No TypeScript errors
-- [x] Builds successfully
-- [ ] Integration test with real agent execution
-- [ ] Performance test with 100+ nodes
-- [ ] UI/UX test with complex workflows
-
-## 🐛 Known Issues
-
-None currently. All multi-connection features working as expected.
-
-## 💡 Best Practices
-
-1. **Limit connections per handle**: Max 3-5 connections per handle for readability
-2. **Use aggregator agents**: Instead of 10 direct connections, use an aggregator
-3. **Organize spatially**: Keep connected agents close together
-4. **Use colors**: Leverage connection colors for quick workflow understanding
-5. **Label appropriately**: Connection labels help identify data flow
-
-## 📊 Statistics
-
-- **32+ Agents**: All support multi-connection
-- **6 Categories**: Each with optimized handle counts
-- **5 Connection Types**: Each with unique visual style
-- **3 Handle Positions**: Evenly distributed
-- **Unlimited Connections**: No artificial limits imposed
-
-## 🎓 Learning Resources
-
-1. **README.md** - Basic agent tab documentation
-2. **MULTI_CONNECTION_GUIDE.md** - Comprehensive multi-connection guide
-3. **types.ts** - TypeScript type definitions
-4. **agentConfigs.ts** - All 32+ agent configurations
-
----
-
-**Multi-connection support successfully implemented! 🎉**
-
-Users can now create sophisticated agent workflows with parallel processing, data aggregation, and strategy diversification. The visual system makes it easy to understand complex data flows at a glance.
diff --git a/fincept-terminal-desktop/src/components/tabs/agents/MULTI_CONNECTION_GUIDE.md b/fincept-terminal-desktop/src/components/tabs/agents/MULTI_CONNECTION_GUIDE.md
deleted file mode 100644
index 82a3c477a..000000000
--- a/fincept-terminal-desktop/src/components/tabs/agents/MULTI_CONNECTION_GUIDE.md
+++ /dev/null
@@ -1,312 +0,0 @@
-# Multi-Connection Agent System
-
-## Overview
-
-The Agents Tab now supports **multiple simultaneous connections** for both inputs and outputs, allowing you to create complex data pipelines and multi-strategy workflows.
-
-## Connection Capabilities by Agent Category
-
-### 📊 Data Agents (3 inputs, 3 outputs)
-- **Can receive from**: Multiple data sources simultaneously
-- **Can send to**: Multiple analysis/strategy agents
-- **Use case**: Aggregate data from multiple sources and distribute to multiple consumers
-
-```
-Data Source 1 ──┐
-Data Source 2 ──┼─► Data Aggregator ──┬─► Analysis Agent 1
-Data Source 3 ──┘ ├─► Analysis Agent 2
- └─► Analysis Agent 3
-```
-
-### 📈 Analysis Agents (3 inputs, 2 outputs)
-- **Can receive from**: Multiple data agents or other analysis agents
-- **Can send to**: Multiple strategy/execution agents
-- **Use case**: Combine multiple data streams for comprehensive analysis
-
-```
-Market Data ────┐
-News Data ───────┼─► Fundamental Analysis ──┬─► Strategy Agent
-Economic Data ───┘ └─► Risk Assessment
-```
-
-### 💡 Hedge Fund Agents (2 inputs, 3 outputs)
-- **Can receive from**: Data and analysis agents
-- **Can send to**: Multiple execution/monitoring agents
-- **Use case**: Generate signals for multiple portfolio strategies
-
-```
-Technical Data ──┐
-Fundamental ─────┼─► Macro Cycle Agent ──┬─► Portfolio Manager 1
- │ ├─► Portfolio Manager 2
- └─► Signal Generator
-```
-
-### 🎯 Trader Style Agents (2 inputs, 3 outputs)
-- **Can receive from**: Data and analysis agents
-- **Can send to**: Multiple signal generators or portfolio managers
-- **Use case**: Apply legendary investor strategies to multiple portfolios
-
-```
-Financial Data ──┐
-Market Sentiment ┼─► Warren Buffett Agent ──┬─► Long-term Portfolio
- │ ├─► Value Portfolio
- └─► Quality Portfolio
-```
-
-### ⚡ Execution Agents (2 inputs, 2 outputs)
-- **Can receive from**: Multiple strategy agents
-- **Can send to**: Monitoring and portfolio management
-- **Use case**: Aggregate signals from multiple strategies
-
-```
-Strategy 1 ──┐
-Strategy 2 ──┼─► Signal Generator ──┬─► Portfolio Manager
-Strategy 3 ──┘ └─► Alert Monitor
-```
-
-### 🔔 Monitoring Agents (2 inputs, 2 outputs)
-- **Can receive from**: Execution and portfolio agents
-- **Can send to**: Other monitoring or alerting systems
-- **Use case**: Multi-level monitoring and alerting
-
-## Visual Connection Guide
-
-### Connection Colors & Types
-
-| Source Category | Edge Color | Label | Stroke Width | Purpose |
-|----------------|------------|-------|--------------|---------|
-| Data Agents | 🟢 Green (#84cc16) | 📊 Data | 2.5px | Raw data flow |
-| Analysis Agents | 🟣 Purple (#8b5cf6) | 📈 Analysis | 2.5px | Analyzed insights |
-| Trader/Hedge Fund | 🔵 Blue (#3b82f6) | 💡 Signal | 2.5px | Trading signals |
-| Execution Agents | 🟢 Green (#10b981) | ⚡ Execute | 3px | Execution commands |
-| Other | 🟠 Orange (#ea580c) | - | 2px | Generic data flow |
-
-### Handle Positioning
-
-Each agent node displays multiple handles distributed evenly:
-
-```
-INPUT HANDLES (Left Side) OUTPUT HANDLES (Right Side)
- ○ Input 1 Output 1 ○
- ○ Input 2 Output 2 ○
- ○ Input 3 Output 3 ○
-```
-
-The handles are positioned at:
-- **2 handles**: 33%, 66% from top
-- **3 handles**: 25%, 50%, 75% from top
-
-## Example Workflows
-
-### 1. Multi-Source Data Aggregation
-
-```
-Yahoo Finance ──────┐
-Alpha Vantage ──────┼─► Data Aggregator ──► Fundamental Analysis
-Polygon.io ─────────┘
-```
-
-### 2. Multi-Strategy Signal Generation
-
-```
- ┌─► Warren Buffett Agent ─┐
-Market Data ────────┤ ├─► Signal Aggregator ──► Portfolio Manager
- └─► Joel Greenblatt ──────┘
-```
-
-### 3. Hedge Fund Pipeline
-
-```
-Economic Data ──┐
-Market Data ────┼─► Macro Cycle Agent ───┬─► Risk Assessment ──► Portfolio Manager
-News Feed ──────┘ └─► Alert Monitor
-```
-
-### 4. Multi-Level Analysis
-
-```
-Price Data ──┐
-Volume Data ─┼─► Technical Analysis ──┐
-Indicators ──┘ ├─► Signal Generator ──► Execution Agent
- │
-Financials ──┐ │
-Earnings ────┼─► Fundamental Analysis ┘
-Balance Sheet┘
-```
-
-### 5. Diversified Portfolio Strategy
-
-```
- ┌─► Value Portfolio
-Data Collector ──┼─► Growth Portfolio
- ├─► Income Portfolio
- └─► Performance Tracker (monitors all)
-```
-
-## Advanced Patterns
-
-### Fan-Out Pattern (1 → Many)
-One agent distributes data to multiple consumers:
-
-```
-Single Data Source ──► Agent ──┬─► Consumer 1
- ├─► Consumer 2
- └─► Consumer 3
-```
-
-### Fan-In Pattern (Many → 1)
-Multiple sources aggregate into one agent:
-
-```
-Source 1 ──┐
-Source 2 ──┼─► Aggregator ──► Output
-Source 3 ──┘
-```
-
-### Pipeline Pattern
-Sequential processing with multiple stages:
-
-```
-Data ──► Collector ──► Transformer ──► Analyzer ──► Generator ──► Executor
-```
-
-### Diamond Pattern
-Split and rejoin for parallel processing:
-
-```
- ┌─► Fast Analysis ───┐
-Input ──┤ ├─► Combiner ──► Output
- └─► Deep Analysis ────┘
-```
-
-### Hub-and-Spoke Pattern
-Central coordinator with multiple satellites:
-
-```
- ┌─► Specialist 1 ──┐
- ├─► Specialist 2 ──┤
-Hub ───┼─► Specialist 3 ──┼─► Hub ──► Output
- ├─► Specialist 4 ──┤
- └─► Specialist 5 ──┘
-```
-
-## Best Practices
-
-### 1. Connection Organization
-- **Group by purpose**: Keep related agents close together
-- **Color coding**: Use edge colors to identify data flow types
-- **Label connections**: Connection labels show data type
-
-### 2. Performance Optimization
-- **Limit depth**: Keep workflow depth under 6-7 levels
-- **Parallel execution**: Use fan-out for concurrent processing
-- **Caching**: Reuse data from upstream agents when possible
-
-### 3. Workflow Design
-- **Modular design**: Create reusable sub-workflows
-- **Error handling**: Include monitoring agents at critical points
-- **Validation**: Test each connection before full execution
-
-### 4. Connection Limits
-While technically unlimited, recommended maximums:
-- **Data Agents**: Up to 5-6 outputs for distribution
-- **Analysis Agents**: Up to 3-4 inputs for aggregation
-- **Strategy Agents**: Up to 3-4 outputs for diversification
-- **Execution Agents**: Up to 2-3 inputs for signal consensus
-
-## Connection Validation
-
-The system automatically validates:
-- ✅ Source and target nodes exist
-- ✅ Appropriate handle types (source → target)
-- ✅ No self-connections
-- ✅ Unique connection IDs
-
-## Troubleshooting
-
-### Connection Won't Create
-1. **Check handle visibility**: Ensure handles are visible on both nodes
-2. **Verify compatibility**: Some agents may have category restrictions
-3. **Clear existing**: Delete conflicting connections
-
-### Too Many Connections
-1. **Use aggregator agents**: Combine multiple inputs before processing
-2. **Create sub-workflows**: Break complex flows into manageable pieces
-3. **Use fan-in/fan-out**: Organize connections systematically
-
-### Performance Issues
-1. **Reduce connection count**: Limit to essential connections
-2. **Simplify workflow**: Break into smaller workflows
-3. **Use caching**: Enable data caching for repeated queries
-
-## Future Enhancements
-
-### Planned Features
-- [ ] Connection grouping (bundle multiple connections)
-- [ ] Conditional connections (activate based on criteria)
-- [ ] Connection weights (priority/importance)
-- [ ] Connection filters (data transformation on edge)
-- [ ] Connection templates (save common patterns)
-- [ ] Connection validation rules (custom constraints)
-- [ ] Connection analytics (data flow metrics)
-
-### Advanced Capabilities
-- [ ] Dynamic connection routing
-- [ ] Load balancing across connections
-- [ ] Connection failover and redundancy
-- [ ] Real-time connection health monitoring
-- [ ] Connection-level error handling
-
-## API Reference
-
-### Connection Object
-```typescript
-{
- id: string; // Unique connection ID
- source: string; // Source node ID
- sourceHandle: string; // Source handle ID (e.g., "output-0")
- target: string; // Target node ID
- targetHandle: string; // Target handle ID (e.g., "input-1")
- animated: boolean; // Animation state
- style: {
- stroke: string; // Edge color
- strokeWidth: number; // Edge thickness
- };
- label: string; // Connection label
- markerEnd: {
- type: MarkerType; // Arrow type
- color: string; // Arrow color
- };
-}
-```
-
-### Creating Connections Programmatically
-```typescript
-const connection = {
- source: 'agent_1',
- sourceHandle: 'output-0',
- target: 'agent_2',
- targetHandle: 'input-1',
-};
-onConnect(connection);
-```
-
-## Keyboard Shortcuts
-
-- **Delete**: Remove selected connections
-- **Backspace**: Remove selected connections
-- **Ctrl+A**: Select all (nodes and connections)
-- **Ctrl+C**: Copy selected (future feature)
-- **Ctrl+V**: Paste (future feature)
-
-## Tips & Tricks
-
-1. **Visual Organization**: Use different handle positions to avoid crossing connections
-2. **Connection Labels**: Hover over connections to see their type
-3. **Color Coding**: Quickly identify data flow by connection color
-4. **Handle Tooltips**: Hover over handles to see "Input N" or "Output N"
-5. **Multi-Select**: Select multiple nodes to see all their connections highlighted
-
----
-
-*Multi-connection support enables sophisticated agentic workflows with parallel processing, data aggregation, and strategy diversification.*
diff --git a/fincept-terminal-desktop/src/components/tabs/agents/UNLIMITED_CONNECTIONS.md b/fincept-terminal-desktop/src/components/tabs/agents/UNLIMITED_CONNECTIONS.md
deleted file mode 100644
index 83decd2b0..000000000
--- a/fincept-terminal-desktop/src/components/tabs/agents/UNLIMITED_CONNECTIONS.md
+++ /dev/null
@@ -1,428 +0,0 @@
-# Unlimited Dynamic Connections System
-
-## 🚀 Overview
-
-The Agents Tab now supports **truly unlimited connections** with a dynamic handle system that automatically expands based on your needs. No more artificial limits!
-
-## ✨ Key Features
-
-### 1. **Dynamic Handle Generation**
-- Handles automatically appear as you add connections
-- Always shows at least 2 handles per side (minimum)
-- Shows current connections + 1 extra handle for new connections
-- Hover to expand and see up to 5 handles at once
-
-### 2. **Real-Time Connection Tracking**
-- Live badge showing active connections: `📥 3/5`
-- Green badge when connected, gray when empty
-- Automatically updates as you add/remove connections
-
-### 3. **Auto-Expand on Hover**
-- Hover over any agent to see more handles
-- Makes it easy to add new connections
-- Smooth animation and visual feedback
-
-### 4. **No Artificial Limits**
-- Connect 10, 20, 50+ data sources to one agent
-- Fan-out to unlimited downstream consumers
-- System automatically manages handle positioning
-
-## 🎯 How It Works
-
-### Dynamic Handle Algorithm
-
-```typescript
-// Minimum handles shown (always visible)
-const minHandles = 2;
-
-// Base handles = existing connections + 1 spare
-const baseHandles = Math.max(minHandles, currentConnections + 1);
-
-// Expanded handles (on hover) = at least 5
-const expandedHandles = isHovered ? Math.max(baseHandles, 5) : baseHandles;
-```
-
-### Example Scenarios
-
-#### Scenario 1: New Agent (No Connections)
-```
-State: 0 connections
-Display: 2 handles (minimum)
-Badge: 📥 0/2
-
-On Hover: 5 handles
-Badge: 📥 0/5
-```
-
-#### Scenario 2: Few Connections
-```
-State: 3 connections
-Display: 4 handles (3 + 1 spare)
-Badge: 📥 3/4
-
-On Hover: 5 handles
-Badge: 📥 3/5
-```
-
-#### Scenario 3: Many Connections
-```
-State: 10 connections
-Display: 11 handles (10 + 1 spare)
-Badge: 📥 10/11
-
-On Hover: 11 handles (already showing enough)
-Badge: 📥 10/11
-```
-
-## 📊 Visual Indicators
-
-### Connection Count Badges
-
-**Input Badge (Left Side)**
-```
-📥 [3]/5
- └─ Active connections (green if > 0)
- └─ Available handles
-```
-
-**Output Badge (Right Side)**
-```
-📤 [5]/6
- └─ Active connections (blue if > 0)
- └─ Available handles
-```
-
-### Badge Colors
-- **Active (has connections)**:
- - Input: Green background (#84cc16)
- - Output: Blue background (#3b82f6)
-- **Empty (no connections)**:
- - Gray background (#404040)
-
-### Hover Tooltip
-```
-💡 Hover to see more handles
-```
-*Appears when hovering over an agent node*
-
-## 🔥 Real-World Examples
-
-### Example 1: Multi-Source Data Aggregation
-
-```
-Yahoo Finance ────┐
-Alpha Vantage ────┤
-Polygon.io ───────┤
-Finnhub ──────────┼─► Data Aggregator ──► Analysis
-IEX Cloud ────────┤ 📥 5/6 📤 1/2
-Twelve Data ──────┤
-Binance ──────────┤
-CoinGecko ────────┘
-```
-
-The Data Aggregator automatically:
-- Shows 6 input handles (5 connected + 1 spare)
-- Shows 2 output handles (1 connected + 1 spare)
-- Hover reveals up to 8 input handles for more sources
-
-### Example 2: Strategy Diversification
-
-```
- ┌─► Conservative Portfolio
- ├─► Moderate Portfolio
-Warren Buffett ─────┼─► Aggressive Portfolio
-Agent ├─► Retirement Portfolio
-📥 2/3 📤 8/9 ├─► Tax-Advantaged Portfolio
- ├─► Education Portfolio
- ├─► Emergency Fund
- └─► Speculative Portfolio
-```
-
-The Warren Buffett agent automatically:
-- Shows 3 input handles (2 data sources + 1 spare)
-- Shows 9 output handles (8 portfolios + 1 spare)
-- Can easily add more portfolios by hovering
-
-### Example 3: Parallel Analysis Pipeline
-
-```
- ┌─► Technical Analysis ──┐
- ├─► Fundamental Analysis ─┤
- ├─► Sentiment Analysis ───┤
- ├─► Macro Analysis ───────┤
-Data ───┼─► Sector Analysis ──────┼─► Signal Generator ──► Execution
-Source ├─► Risk Analysis ────────┤ 📥 10/11 📤 1/2
- ├─► Correlation Analysis ─┤
- ├─► Volume Analysis ──────┤
- ├─► News Analysis ────────┤
- └─► Insider Analysis ─────┘
-```
-
-The Signal Generator shows:
-- 11 input handles (10 analysis sources + 1 spare)
-- All analysis results feed into one decision
-- Hover to add more analysis sources
-
-## ⚙️ Technical Implementation
-
-### 1. Connection Tracking
-
-```typescript
-// Automatically count connections
-const connectedInputs = edges.filter(edge => edge.target === nodeId).length;
-const connectedOutputs = edges.filter(edge => edge.source === nodeId).length;
-
-// Update node data
-node.data.connectedInputs = connectedInputs;
-node.data.connectedOutputs = connectedOutputs;
-```
-
-### 2. Handle Rendering
-
-```typescript
-// Calculate dynamic handle count
-const inputHandleCount = Math.max(2, connectedInputs + 1);
-const outputHandleCount = Math.max(2, connectedOutputs + 1);
-
-// Expand on hover
-if (isHovered) {
- inputHandleCount = Math.max(inputHandleCount, 5);
- outputHandleCount = Math.max(outputHandleCount, 5);
-}
-
-// Render handles
-Array.from({ length: inputHandleCount }).map((_, index) => {
- const position = ((index + 1) * 100) / (inputHandleCount + 1);
- return <Handle key={index} top={`${position}%`} />;
-});
-```
-
-### 3. Automatic Updates
-
-```typescript
-// Update counts whenever edges change
-useEffect(() => {
- setNodes(nodes => nodes.map(node => ({
- ...node,
- data: {
- ...node.data,
- connectedInputs: edges.filter(e => e.target === node.id).length,
- connectedOutputs: edges.filter(e => e.source === node.id).length,
- }
- })));
-}, [edges]);
-```
-
-## 🎨 Visual Design
-
-### Handle Distribution
-
-Handles are evenly distributed using the formula:
-```
-position = ((index + 1) * 100) / (totalHandles + 1)
-```
-
-**Example with 5 handles:**
-- Handle 0: 16.67% from top
-- Handle 1: 33.33% from top
-- Handle 2: 50.00% from top (center)
-- Handle 3: 66.67% from top
-- Handle 4: 83.33% from top
-
-### Smooth Transitions
-
-All handle changes are animated:
-```css
-transition: all 0.2s ease-in-out;
-```
-
-## 💡 Best Practices
-
-### 1. **Organizing Many Connections**
-
-❌ **Bad**: Direct connections from 20 sources
-```
-Source 1 ──┐
-Source 2 ──┤
-... ├─► Analysis Agent (messy!)
-Source 19 ─┤
-Source 20 ─┘
-```
-
-✅ **Good**: Use aggregator nodes
-```
-Sources 1-10 ──► Aggregator A ──┐
-Sources 11-20 ─► Aggregator B ──┼─► Analysis Agent (clean!)
- │
-```
-
-### 2. **Visual Clarity**
-
-- **Keep related nodes close**: Minimize line crossing
-- **Use vertical spacing**: Stack nodes to align handles
-- **Color coding**: Connection colors show data types
-- **Labels**: Connection labels identify data flow
-
-### 3. **Performance Tips**
-
-- **Under 50 connections per node**: Optimal performance
-- **50-100 connections**: Still good, may need scrolling
-- **100+ connections**: Consider splitting workflows
-
-### 4. **Workflow Design**
-
-**Fan-Out (1 → Many)**
-```
-Single Source ──► Hub ──┬─► Consumer 1
- ├─► Consumer 2
- ├─► Consumer 3
- └─► ... Consumer N
-```
-
-**Fan-In (Many → 1)**
-```
-Source 1 ──┐
-Source 2 ──┤
-Source 3 ──┼─► Aggregator ──► Output
-... │
-Source N ──┘
-```
-
-**Hybrid (Many → Many)**
-```
-Source 1 ──┐ ┌─► Consumer 1
-Source 2 ──┼─► Router ───┼─► Consumer 2
-Source 3 ──┘ └─► Consumer 3
-```
-
-## 🔧 Advanced Features
-
-### Connection Limits (Optional)
-
-While technically unlimited, you can add soft limits:
-
-```typescript
-const MAX_RECOMMENDED_CONNECTIONS = 50;
-
-if (connectedInputs > MAX_RECOMMENDED_CONNECTIONS) {
- showWarning("Consider using aggregator nodes for better organization");
-}
-```
-
-### Connection Analytics
-
-Track connection metrics:
-
-```typescript
-{
- nodeId: 'agent_123',
- totalConnections: 25,
- inputConnections: 10,
- outputConnections: 15,
- utilizationRate: 0.625, // 25/40 available handles
- lastConnectionTime: '2025-01-15T10:30:00Z'
-}
-```
-
-### Bulk Connection Operations
-
-Connect multiple sources at once:
-
-```typescript
-function connectMultipleSources(sources: string[], target: string) {
- sources.forEach((source, index) => {
- onConnect({
- source: source,
- sourceHandle: `output-0`,
- target: target,
- targetHandle: `input-${index}`
- });
- });
-}
-```
-
-## 📈 Performance Characteristics
-
-### Rendering Performance
-
-| Connections | Handle Render Time | Update Time | User Experience |
-|-------------|-------------------|-------------|-----------------|
-| 0-10 | < 1ms | Instant | Excellent |
-| 10-50 | 1-5ms | < 10ms | Excellent |
-| 50-100 | 5-15ms | 10-50ms | Good |
-| 100-200 | 15-30ms | 50-100ms | Acceptable |
-| 200+ | 30ms+ | 100ms+ | Consider optimization |
-
-### Memory Usage
-
-- **Per handle**: ~100 bytes
-- **100 handles**: ~10 KB
-- **1000 handles**: ~100 KB (across all nodes)
-
-Very efficient even with large workflows!
-
-## 🐛 Troubleshooting
-
-### Issue: Handles overlap with many connections
-
-**Solution**:
-- Use vertical layout to spread nodes apart
-- Hover to access specific handles
-- Consider using aggregator nodes
-
-### Issue: Can't find the right handle
-
-**Solution**:
-- Hover over agent to expand handles
-- Use minimap to zoom out and see structure
-- Connection badges show current usage
-
-### Issue: Performance degradation with 200+ connections
-
-**Solution**:
-- Split workflow into sub-workflows
-- Use aggregator pattern (group connections)
-- Enable workflow optimization features
-
-## 📚 API Reference
-
-### Node Data Structure
-
-```typescript
-interface AgentNodeData {
- // ... other properties
- connectedInputs: number; // Current input connections
- connectedOutputs: number; // Current output connections
-}
-```
-
-### Connection Event
-
-```typescript
-onConnect(params: {
- source: string; // Source node ID
- sourceHandle: string; // Source handle ID
- target: string; // Target node ID
- targetHandle: string; // Target handle ID
-})
-```
-
-### Update Connection Counts
-
-```typescript
-updateConnectionCounts(): void
-// Automatically called when edges change
-// Updates all nodes with current connection counts
-```
-
-## 🎓 Learn More
-
-- **README.md** - Basic agents tab overview
-- **MULTI_CONNECTION_GUIDE.md** - Connection patterns and examples
-- **IMPLEMENTATION_SUMMARY.md** - Technical implementation details
-
----
-
-**Unlimited connections = Unlimited possibilities! 🚀**
-
-Build sophisticated data pipelines with as many connections as you need. The system automatically adapts to your workflow complexity.
diff --git a/fincept-terminal-desktop/src/components/tabs/data-mapping/AUTH_INTEGRATION.md b/fincept-terminal-desktop/src/components/tabs/data-mapping/AUTH_INTEGRATION.md
deleted file mode 100644
index 36acfab4b..000000000
--- a/fincept-terminal-desktop/src/components/tabs/data-mapping/AUTH_INTEGRATION.md
+++ /dev/null
@@ -1,329 +0,0 @@
-# Authentication Integration Strategy
-
-## Overview
-
-The Data Mapping system **does NOT handle authentication directly**. Instead, it leverages your existing **Data Sources** connections that already have authentication configured.
-
-## Architecture Flow
-
-```
-┌──────────────────────────────────────────────────────────────────┐
-│ DATA SOURCE CONNECTION │
-│ (Already configured in Data Sources tab) │
-│ │
-│ Connection ID: "conn_upstox_123" │
-│ Type: "upstox" │
-│ Config: │
-│ - apiKey: "xyz123..." │
-│ - apiSecret: "secret..." │
-│ - redirectUrl: "..." │
-│ - accessToken: "..." (after OAuth flow) │
-│ │
-│ Status: CONNECTED ✓ │
-└──────────────────────────────────────────────────────────────────┘
- ↓
- │ References connection
- ↓
-┌──────────────────────────────────────────────────────────────────┐
-│ DATA MAPPING CONFIG │
-│ │
-│ Mapping ID: "map_upstox_ohlcv" │
-│ Name: "Upstox Historical Candles → OHLCV" │
-│ │
-│ Source: │
-│ connectionId: "conn_upstox_123" ← References connection │
-│ endpoint: "/historical-candle/{symbol}/day/{from}/{to}" │
-│ method: "GET" │
-│ │
-│ Target: │
-│ schema: "OHLCV" │
-│ │
-│ Mappings: [...] │
-└──────────────────────────────────────────────────────────────────┘
- ↓
- │ Uses connection to fetch data
- ↓
-┌──────────────────────────────────────────────────────────────────┐
-│ MAPPING EXECUTION ENGINE │
-│ │
-│ 1. Load connection: getConnection("conn_upstox_123") │
-│ 2. Get adapter: UpstoxAdapter(connection) │
-│ 3. Build request: │
-│ - URL: endpoint + parameters │
-│ - Headers: Authorization from connection.config │
-│ 4. Execute request via adapter │
-│ 5. Receive raw response │
-│ 6. Apply mapping transformations │
-│ 7. Return unified data │
-└──────────────────────────────────────────────────────────────────┘
-```
-
-## Implementation Details
-
-### 1. Connection Selection in UI
-
-When creating a mapping, users select from existing connections:
-
-```typescript
-// In DataMappingTab.tsx
-function ConnectionSelector({ onSelect }: Props) {
- const connections = useDataSourceConnections(); // From existing data-sources
-
- return (
- <select onChange={(e) => onSelect(e.target.value)}>
- {connections.map(conn => (
- <option key={conn.id} value={conn.id}>
- {conn.name} ({conn.type}) - {conn.status}
- </option>
- ))}
- </select>
- );
-}
-```
-
-### 2. Fetching Sample Data
-
-During mapping creation, we need sample data. The system fetches it using the connection:
-
-```typescript
-// In MappingEngine.ts
-async fetchSampleData(
- connection: DataSourceConnection,
- endpoint: string,
- params: Record<string, any>
-): Promise<any> {
- // Get the adapter for this connection type
- const adapter = createAdapter(connection);
-
- if (!adapter) {
- throw new Error(`No adapter for ${connection.type}`);
- }
-
- // Build the request
- const request = {
- endpoint,
- method: 'GET',
- params,
- };
-
- // Execute via adapter (handles auth automatically)
- const response = await adapter.executeRequest(request);
-
- return response.data;
-}
-```
-
-### 3. Runtime Execution
-
-When a chart or analysis needs data, it requests mapped data:
-
-```typescript
-// Usage in other components
-const mappingEngine = new MappingEngine();
-
-const data = await mappingEngine.execute({
- mappingId: 'map_upstox_ohlcv',
- parameters: {
- symbol: 'SBIN',
- from: '2024-01-01',
- to: '2024-10-01'
- }
-});
-
-// Returns: [{ symbol, timestamp, open, high, low, close, volume }, ...]
-```
-
-## Broker-Specific Authentication
-
-### Upstox Example
-
-```typescript
-// Connection configuration (already in data-sources)
-const upstoxConnection: DataSourceConnection = {
- id: 'conn_upstox_123',
- type: 'upstox',
- config: {
- apiKey: 'xyz123',
- apiSecret: 'secret123',
- redirectUrl: 'http://localhost:1420/callback',
- accessToken: 'Bearer eyJ...', // Obtained via OAuth
- refreshToken: '...',
- },
- status: 'connected'
-};
-
-// The UpstoxAdapter handles authentication
-class UpstoxAdapter extends BaseAdapter {
- async executeRequest(request: any): Promise<any> {
- const headers = {
- 'Authorization': this.connection.config.accessToken,
- 'Accept': 'application/json'
- };
-
- const response = await fetch(
- `https://api.upstox.com/v2${request.endpoint}`,
- { headers, method: request.method }
- );
-
- return await response.json();
- }
-}
-```
-
-### Fyers Example
-
-```typescript
-// Fyers uses API key + access token
-const fyersConnection: DataSourceConnection = {
- id: 'conn_fyers_456',
- type: 'fyers',
- config: {
- appId: 'ABC123',
- apiSecret: 'secret456',
- accessToken: 'fyers_access_token_xyz',
- },
- status: 'connected'
-};
-
-class FyersAdapter extends BaseAdapter {
- async executeRequest(request: any): Promise<any> {
- const headers = {
- 'Authorization': `${this.connection.config.appId}:${this.connection.config.accessToken}`,
- };
-
- const response = await fetch(
- `https://api.fyers.in${request.endpoint}`,
- { headers }
- );
-
- return await response.json();
- }
-}
-```
-
-## Storage & Security
-
-### Where Auth Data is Stored
-
-```
-DuckDB Tables:
-├── data_source_connections
-│ ├── id (primary key)
-│ ├── type
-│ ├── config (ENCRYPTED JSON with credentials)
-│ └── status
-│
-└── data_mappings
- ├── id (primary key)
- ├── connection_id (foreign key → data_source_connections.id)
- ├── mapping_config (JSON)
- └── metadata
-```
-
-### Security Best Practices
-
-1. **Credentials Encryption**: All API keys/secrets stored encrypted in DuckDB
-2. **No Plaintext**: Never log credentials in console
-3. **Token Refresh**: Adapters handle OAuth token refresh automatically
-4. **Session Management**: Expired tokens trigger re-authentication flow
-5. **Sandboxing**: Custom JS expressions run in sandboxed VM
-
-## Endpoint Management
-
-### How Users Specify Endpoints
-
-```typescript
-// Option 1: Manual entry
-mapping.source.endpoint = "/historical-candle/{symbol}/day/{from}/{to}";
-
-// Option 2: Select from pre-defined endpoints
-const UPSTOX_ENDPOINTS = {
- historicalCandles: {
- path: '/historical-candle/{symbol}/{interval}/{from}/{to}',
- method: 'GET',
- parameters: [
- { name: 'symbol', type: 'string', required: true, location: 'path' },
- { name: 'interval', type: 'string', required: true, location: 'path' },
- { name: 'from', type: 'date', required: true, location: 'path' },
- { name: 'to', type: 'date', required: true, location: 'path' },
- ],
- authentication: { type: 'bearer', location: 'header' }
- },
- getProfile: {
- path: '/user/profile',
- method: 'GET',
- parameters: [],
- authentication: { type: 'bearer', location: 'header' }
- }
-};
-```
-
-### Dynamic Parameter Substitution
-
-```typescript
-// User specifies:
-endpoint: "/historical-candle/{symbol}/day/{from}/{to}"
-parameters: { symbol: "SBIN", from: "2024-01-01", to: "2024-10-01" }
-
-// Engine substitutes:
-finalUrl: "/historical-candle/SBIN/day/2024-01-01/2024-10-01"
-```
-
-## Testing Flow
-
-### In Mapping Creation UI
-
-1. User selects connection: "Upstox Production"
-2. System checks connection status (must be CONNECTED)
-3. User enters or selects endpoint
-4. User provides test parameters (symbol, dates, etc.)
-5. Click "Fetch Sample Data"
-6. System:
- - Gets adapter for connection
- - Builds authenticated request
- - Executes request
- - Returns raw JSON
-7. User sees raw JSON in JSON Explorer
-8. User creates field mappings visually
-9. System shows live preview of transformed data
-10. User tests with different parameters
-11. Save mapping
-
-## Error Handling
-
-### Connection Errors
-
-```typescript
-try {
- const data = await mappingEngine.execute({ mappingId, parameters });
-} catch (error) {
- if (error.code === 'AUTH_FAILED') {
- // Connection auth expired
- showNotification('Please reconnect your data source');
- redirectToDataSources();
- } else if (error.code === 'CONNECTION_NOT_FOUND') {
- showError('Data source connection deleted');
- } else if (error.code === 'RATE_LIMIT') {
- showWarning('API rate limit exceeded. Retry in 1 minute');
- }
-}
-```
-
-## Benefits of This Approach
-
-✅ **Separation of Concerns**: Auth handled by data-sources, mapping handles transformation
-✅ **Reusability**: One connection can power multiple mappings
-✅ **Security**: Credentials stored centrally with encryption
-✅ **Maintainability**: Auth logic in adapters, not scattered in mapping code
-✅ **Flexibility**: Easy to add new data sources without changing mapping system
-✅ **User-Friendly**: Users don't re-enter credentials for each mapping
-
-## Next Steps
-
-When implementing, we'll:
-
-1. Create `ConnectionService` to query existing connections
-2. Extend adapters with `executeRequest(endpoint, params)` method
-3. Build UI components to select connections and test endpoints
-4. Add parameter substitution logic
-5. Implement error handling for auth failures
diff --git a/fincept-terminal-desktop/src/components/tabs/data-mapping/COMPLETED.md b/fincept-terminal-desktop/src/components/tabs/data-mapping/COMPLETED.md
deleted file mode 100644
index 4856d6ae4..000000000
--- a/fincept-terminal-desktop/src/components/tabs/data-mapping/COMPLETED.md
+++ /dev/null
@@ -1,390 +0,0 @@
-# 🎉 DATA MAPPING SYSTEM - COMPLETED!
-
-## ✅ 100% COMPLETE - READY FOR USE
-
-**Status:** Production-ready transformation engine with full UI
-**Date Completed:** 2024
-**Total Files Created:** 30+
-
----
-
-## 📂 Complete File Structure
-
-```
-src/components/tabs/data-mapping/
-│
-├── DataMappingTab.tsx ✅ Main tab component (step-by-step wizard)
-├── index.ts ✅ Main exports
-├── types.ts ✅ All TypeScript interfaces
-│
-├── README.md ✅ Complete documentation
-├── AUTH_INTEGRATION.md ✅ Authentication strategy
-├── PROGRESS.md ✅ Development progress
-├── COMPLETED.md ✅ This file
-│
-├── schemas/
-│ ├── index.ts ✅ 7 unified schemas (OHLCV, QUOTE, ORDER, etc.)
-│ └── validators.ts (Future: Advanced validators)
-│
-├── engine/
-│ ├── MappingEngine.ts ✅ Core transformation engine
-│ │
-│ └── parsers/
-│ ├── index.ts ✅ Parser registry & auto-detection
-│ ├── BaseParser.ts ✅ Abstract base class
-│ ├── JSONPathParser.ts ✅ JSONPath queries ($.data.field[*])
-│ ├── JSONataParser.ts ✅ Powerful transformations
-│ ├── JMESPathParser.ts ✅ AWS-style queries
-│ ├── DirectParser.ts ✅ Simple object access
-│ └── JavaScriptParser.ts ✅ Sandboxed JS execution
-│
-├── components/
-│ ├── JSONExplorer.tsx ✅ Interactive JSON tree viewer
-│ ├── ExpressionBuilder.tsx ✅ Build & test expressions
-│ ├── LivePreview.tsx ✅ Real-time preview
-│ ├── SchemaSelector.tsx ✅ Choose target schema
-│ ├── ConnectionSelector.tsx ✅ Select data source
-│ └── TemplateLibrary.tsx ✅ Pre-built templates
-│
-├── services/
-│ ├── ConnectionService.ts ✅ Data source integration
-│ └── MappingStorage.ts ✅ Save/load mappings (localStorage)
-│
-├── templates/
-│ └── indian-brokers.ts ✅ Upstox, Fyers, Dhan, Zerodha (6 templates)
-│
-└── utils/
- └── transformFunctions.ts ✅ 22 transformation functions
-```
-
----
-
-## 🚀 Key Features Implemented
-
-### Core Transformation Engine
-- ✅ **5 Parser Engines**: JSONPath, JSONata, JMESPath, Direct, JavaScript
-- ✅ **22 Transform Functions**: Type conversion, date/time, math, string, financial
-- ✅ **7 Unified Schemas**: OHLCV, QUOTE, TICK, ORDER, POSITION, PORTFOLIO, INSTRUMENT
-- ✅ **Post-Processing**: Filter, sort, limit, deduplicate
-- ✅ **Validation**: Schema validation with detailed error messages
-- ✅ **Error Handling**: Comprehensive error handling & fallbacks
-
-### User Interface
-- ✅ **Step-by-Step Wizard**: 6-step mapping creation flow
-- ✅ **Template Library**: Pre-built mappings for Indian brokers
-- ✅ **JSON Explorer**: Interactive tree viewer with copy & generate
-- ✅ **Expression Builder**: Live testing with syntax help
-- ✅ **Live Preview**: Real-time transformation results
-- ✅ **Schema Selector**: Browse and select target schemas
-- ✅ **Connection Selector**: Choose from existing data sources
-
-### Authentication & Security
-- ✅ **Connection-Based Auth**: Uses existing data source connections
-- ✅ **No Credential Re-entry**: Mappings reference connections
-- ✅ **Sandboxed Execution**: Safe JavaScript execution
-- ✅ **Input Validation**: Prevents dangerous operations
-
-### Templates
-- ✅ **Upstox**: Historical candles, Market quotes
-- ✅ **Fyers**: Quotes, Positions
-- ✅ **Dhan**: Positions, Orders
-- ✅ **Zerodha**: OHLC data
-
-### Storage & Persistence
-- ✅ **LocalStorage Fallback**: Save/load mappings
-- ✅ **Import/Export**: JSON import/export
-- ✅ **Duplicate**: Clone existing mappings
-- 🔄 **DuckDB Integration**: Ready for implementation (stub created)
-
----
-
-## 💡 How to Use
-
-### 1. Import in Your App
-
-```typescript
-// Import the main tab component
-import DataMappingTab from './components/tabs/data-mapping';
-
-// Add to your tab system
-<DataMappingTab />
-```
-
-### 2. Create a Mapping (UI Flow)
-
-```
-Step 1: Choose Template (or skip)
- → Browse Indian broker templates
- → Select Upstox Historical → OHLCV
-
-Step 2: Select Connection
- → Choose existing Upstox connection
- → Must be "connected" status
-
-Step 3: Choose Schema
- → Select target: OHLCV
- → Preview required fields
-
-Step 4: Provide Sample Data
- → Paste sample API response
- → Or fetch from endpoint
-
-Step 5: Configure Mapping
- → Set extraction expression
- → Map each field
- → Add transformations
-
-Step 6: Test & Save
- → Run test with sample data
- → Verify output
- → Save mapping
-```
-
-### 3. Use Mapping Programmatically
-
-```typescript
-import { mappingEngine } from './components/tabs/data-mapping';
-
-// Execute a saved mapping
-const result = await mappingEngine.execute({
- mapping: loadedMapping,
- parameters: {
- symbol: 'SBIN',
- from: '2024-01-01',
- to: '2024-10-01'
- }
-});
-
-if (result.success) {
- console.log('Transformed data:', result.data);
- // Use standardized OHLCV data in charts, analytics, etc.
-}
-```
-
----
-
-## 📊 System Statistics
-
-| Category | Count | Status |
-|----------|-------|--------|
-| **Core Files** | 15 | ✅ Complete |
-| **UI Components** | 6 | ✅ Complete |
-| **Parser Engines** | 5 | ✅ Complete |
-| **Transform Functions** | 22 | ✅ Complete |
-| **Unified Schemas** | 7 | ✅ Complete |
-| **Templates** | 6 | ✅ Complete |
-| **Services** | 2 | ✅ Complete |
-| **Documentation** | 4 | ✅ Complete |
-| **Total Lines of Code** | ~5000+ | ✅ Complete |
-
----
-
-## 🎯 What You Can Do Now
-
-### Transform Any Financial Data
-```typescript
-// Upstox → Standard OHLCV
-Upstox Response (array of arrays)
- → Parse with JSONata
- → Map to unified OHLCV
- → Validate against schema
- → Output: [{ symbol, timestamp, open, high, low, close, volume }]
-
-// Fyers → Standard QUOTE
-Fyers Response (nested object)
- → Parse with JSONPath
- → Extract nested fields
- → Transform timestamps
- → Output: { symbol, price, bid, ask, volume, ... }
-
-// Any Broker → Any Schema
-Your API → Choose Parser → Map Fields → Get Standard Data
-```
-
-### Reuse Across Components
-```typescript
-// In Chart Component
-const ohlcData = await fetchMappedData('map_upstox_ohlcv', { symbol: 'AAPL' });
-renderCandlestickChart(ohlcData);
-
-// In Analytics Component
-const positions = await fetchMappedData('map_fyers_positions');
-calculatePortfolioMetrics(positions);
-
-// In Dashboard Component
-const quotes = await fetchMappedData('map_dhan_quotes', { symbols: ['SBIN', 'RELIANCE'] });
-updateLiveTicker(quotes);
-```
-
----
-
-## 🔧 Configuration Examples
-
-### Example 1: Upstox Historical Candles
-
-```json
-{
- "name": "Upstox → OHLCV",
- "source": {
- "connectionId": "conn_upstox_123",
- "endpoint": "/historical-candle/{symbol}/day/{from}/{to}"
- },
- "target": {
- "schema": "OHLCV"
- },
- "extraction": {
- "engine": "jsonata",
- "rootPath": "data.candles"
- },
- "fieldMappings": [
- { "targetField": "timestamp", "sourceExpression": "$[0]", "transform": "toISODate" },
- { "targetField": "open", "sourceExpression": "$[1]" },
- { "targetField": "high", "sourceExpression": "$[2]" },
- { "targetField": "low", "sourceExpression": "$[3]" },
- { "targetField": "close", "sourceExpression": "$[4]" },
- { "targetField": "volume", "sourceExpression": "$[5]" }
- ]
-}
-```
-
-### Example 2: Fyers Quotes
-
-```json
-{
- "name": "Fyers → QUOTE",
- "source": {
- "connectionId": "conn_fyers_456",
- "endpoint": "/quotes/"
- },
- "target": {
- "schema": "QUOTE"
- },
- "extraction": {
- "engine": "jsonata",
- "rootPath": "d"
- },
- "fieldMappings": [
- { "targetField": "symbol", "sourceExpression": "n" },
- { "targetField": "price", "sourceExpression": "v.lp" },
- { "targetField": "bid", "sourceExpression": "v.spread.bid" },
- { "targetField": "ask", "sourceExpression": "v.spread.ask" },
- { "targetField": "volume", "sourceExpression": "v.volume" }
- ]
-}
-```
-
----
-
-## 🎨 UI Screenshots (Conceptual)
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│ DATA MAPPING [TEMPLATES] [CREATE] [MY MAPS] │
-├─────────────────────────────────────────────────────────────────┤
-│ │
-│ ┌─────────────────┐ ┌──────────────────────┐ ┌────────────┐ │
-│ │ Template │ │ Mapping Wizard │ │ Preview │ │
-│ │ Library │ │ │ │ │ │
-│ │ │ │ Step 1: Template │ │ Input: │ │
-│ │ • Upstox │ │ [Browse templates] │ │ {...} │ │
-│ │ • Fyers │ │ │ │ │ │
-│ │ • Dhan │ │ Step 2: Connection │ │ ↓ │ │
-│ │ • Zerodha │ │ [Select source] │ │ │ │
-│ │ │ │ │ │ Output: │ │
-│ │ [Search...] │ │ Step 3: Schema │ │ [{...}] │ │
-│ │ │ │ [Choose OHLCV] │ │ │ │
-│ └─────────────────┘ └──────────────────────┘ └────────────┘ │
-│ │
-└─────────────────────────────────────────────────────────────────┘
-```
-
----
-
-## 🚦 Production Readiness Checklist
-
-- ✅ **Core Engine**: Fully functional transformation pipeline
-- ✅ **Parser System**: 5 production-ready parsers
-- ✅ **UI Components**: Complete step-by-step wizard
-- ✅ **Templates**: 6 broker templates ready to use
-- ✅ **Error Handling**: Comprehensive error messages
-- ✅ **Validation**: Schema validation implemented
-- ✅ **Documentation**: Complete README & guides
-- ✅ **Type Safety**: Full TypeScript coverage
-- ⚠️ **Storage**: LocalStorage fallback (DuckDB stub ready)
-- ⚠️ **Testing**: Manual testing done (unit tests recommended)
-
----
-
-## 📚 Next Steps (Optional Enhancements)
-
-### Short-term
-1. **DuckDB Integration**: Replace localStorage with DuckDB
-2. **More Templates**: Add Angel One, Groww, 5Paisa
-3. **Drag-Drop Mapper**: Visual field connection UI
-4. **AI Suggestions**: Auto-detect field mappings
-
-### Long-term
-5. **Multi-Source Mapping**: Combine data from multiple sources
-6. **Scheduled Refresh**: Auto-update mapped data
-7. **Caching Layer**: Cache transformed data
-8. **Version Control**: Track mapping changes
-9. **Sharing**: Export/import mappings between users
-10. **Monitoring**: Usage analytics & performance metrics
-
----
-
-## 🎓 Learning Resources
-
-### For Developers
-- **JSONPath Tutorial**: https://goessner.net/articles/JsonPath/
-- **JSONata Playground**: https://try.jsonata.org/
-- **JMESPath Tutorial**: https://jmespath.org/tutorial.html
-
-### For Users
-- See `README.md` for complete guide
-- See `AUTH_INTEGRATION.md` for connection setup
-- Check templates in `templates/indian-brokers.ts` for examples
-
----
-
-## 🏆 Achievement Summary
-
-**What We Built:**
-- ✅ State-of-the-art JSON transformation engine
-- ✅ Bloomberg-style professional UI
-- ✅ Production-ready for Indian brokers
-- ✅ Extensible architecture for future growth
-- ✅ Type-safe with full TypeScript
-- ✅ Well-documented & maintainable
-
-**Impact:**
-- 🎯 **Universal Data Adapter**: Connect any broker, normalize to standard format
-- 🚀 **Developer-Friendly**: Simple API, powerful capabilities
-- 💼 **Business Value**: Support unlimited data sources without code changes
-- 🔧 **Maintainable**: Clean architecture, extensive documentation
-
----
-
-## 🎉 CONGRATULATIONS!
-
-You now have a **complete, production-ready data mapping system** that can:
-- Transform data from any broker (Upstox, Fyers, Dhan, Zerodha, etc.)
-- Normalize to unified schemas (OHLCV, QUOTE, ORDER, POSITION, etc.)
-- Handle complex nested JSON with 5 powerful parsers
-- Apply 22 transformation functions
-- Validate against schemas
-- Provide beautiful UI for configuration
-
-**The system is ready to use in your Fincept Terminal!** 🚀
-
----
-
-## 📞 Support
-
-For questions or issues:
-1. Check `README.md` for documentation
-2. Review `AUTH_INTEGRATION.md` for connection setup
-3. See template examples in `templates/indian-brokers.ts`
-4. Inspect types in `types.ts` for API reference
-
-**Happy Mapping!** 🎊
diff --git a/fincept-terminal-desktop/src/components/tabs/data-mapping/PROGRESS.md b/fincept-terminal-desktop/src/components/tabs/data-mapping/PROGRESS.md
deleted file mode 100644
index 1d8af0c37..000000000
--- a/fincept-terminal-desktop/src/components/tabs/data-mapping/PROGRESS.md
+++ /dev/null
@@ -1,230 +0,0 @@
-# Data Mapping System - Implementation Progress
-
-## ✅ COMPLETED (Core Engine & Infrastructure)
-
-### 1. Type System & Schemas
-- [x] `types.ts` - All TypeScript interfaces (ParserEngine, FieldMapping, DataMappingConfig, etc.)
-- [x] `schemas/index.ts` - 7 unified schemas (OHLCV, QUOTE, TICK, ORDER, POSITION, PORTFOLIO, INSTRUMENT)
-
-### 2. Parser Engine (5 parsers implemented)
-- [x] `engine/parsers/BaseParser.ts` - Abstract base class
-- [x] `engine/parsers/JSONPathParser.ts` - JSONPath queries ($.data.field[*])
-- [x] `engine/parsers/JSONataParser.ts` - Powerful transformations
-- [x] `engine/parsers/JMESPathParser.ts` - AWS-style queries
-- [x] `engine/parsers/DirectParser.ts` - Simple object access
-- [x] `engine/parsers/JavaScriptParser.ts` - Sandboxed JS execution
-- [x] `engine/parsers/index.ts` - Parser registry & auto-detection
-
-### 3. Transformation System
-- [x] `utils/transformFunctions.ts` - 22 transformation functions:
- - Type conversions (toNumber, toString, toBoolean)
- - Date/time (toISODate, fromUnixTimestamp, toUnixTimestamp, etc.)
- - Math (round, multiply, divide, add, subtract)
- - String (uppercase, lowercase, trim, replace, substring)
- - Financial (bpsToPercent, percentToBps, roundPrice)
-
-### 4. Core Mapping Engine
-- [x] `engine/MappingEngine.ts` - Complete transformation pipeline:
- - Data fetching from connections
- - Extraction using parsers
- - Field mapping & transformation
- - Post-processing (filter, sort, limit, deduplicate)
- - Validation against schemas
- - Error handling & result metadata
-
-### 5. Services
-- [x] `services/ConnectionService.ts` - Interface with data-sources
-
-### 6. Documentation
-- [x] `README.md` - Complete system documentation
-- [x] `AUTH_INTEGRATION.md` - Authentication strategy
-- [x] `PROGRESS.md` - This file
-
-### 7. Dependencies
-- [x] npm packages installed: jsonpath, jsonata, jmespath
-
----
-
-## 🚧 IN PROGRESS (UI Components)
-
-The following components need to be built to complete the system:
-
-### UI Components (Priority Order)
-
-1. **JSONExplorer.tsx** - Interactive JSON tree viewer
- - Expand/collapse nodes
- - Click to select fields
- - Auto-generate expressions
- - Copy paths
-
-2. **ExpressionBuilder.tsx** - Build & test parser expressions
- - Parser engine selector
- - Expression editor with syntax highlighting
- - Live testing with sample data
- - Syntax help & examples
-
-3. **SchemaSelector.tsx** - Choose target schema
- - Display available schemas
- - Show field definitions
- - Preview examples
-
-4. **ConnectionSelector.tsx** - Select data source connection
- - List connected data sources
- - Filter by type/status
- - Show connection details
-
-5. **FieldMapper.tsx** - Map individual fields
- - Source expression input
- - Target field selector
- - Transform function picker
- - Default value input
-
-6. **MappingCanvas.tsx** - Visual field mapping interface
- - Source schema display
- - Target schema display
- - Visual connectors
- - Drag-drop mapping
-
-7. **LivePreview.tsx** - Real-time transformation preview
- - Input data display
- - Transformed output
- - Validation results
- - Error messages
-
-8. **TemplateLibrary.tsx** - Pre-built templates
- - Browse templates by category
- - Preview template config
- - Apply template
- - Save custom templates
-
-9. **MappingList.tsx** - List of saved mappings
- - Search & filter
- - Edit/delete actions
- - Quick test
- - Usage stats
-
-10. **DataMappingTab.tsx** - Main tab component
- - 3-panel layout
- - Step-by-step wizard
- - State management
- - Integration with other components
-
-### Templates
-
-11. **templates/indian-brokers.ts** - Pre-built mappings for:
- - Upstox (historical, quotes, orders)
- - Fyers (quotes, positions)
- - Dhan (portfolio, orders)
- - Zerodha (Kite API)
- - Angel One
-
-12. **templates/global-providers.ts** - Pre-built mappings for:
- - Yahoo Finance
- - Alpha Vantage
- - Polygon.io
- - Finnhub
- - IEX Cloud
-
-### Storage & Persistence
-
-13. **services/MappingStorage.ts** - DuckDB integration
- - Save/load mappings
- - Version control
- - Import/export
- - Search & indexing
-
-14. **services/AIMapper.ts** - AI-powered auto-mapping
- - Analyze source JSON structure
- - Suggest field mappings
- - Confidence scoring
- - Semantic matching
-
-### Utilities
-
-15. **utils/jsonFlattener.ts** - Flatten nested JSON for UI
-16. **utils/pathBuilder.ts** - Build JSONPath/JSONata expressions
-17. **utils/sampleData.ts** - Sample data for testing
-
----
-
-## 📊 Completion Status
-
-| Category | Completed | Total | % |
-|----------|-----------|-------|-----|
-| Core Engine | 4 | 4 | 100% |
-| Parsers | 6 | 6 | 100% |
-| Schemas | 7 | 7 | 100% |
-| Transforms | 22 | 22 | 100% |
-| Services | 1 | 4 | 25% |
-| UI Components | 0 | 10 | 0% |
-| Templates | 0 | 2 | 0% |
-| Utilities | 0 | 3 | 0% |
-| **TOTAL** | **40** | **58** | **69%** |
-
----
-
-## 🎯 Next Steps
-
-### Immediate (High Priority)
-1. Build main `DataMappingTab.tsx` with basic layout
-2. Implement `JSONExplorer` for data inspection
-3. Create `ExpressionBuilder` for testing
-4. Build `LivePreview` panel
-
-### Short-term (Medium Priority)
-5. Implement `MappingCanvas` for visual mapping
-6. Create `TemplateLibrary` component
-7. Add Indian broker templates (Upstox, Fyers, Dhan)
-8. Build `MappingList` for saved mappings
-
-### Long-term (Lower Priority)
-9. Implement DuckDB storage
-10. Add AI-powered mapping suggestions
-11. Build drag-drop visual mapper
-12. Add advanced features (multi-mapping, caching)
-
----
-
-## 💡 What We Have Built So Far
-
-The **core transformation engine** is complete and production-ready:
-
-```typescript
-// Example: Transform Upstox data to OHLCV
-const engine = new MappingEngine();
-
-const result = await engine.execute({
- mapping: upstoxOHLCVMapping,
- parameters: { symbol: 'SBIN', from: '2024-01-01', to: '2024-10-01' }
-});
-
-// Returns standardized OHLCV data
-// [{ symbol, timestamp, open, high, low, close, volume }, ...]
-```
-
-**Features:**
-✅ 5 powerful parsers (JSONPath, JSONata, JMESPath, Direct, JavaScript)
-✅ 22 transformation functions
-✅ Schema validation
-✅ Post-processing (filter, sort, limit)
-✅ Error handling & metadata
-✅ Authentication via existing connections
-✅ Extensible architecture
-
-**What's Needed:**
-- UI components to configure mappings visually
-- Templates for common data sources
-- Storage/persistence layer
-- User-friendly workflow
-
----
-
-## 🚀 Ready to Continue
-
-The foundation is solid. We can now:
-1. Build the UI layer
-2. Create templates for Indian brokers
-3. Add storage integration
-4. Test end-to-end workflow
-
-Choose which component to build next!
diff --git a/legacy-python-depreciated/CONTRIBUTING.md b/legacy-python-depreciated/CONTRIBUTING.md
deleted file mode 100644
index 4130eace5..000000000
--- a/legacy-python-depreciated/CONTRIBUTING.md
+++ /dev/null
@@ -1,288 +0,0 @@
-# Contributing to Fincept Terminals
-
-Welcome to the Fincept Terminal community! Your contributions help build the future of open-source financial technology.
-
-## Project Architecture Overview
-
-Fincept Terminal uses a **Hybrid MVP (Model-View-Presenter) + Services** architecture designed for massive scalability and modular development. This architecture allows thousands of developers to contribute independently without breaking existing functionality.
-
-### Why This Architecture?
-
-- **Modularity**: Add new features without affecting existing code
-- **Team Collaboration**: Different teams can work on different layers simultaneously
-- **Easy Testing**: Each layer can be tested in isolation
-- **Beginner Friendly**: Clear separation makes it easy to understand and contribute
-- **Bloomberg Scale**: Designed to handle thousands of data sources and features
-
-## Directory Structure
-
-```
-/fincept_terminal
-├── /models # Data structures and entities
-│ ├── /analytics
-│ │ └── analytics_models.py
-│ ├── /dashboard
-│ │ └── dashboard_models.py
-│ ├── /portfolio
-│ │ └── portfolio_models.py
-│ ├── /watchlist
-│ │ └── watchlist_models.py
-│ └── /shared # Models used by 2+ modules
-│ └── common_models.py
-├── /services # Data fetching and processing
-│ ├── /analytics
-│ │ └── analytics_service.py
-│ ├── /dashboard
-│ │ └── dashboard_service.py
-│ ├── /portfolio
-│ │ └── portfolio_service.py
-│ ├── /watchlist
-│ │ └── watchlist_service.py
-│ └── /shared # Services used by 2+ modules
-│ └── api_service.py
-├── /presenters # Business logic and coordination
-│ ├── /analytics
-│ │ └── analytics_presenter.py
-│ ├── /dashboard
-│ │ └── dashboard_presenter.py
-│ ├── /portfolio
-│ │ └── portfolio_presenter.py
-│ ├── /watchlist
-│ │ └── watchlist_presenter.py
-│ └── /shared # Inter-module communication
-│ └── event_bus.py
-├── /views # User interface components
-│ ├── /analytics
-│ │ └── analytics_view.py
-│ ├── /dashboard
-│ │ └── dashboard_view.py
-│ ├── /portfolio
-│ │ └── portfolio_view.py
-│ ├── /watchlist
-│ │ └── watchlist_view.py
-│ └── /shared # Reusable UI components
-│ ├── chart_components.py
-│ └── common_widgets.py
-├── /utils # Global utilities (logging, validation, etc.)
-│ ├── logging.py
-│ ├── validators.py
-│ └── formatters.py
-└── /core # Framework core and base classes
- ├── base_tab.py
- ├── base_service.py
- └── app_config.py
-```
-
-## Architecture Layers
-
-### 1. Models Layer (`/models`)
-**Purpose**: Define data structures, entities, and business objects
-
-**What goes here**:
-- Data classes and dataclasses
-- Entity definitions (Stock, Portfolio, News, etc.)
-- Configuration objects
-- Enums and constants
-
-**Example**:
-```python
-# models/dashboard/stock_data.py
-@dataclass
-class StockData:
- symbol: str
- price: float
- change_pct: float
- volume: int
-```
-
-**Contribution Guidelines**:
-- Use dataclasses for simple data containers
-- Include validation methods
-- Add type hints to all fields
-- Document all fields with docstrings
-
-### 2. Services Layer (`/services`)
-**Purpose**: Handle data fetching, API calls, and data processing
-
-**What goes here**:
-- External API integrations
-- Data fetching logic
-- Data transformation and processing
-- Caching mechanisms
-- Error handling for data operations
-
-**Example**:
-```python
-# services/dashboard/market_data_service.py
-class MarketDataService:
- def fetch_stock_data(self, symbols: List[str]) -> Dict[str, StockData]:
- # API calls and data processing
-```
-
-**Contribution Guidelines**:
-- Handle all errors gracefully with fallback data
-- Use concurrent programming for multiple API calls
-- Include comprehensive logging
-- Write data validation logic
-- Create mock/fallback data for testing
-
-### 3. Presenters Layer (`/presenters`)
-**Purpose**: Business logic, state management, and coordination between views and services
-
-**What goes here**:
-- Business rules and logic
-- State management
-- Event handling
-- Data transformation for UI
-- Inter-module communication
-
-**Example**:
-```python
-# presenters/dashboard/dashboard_presenter.py
-class DashboardPresenter:
- def __init__(self, view, service):
- self.view = view
- self.service = service
-
- def refresh_data(self):
- data = self.service.fetch_all_data()
- self.view.update_display(data)
-```
-
-**Contribution Guidelines**:
-- Keep business logic here, not in views
-- Manage application state
-- Handle user interactions
-- Coordinate between multiple services if needed
-
-### 4. Views Layer (`/views`)
-**Purpose**: User interface and presentation logic only
-
-**What goes here**:
-- DearPyGui UI components
-- Chart creation and rendering
-- Event callbacks (but not logic)
-- UI updates and animations
-
-**Example**:
-```python
-# views/dashboard/dashboard_view.py
-class DashboardView(BaseTab):
- def create_content(self):
- # DearPyGui UI creation only
- dpg.add_table(...)
-
- def update_stock_table(self, stocks):
- # Update UI with new data
-```
-
-**Contribution Guidelines**:
-- Only DearPyGui code goes here
-- No business logic in views
-- Event handlers should call presenter methods
-- Focus on user experience and visual design
-
-## How to Contribute
-
-### Adding a New Feature
-
-1. **Choose Your Layer**: Decide which layer your contribution affects
-2. **Create Module Folders**: Add folders in relevant layers
-3. **Follow Naming Conventions**: Use clear, descriptive names
-
-**Example: Adding a "News Analysis" feature**
-```
-/app
-├── /models/news_analysis/
-│ ├── news_models.py
-│ └── sentiment_models.py
-├── /services/news_analysis/
-│ ├── news_service.py
-│ └── sentiment_service.py
-├── /presenters/news_analysis/
-│ └── news_presenter.py
-└── /views/news_analysis/
- └── news_view.py
-```
-
-### Partial Contributions Welcome
-
-You don't need to implement all layers! Contributions can be:
-
-**UI Only**: Work in `/views` folder
-- Design new charts or interfaces
-- Improve existing UI components
-- Add new visualization types
-
-**Data Only**: Work in `/services` folder
-- Add new data sources (crypto exchanges, news APIs)
-- Improve data processing algorithms
-- Add new market indicators
-
-**Business Logic Only**: Work in `/presenters` folder
-- Add new analysis algorithms
-- Implement trading strategies
-- Create data aggregation logic
-
-**Models Only**: Work in `/models` folder
-- Define new data structures
-- Add validation logic
-- Create configuration objects
-
-### Inter-Module Communication
-
-When features need to communicate:
-
-1. **Add to `/shared` folders**: Common code goes in shared directories
-2. **Use Presenter Layer**: Inter-module communication happens in presenters
-3. **Avoid Direct Dependencies**: Modules should not directly import each other
-
-### File Naming Conventions
-
-- **Models**: `*_models.py` (e.g., `stock_models.py`)
-- **Services**: `*_service.py` (e.g., `market_data_service.py`)
-- **Presenters**: `*_presenter.py` (e.g., `dashboard_presenter.py`)
-- **Views**: `*_view.py` (e.g., `analytics_view.py`)
-
-### Code Quality Standards
-
-1. **Type Hints**: Use type hints for all function parameters and returns
-2. **Docstrings**: Document all classes and public methods
-3. **Error Handling**: Include comprehensive error handling
-4. **Logging**: Use the shared logging system for debugging
-5. **Testing**: Write unit tests for your contributions
-
-### Getting Started
-
-1. **Fork the Repository**
-2. **Choose a Feature**: Pick something you want to work on
-3. **Create Module Structure**: Add necessary folders
-4. **Start Small**: Begin with models or a simple service
-5. **Submit PR**: Submit your contribution for review
-
-### Examples for New Contributors
-
-**Easy Contributions**:
-- Add a new stock exchange data source
-- Create a new chart type for existing data
-- Add a new economic indicator
-- Improve error messages
-
-**Medium Contributions**:
-- Add crypto portfolio tracking
-- Implement technical analysis indicators
-- Create news sentiment analysis
-- Add export/import functionality
-
-**Advanced Contributions**:
-- Add real-time streaming data
-- Implement machine learning features
-- Create plugin system for external modules
-- Add advanced backtesting capabilities
-
-## Questions?
-
-- Read existing code in `/app` to understand patterns
-- Check `/utils` for shared utilities you can use
-- Look at `/core` for base classes to inherit from
-- Submit an issue if you need clarification