diff --git a/docs/planned/FUNCTIONALITY_REVIEW.md b/docs/planned/FUNCTIONALITY_REVIEW.md
new file mode 100644
index 0000000..90cd89a
--- /dev/null
+++ b/docs/planned/FUNCTIONALITY_REVIEW.md
@@ -0,0 +1,786 @@
+# Trading Dashboard Functionality Review
+
+**Date:** 2026-05-09  
+**Purpose:** Comprehensive review of trading dashboard functionality, identifying gaps, bugs, and improvements  
+**Status:** Initial Review
+
+---
+
+## Executive Summary
+
+The trading dashboard monorepo is in a mature state with Phase 6 marked as Done. However, several gaps, bugs, and improvement opportunities exist across backend, web, and mobile surfaces.
+
+**Key Findings:**
+- **Functional Gaps:** 12 identified
+- **Bugs:** 8 identified
+- **Improvements:** 15 identified
+- **Documentation Gaps:** 6 identified
+- **Testing Gaps:** 5 identified
+- **Security Concerns:** 4 identified
+- **Performance Issues:** 3 identified
+
+---
+
+## 1. Functional Gaps
+
+### 1.1 Mobile Push Notifications
+
+**Status:** Deferred in ROADMAP  
+**Issue:** Push notification architecture is not implemented  
+**Impact:** Users cannot receive real-time alerts on mobile  
+**Reference:** ROADMAP.md line 343, line 626
+
+**Recommendation:**
+- Select push notification provider (OneSignal, Firebase Cloud Messaging, or Expo Push)
+- Implement push notification service
+- Add notification permission handling in mobile app
+- Test notification delivery across platforms
+
+### 1.2 Cosmos Audit Events Container
+
+**Status:** Not created  
+**Issue:** Cosmos audit-events container referenced but not provisioned  
+**Impact:** Audit events cannot be persisted to Cosmos  
+**Reference:** ROADMAP.md line 627
+
+**Recommendation:**
+- Create Cosmos audit-events container in Azure
+- Verify repository implementation
+- Test audit event persistence
+- Update deployment documentation
+
+### 1.3 Mobile Internal Beta
+
+**Status:** Not started  
+**Issue:** Mobile internal beta not conducted  
+**Impact:** Mobile app not validated with real users  
+**Reference:** ROADMAP.md line 500-501, CUTOVER_WEB.md line 224
+
+**Recommendation:**
+- Define mobile beta criteria
+- Select internal beta testers
+- Deploy mobile beta
+- Collect feedback and iterate
+
+### 1.4 Web Internal Adoption
+
+**Status:** In progress  
+**Issue:** Web internal adoption not complete  
+**Impact:** Legacy web dashboard still in use  
+**Reference:** ROADMAP.md line 499, CUTOVER_WEB.md
+
+**Recommendation:**
+- Complete CUTOVER_WEB.md checklist
+- Switch internal operators to new web dashboard
+- Monitor for issues
+- Archive legacy web dashboard
+
+### 1.5 Backtest Feature Flag Integration
+
+**Status:** Partially implemented  
+**Issue:** Backtest feature flag exists but not fully integrated  
+**Impact:** Inconsistent backtest access control  
+**Reference:** ROADMAP.md line 45-46
+
+**Recommendation:**
+- Verify backtest feature flag contract
+- Ensure consistent evaluation across web and backend
+- Test feature flag toggling
+- Update documentation
+
+### 1.6 Marketplace Tab
+
+**Status:** Feature-flagged  
+**Issue:** Marketplace tab visibility controlled by feature flag  
+**Impact:** Marketplace may not be available to all users  
+**Reference:** CUTOVER_WEB.md line 47-48
+
+**Recommendation:**
+- Define marketplace rollout strategy
+- Test marketplace functionality
+- Ensure marketplace data integrity
+- Plan for full rollout
+
+### 1.7 Membership Tab
+
+**Status:** Feature-flagged  
+**Issue:** Membership tab visibility controlled by feature flag  
+**Impact:** Membership features may not be available  
+**Reference:** CUTOVER_WEB.md line 48-49
+
+**Recommendation:**
+- Define membership feature scope
+- Implement membership functionality
+- Test membership workflows
+- Plan for full rollout
+
+### 1.8 Mobile Strategy Management
+
+**Status:** Not implemented  
+**Issue:** Mobile app does not support strategy editing  
+**Impact:** Users cannot manage strategies on mobile  
+**Reference:** ROADMAP.md line 364
+
+**Recommendation:**
+- Define mobile strategy management scope
+- Implement basic strategy viewing
+- Add strategy editing if needed
+- Ensure backend API supports mobile operations
+
+### 1.9 Mobile Admin Diagnostics
+
+**Status:** Not implemented  
+**Issue:** No admin diagnostics UI in mobile app  
+**Impact:** Admins cannot diagnose issues on mobile  
+**Reference:** ROADMAP.md line 365
+
+**Recommendation:**
+- Assess need for mobile admin diagnostics
+- Implement if justified
+- Ensure role-based access control
+- Test admin workflows
+
+### 1.10 Chat/Copilot Integration
+
+**Status:** Partially implemented  
+**Issue:** Chat copilot exists but may not be fully integrated  
+**Impact:** AI assistance may be incomplete  
+**Reference:** Backend has verifyChatCopilotContract.ts
+
+**Recommendation:**
+- Review chat copilot implementation
+- Test chat functionality across surfaces
+- Ensure fallback mechanisms work
+- Document chat copilot behavior
+
+### 1.11 Reconciliation Services
+
+**Status:** Multiple reconciliation services exist  
+**Issue:** Reconciliation may have gaps in coverage  
+**Impact:** Data inconsistencies may not be detected  
+**Reference:** backend/src/services/ has multiple reconciliation services
+
+**Recommendation:**
+- Audit reconciliation service coverage
+- Test reconciliation workflows
+- Ensure all reconciliation paths are covered
+- Add monitoring for reconciliation failures
+
+### 1.12 Trading Control Persistence
+
+**Status:** Cosmos-backed  
+**Issue:** Trading control persistence may have edge cases  
+**Impact:** Trading control state may be inconsistent  
+**Reference:** tradingControlRepository.ts
+
+**Recommendation:**
+- Test trading control persistence edge cases
+- Ensure control state is durable across restarts
+- Add control state validation
+- Monitor control state drift
+
+---
+
+## 2. Bugs
+
+### 2.1 UX Guide Typo
+
+**File:** docs/UX_TESTING_SETUP_GUIDE.md line 76  
+**Issue:** Typo in environment variable name  
+**Code:** `BYTELYST_PACKAGE_SOURCE=giteaye`  
+**Expected:** `BYTELYST_PACKAGE_SOURCE=gitea`  
+**Impact:** Documentation error could confuse developers  
+**Priority:** Low
+
+**Fix:**
+```bash
+sed -i 's/giteaye/gitea/g' docs/UX_TESTING_SETUP_GUIDE.md
+```
+
+### 2.2 E2E Test Count Parsing
+
+**File:** scripts/tests/run-e2e.sh  
+**Issue:** Test count parsing shows 0 even when tests pass  
+**Impact:** Test results summary is misleading  
+**Priority:** Medium  
+**Status:** Fixed in commit c9c6119
+
+**Verification:**
+```bash
+./scripts/tests/run-e2e.sh
+# Verify test count is displayed correctly
+```
+
+### 2.3 Mobile App Src Directory
+
+**Issue:** Mobile app uses `app/` directory instead of `src/`  
+**Impact:** Inconsistent with typical Expo structure  
+**Reference:** mobile/app/ exists but mobile/src/ does not  
+**Priority:** Low  
+**Note:** This is intentional per Expo Router conventions
+
+### 2.4 Legacy Supabase Scripts
+
+**Issue:** Root-level backend scripts still use legacy Supabase  
+**Impact:** Maintenance burden, potential data inconsistency  
+**Reference:** docs/BACKEND_LEGACY_SUPABASE_SCRIPTS.md  
+**Priority:** Medium
+
+**Recommendation:**
+- Document why each script needs legacy Supabase
+- Migrate to Cosmos where possible
+- Add deprecation warnings
+- Plan for eventual removal
+
+### 2.5 SupabaseService Size
+
+**File:** backend/src/services/SupabaseService.ts (118KB)  
+**Issue:** Very large file indicates potential code smell  
+**Impact:** Difficult to maintain, test, and understand  
+**Priority:** Medium
+
+**Recommendation:**
+- Refactor SupabaseService into smaller modules
+- Extract common patterns
+- Improve testability
+- Document module boundaries
+
+### 2.6 TradeExecutor Size
+
+**File:** backend/src/services/TradeExecutor.ts (128KB)  
+**Issue:** Very large file indicates potential code smell  
+**Impact:** Difficult to maintain, test, and understand  
+**Priority:** Medium
+
+**Recommendation:**
+- Refactor TradeExecutor into smaller modules
+- Extract strategy-specific logic
+- Improve testability
+- Document execution flow
+
+### 2.7 apiServer Size
+
+**File:** backend/src/services/apiServer.ts (183KB)  
+**Issue:** Very large file indicates potential code smell  
+**Impact:** Difficult to maintain, test, and understand  
+**Priority:** Medium
+
+**Recommendation:**
+- Refactor apiServer into route modules
+- Extract endpoint handlers
+- Improve testability
+- Document API contract
+
+### 2.8 Web Chat Control Size
+
+**File:** web/src/components/ChatControl.tsx (58KB)  
+**Issue:** Very large component indicates potential code smell  
+**Impact:** Difficult to maintain, test, and understand  
+**Priority:** Medium
+
+**Recommendation:**
+- Refactor ChatControl into smaller components
+- Extract chat logic into hooks
+- Improve testability
+- Document component behavior
+
+---
+
+## 3. Improvements
+
+### 3.1 Backend Service Modularization
+
+**Issue:** Several backend services are very large (SupabaseService 118KB, TradeExecutor 128KB, apiServer 183KB)  
+**Impact:** Maintainability, testability, code review difficulty  
+**Priority:** High
+
+**Recommendation:**
+- Split SupabaseService into domain-specific modules
+- Split TradeExecutor into strategy-specific modules
+- Split apiServer into route-specific modules
+- Add integration tests for refactored modules
+
+### 3.2 Web Component Modularization
+
+**Issue:** ChatControl.tsx is 58KB, TradeProfileManager.tsx is 92KB  
+**Impact:** Maintainability, testability, code review difficulty  
+**Priority:** High
+
+**Recommendation:**
+- Split ChatControl into chat-specific components
+- Split TradeProfileManager into profile-specific components
+- Extract business logic into hooks
+- Add unit tests for refactored components
+
+### 3.3 Backend API Contract Documentation
+
+**Issue:** API endpoints documented in BACKEND_API_DEPRECATION.md but not in Swagger/OpenAPI  
+**Impact:** API consumers must read code to understand endpoints  
+**Priority:** Medium
+
+**Recommendation:**
+- Generate OpenAPI/Swagger documentation from backend code
+- Host API documentation
+- Keep documentation in sync with code
+- Add API versioning
+
+### 3.4 Web Component Storybook Coverage
+
+**Issue:** Not all web components have Storybook stories  
+**Impact:** Component development and testing less efficient  
+**Priority:** Medium
+
+**Recommendation:**
+- Add Storybook stories for all major components
+- Use Storybook for component development
+- Add visual regression tests
+- Document component variants
+
+### 3.5 Mobile App Testing
+
+**Issue:** Mobile app has limited test coverage  
+**Impact:** Mobile bugs may go undetected  
+**Priority:** High
+
+**Recommendation:**
+- Add unit tests for mobile components
+- Add E2E tests for mobile flows
+- Add visual regression tests
+- Test on multiple devices/simulators
+
+### 3.6 Backend Test Coverage
+
+**Issue:** Backend has many contract tests but may lack integration tests  
+**Impact:** Backend integration issues may not be caught  
+**Priority:** Medium
+
+**Recommendation:**
+- Add integration tests for backend services
+- Test Cosmos repository operations
+- Test websocket functionality
+- Test reconciliation workflows
+
+### 3.7 Error Monitoring Integration
+
+**Issue:** No explicit error monitoring integration (Sentry, etc.)  
+**Impact:** Production errors may go undetected  
+**Priority:** High
+
+**Recommendation:**
+- Integrate error monitoring (Sentry, etc.)
+- Add error tracking to all surfaces
+- Set up error alerts
+- Document error response procedures
+
+### 3.8 Performance Monitoring
+
+**Issue:** No explicit performance monitoring  
+**Impact:** Performance regressions may go undetected  
+**Priority:** Medium
+
+**Recommendation:**
+- Add performance monitoring (APM)
+- Track API response times
+- Track frontend performance
+- Set up performance alerts
+
+### 3.9 Logging Standardization
+
+**Issue:** Logging may not be standardized across surfaces  
+**Impact:** Debugging and troubleshooting difficult  
+**Priority:** Medium
+
+**Recommendation:**
+- Standardize log format across backend, web, mobile
+- Add correlation IDs to all logs
+- Add structured logging
+- Centralize log aggregation
+
+### 3.10 Configuration Validation
+
+**Issue:** Environment variables may not be validated at startup  
+**Impact:** Configuration errors may cause runtime failures  
+**Priority:** High
+
+**Recommendation:**
+- Add environment variable validation
+- Fail fast on invalid configuration
+- Document all required environment variables
+- Add configuration tests
+
+### 3.11 Dependency Updates
+
+**Issue:** Dependencies may not be regularly updated  
+**Impact:** Security vulnerabilities, missing features  
+**Priority:** Medium
+
+**Recommendation:**
+- Set up dependency update automation
+- Review security advisories regularly
+- Test dependency updates
+- Document dependency policy
+
+### 3.12 Docker Multi-Stage Builds
+
+**Issue:** Docker builds may not use multi-stage builds  
+**Impact:** Larger Docker images, longer build times  
+**Priority:** Low
+
+**Recommendation:**
+- Implement multi-stage Docker builds
+- Optimize Docker image sizes
+- Reduce build times
+- Test Docker builds in CI
+
+### 3.13 CI/CD Pipeline
+
+**Issue:** No explicit CI/CD pipeline documentation  
+**Impact:** Deployment process unclear  
+**Priority:** Medium
+
+**Recommendation:**
+- Document CI/CD pipeline
+- Add automated testing in CI
+- Add automated deployment
+- Document rollback procedures
+
+### 3.14 Accessibility Improvements
+
+**Issue:** Accessibility may not be fully implemented  
+**Impact:** Users with disabilities may have difficulty  
+**Priority:** Medium
+
+**Recommendation:**
+- Run accessibility audits
+- Fix ARIA issues
+- Improve keyboard navigation
+- Add accessibility tests
+
+### 3.15 Responsive Design Testing
+
+**Issue:** Responsive design may not be tested across all viewports  
+**Impact:** Mobile/tablet users may have poor experience  
+**Priority:** Medium
+
+**Recommendation:**
+- Add viewport matrix tests for all views
+- Test on actual devices
+- Test responsive breakpoints
+- Document responsive behavior
+
+---
+
+## 4. Documentation Gaps
+
+### 4.1 Mobile Cutover Documentation
+
+**Issue:** CUTOVER_MOBILE.md referenced but not created  
+**Impact:** Mobile cutover process unclear  
+**Reference:** CUTOVER_WEB.md line 224  
+**Priority:** High
+
+**Recommendation:**
+- Create CUTOVER_MOBILE.md
+- Document mobile beta process
+- Document mobile cutover steps
+- Document mobile rollback procedures
+
+### 4.2 API Documentation
+
+**Issue:** No comprehensive API documentation  
+**Impact:** API consumers must read code  
+**Priority:** High
+
+**Recommendation:**
+- Generate OpenAPI/Swagger documentation
+- Host API documentation
+- Document all endpoints
+- Add examples
+
+### 4.3 Architecture Documentation
+
+**Issue:** No comprehensive architecture documentation  
+**Impact:** New developers may struggle to understand system  
+**Priority:** Medium
+
+**Recommendation:**
+- Create architecture diagram
+- Document data flow
+- Document service boundaries
+- Document integration points
+
+### 4.4 Deployment Documentation
+
+**Issue:** Deployment process may not be fully documented  
+**Impact:** Deployment errors may occur  
+**Priority:** High
+
+**Recommendation:**
+- Document deployment process
+- Document environment setup
+- Document configuration
+- Document troubleshooting
+
+### 4.5 Troubleshooting Guide
+
+**Issue:** No comprehensive troubleshooting guide  
+**Impact:** Issues may take longer to resolve  
+**Priority:** Medium
+
+**Recommendation:**
+- Create troubleshooting guide
+- Document common issues
+- Document resolution steps
+- Document escalation procedures
+
+### 4.6 Onboarding Documentation
+
+**Issue:** No developer onboarding guide  
+**Impact:** New developers may struggle to get started  
+**Priority:** Medium
+
+**Recommendation:**
+- Create onboarding guide
+- Document development setup
+- Document development workflow
+- Document code review process
+
+---
+
+## 5. Testing Gaps
+
+### 5.1 Mobile E2E Tests
+
+**Issue:** No E2E tests for mobile app  
+**Impact:** Mobile bugs may go undetected  
+**Priority:** High
+
+**Recommendation:**
+- Add Detox or Appium for mobile E2E tests
+- Test critical mobile flows
+- Test on multiple devices
+- Integrate with CI
+
+### 5.2 Backend Integration Tests
+
+**Issue:** Backend has contract tests but limited integration tests  
+**Impact:** Backend integration issues may not be caught  
+**Priority:** Medium
+
+**Recommendation:**
+- Add integration tests for backend services
+- Test Cosmos repository operations
+- Test websocket functionality
+- Test reconciliation workflows
+
+### 5.3 Web Component Unit Tests
+
+**Issue:** Some web components lack unit tests  
+**Impact:** Component bugs may go undetected  
+**Priority:** Medium
+
+**Recommendation:**
+- Add unit tests for all components
+- Test component behavior
+- Test component integration
+- Achieve target coverage
+
+### 5.4 Backend Repository Tests
+
+**Issue:** Backend repositories may lack comprehensive tests  
+**Impact:** Data layer bugs may go undetected  
+**Priority:** Medium
+
+**Recommendation:**
+- Add unit tests for all repositories
+- Test repository operations
+- Test error handling
+- Test Cosmos integration
+
+### 5.5 Performance Tests
+
+**Issue:** No performance tests  
+**Impact:** Performance regressions may go undetected  
+**Priority:** Medium
+
+**Recommendation:**
+- Add load tests for backend API
+- Add performance tests for web
+- Add performance tests for mobile
+- Set up performance baselines
+
+---
+
+## 6. Security Concerns
+
+### 6.1 Tenant Isolation
+
+**Issue:** Tenant isolation may have edge cases  
+**Impact:** Data leak between tenants  
+**Priority:** Critical  
+**Reference:** Backend has verifyTenantIsolation.ts
+
+**Recommendation:**
+- Review tenant isolation implementation
+- Add tenant isolation tests
+- Test tenant isolation edge cases
+- Monitor for tenant isolation violations
+
+### 6.2 API Rate Limiting
+
+**Issue:** No explicit API rate limiting  
+**Impact:** API abuse, DoS attacks  
+**Priority:** High
+
+**Recommendation:**
+- Implement API rate limiting
+- Add rate limiting to backend
+- Add rate limiting to platform-service integration
+- Monitor for rate limit violations
+
+### 6.3 Input Validation
+
+**Issue:** Input validation may not be comprehensive  
+**Impact:** Security vulnerabilities  
+**Priority:** High
+
+**Recommendation:**
+- Review all API inputs for validation
+- Add input validation where missing
+- Sanitize user inputs
+- Test input validation
+
+### 6.4 Secret Management
+
+**Issue:** Secrets may be hardcoded or improperly managed  
+**Impact:** Security vulnerabilities  
+**Priority:** Critical
+
+**Recommendation:**
+- Audit all hardcoded secrets
+- Use Azure Key Vault for secrets
+- Rotate secrets regularly
+- Document secret management
+
+---
+
+## 7. Performance Issues
+
+### 7.1 Backend Service Size
+
+**Issue:** Large backend services may have performance impact  
+**Impact:** Slower startup, larger memory footprint  
+**Priority:** Medium
+
+**Recommendation:**
+- Profile large services
+- Identify performance bottlenecks
+- Optimize hot paths
+- Consider lazy loading
+
+### 7.2 Web Bundle Size
+
+**Issue:** Web bundle size may be large  
+**Impact:** Slower page load  
+**Priority:** Medium
+
+**Recommendation:**
+- Analyze web bundle size
+- Identify large dependencies
+- Implement code splitting
+- Optimize bundle size
+
+### 7.3 Mobile App Size
+
+**Issue:** Mobile app size may be large  
+**Impact:** Slower download, larger storage  
+**Priority:** Low
+
+**Recommendation:**
+- Analyze mobile app size
+- Identify large dependencies
+- Optimize assets
+- Consider dynamic imports
+
+---
+
+## 8. Recommendations Summary
+
+### High Priority
+
+1. **Create CUTOVER_MOBILE.md** - Document mobile cutover process
+2. **Implement error monitoring** - Add Sentry or similar
+3. **Add mobile E2E tests** - Ensure mobile quality
+4. **Review tenant isolation** - Ensure data security
+5. **Add API rate limiting** - Prevent API abuse
+6. **Refactor large backend services** - Improve maintainability
+7. **Refactor large web components** - Improve maintainability
+8. **Add configuration validation** - Fail fast on config errors
+
+### Medium Priority
+
+1. **Create Cosmos audit-events container** - Enable audit persistence
+2. **Generate API documentation** - Improve API discoverability
+3. **Add Storybook coverage** - Improve component development
+4. **Add backend integration tests** - Ensure backend quality
+5. **Add web component unit tests** - Ensure component quality
+6. **Standardize logging** - Improve debugging
+7. **Add performance monitoring** - Detect performance regressions
+8. **Implement dependency updates** - Keep dependencies current
+9. **Improve accessibility** - Ensure inclusive design
+10. **Add performance tests** - Ensure performance
+
+### Low Priority
+
+1. **Fix UX guide typo** - Correct documentation
+2. **Optimize Docker builds** - Reduce image size
+3. **Optimize mobile app size** - Reduce app size
+
+---
+
+## 9. Next Steps
+
+### Immediate (This Week)
+
+1. Fix UX guide typo
+2. Create CUTOVER_MOBILE.md
+3. Add configuration validation
+4. Review tenant isolation
+
+### Short-term (This Month)
+
+1. Implement error monitoring
+2. Add mobile E2E tests
+3. Add API rate limiting
+4. Refactor large backend services
+5. Refactor large web components
+
+### Medium-term (This Quarter)
+
+1. Create Cosmos audit-events container
+2. Generate API documentation
+3. Add Storybook coverage
+4. Add backend integration tests
+5. Add web component unit tests
+
+### Long-term (This Year)
+
+1. Implement push notifications
+2. Complete mobile internal beta
+3. Complete web internal adoption
+4. Add performance monitoring
+5. Standardize logging
+
+---
+
+## 10. Conclusion
+
+The trading dashboard is in a mature state with strong foundations. However, several gaps, bugs, and improvement opportunities exist. Addressing these issues will improve reliability, maintainability, and user experience.
+
+The highest priority items are:
+- Security (tenant isolation, rate limiting)
+- Quality (mobile E2E tests, error monitoring)
+- Maintainability (refactoring large files)
+- Documentation (mobile cutover, API docs)
+
+Addressing these items will ensure the trading dashboard is production-ready and maintainable for the long term.