aimi-replica

Implement authentication service with JWT and password hashing for all personas.

As a frontend developer, implement the Navbar section for the Login page. This section includes a header with a brand logo and a navigation link back to the home page. Ensure the Navbar is styled according to the provided CSS and is accessible to all personas: Administrator, Financial Analyst, and General User. Note that the Navbar component may already exist from the Landing page and should be reused if possible. Page access: shared by all personas (Administrator, Financial Analyst, General User).

Define and implement data retention policies for user and session data.

As a Tech Lead, verify the end-to-end integration between the Landing frontend implementation and the Landing backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the Settings frontend implementation and the Settings backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

Implement role-based access control for different personas: Administrator, Financial Analyst, and General User.

As a frontend developer, implement the LoginFormPanel section for the Login page. This section includes a form with email and password fields, validation logic, and a toggle for showing/hiding the password. It uses state hooks for managing form inputs and errors. Ensure the form is styled according to the provided CSS and is accessible to all personas: Administrator, Financial Analyst, and General User. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the LoginSocialPanel section for the Login page. This section includes buttons for social login options like Google and Apple, with corresponding SVG icons. Ensure the buttons are styled according to the provided CSS and are accessible to all personas: Administrator, Financial Analyst, and General User. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the Footer section for the Login page. This section includes links to Privacy Policy, Terms of Service, and Contact pages, along with a copyright notice. Ensure the Footer is styled according to the provided CSS and is accessible to all personas: Administrator, Financial Analyst, and General User. Note that the Footer component may already exist from the Landing page and should be reused if possible. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the DashboardSidebar section for the Dashboard page. This section includes a sidebar with navigation buttons for various sections such as Overview, Markets, Portfolio, and more. Each button displays an icon and label, and is wrapped in a <button> element with a data-section attribute. Ensure that the sidebar is styled according to the provided CSS and that it conditionally shows links based on persona access (e.g., 'Documents' for Financial Analyst only). Page access: shared by all personas (Administrator, Financial Analyst, General User).

Develop API service layer for chat, upload, and dashboard functionalities.

Set up routing shell with protected routes for persona-specific pages.

As a frontend developer, implement the DashboardHeader section for the Dashboard page. This section includes a header with a page title, current date and time, a search box, and several icon buttons for filters, view toggles, and notifications. The header also displays a user avatar and a tier badge. Ensure the header is styled according to the provided CSS and supports interactions like search input. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the OverviewCards section for the Dashboard page. This section displays key financial metrics such as Total Portfolio Value, Daily Change, Market Status, and Risk Score. Each card shows a label, value, and trend indicator. Ensure the cards are styled according to the provided CSS and that the trend indicators reflect the correct trend direction. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the MarketWidgets section for the Dashboard page. This section includes widgets for Market Overview, Ticker Tape, Economic Calendar, and Heatmap. Each widget displays a title and description, with a placeholder for chart previews. Ensure the widgets are styled according to the provided CSS and that the chart previews are correctly rendered. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the PortfolioSection for the Dashboard page. This section displays a sortable table of portfolio holdings, including symbols, shares, average cost, current price, gain/loss, and allocation. Implement sorting functionality for the table columns and ensure the section is styled according to the provided CSS. Note that this section is accessible by General User ONLY. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the AlertsAndWatchlist section for the Dashboard page. This section includes panels for Active Alerts and Watchlist. Alerts display symbols, trigger prices, and current status, while the watchlist shows symbols, prices, and changes. Ensure the section is styled according to the provided CSS and supports interactions like adding to the watchlist. Note that Alerts are accessible by Financial Analyst and General User, while Watchlist is accessible by Financial Analyst ONLY. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the PriceChart section for the Dashboard page. This section includes a chart with selectable timeframes (1D, 1W, 1M, 1Y) and a compare button. The chart displays a line graph with a gradient fill. Ensure the section is styled according to the provided CSS and supports timeframe selection. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the AnalyticsPanels section for the Dashboard page. This section displays panels for various technical analytics such as Volatility, Beta, and Moving Averages. Each panel includes a label, value, trend indicator, and a sparkline chart. Ensure the section is styled according to the provided CSS and that the sparkline charts are correctly rendered. Note that this section is accessible by Administrator and Financial Analyst. Page access: shared by all personas (Administrator, Financial Analyst, General User).

As a frontend developer, implement the AdminSidebar section for the Admin page. This section includes a responsive sidebar with navigation items such as 'Users', 'Roles & Access', 'System Settings', and more. It uses a mobile toggle button to open/close the sidebar and manages the active section state. Ensure that the sidebar is accessible only to the Administrator persona and that navigation links to restricted pages are conditionally shown. Page access: Administrator only.

As a frontend developer, implement the SessionsPageHeader section which includes a sidebar toggle button, a title 'Active Sessions', a subtitle, and action buttons for exporting and refreshing session data. This section is accessible by the Administrator persona only and should integrate with the DashboardSidebar from the Dashboard page. Page access: Administrator only.

As a frontend developer, implement the SettingsNav section for the Settings page. This section includes a navigation menu with icons for different settings categories such as Profile, Security, Notifications, etc. It uses SVG icons and manages state for mobile navigation toggle. Ensure that the navigation links are conditionally shown based on the Administrator persona access. Page access: Administrator only.

As a frontend developer, implement the AnalyticsHeader section for the Analytics page. This section includes a title, breadcrumb navigation, and interactive period tabs that allow users to switch between different time periods ('All Time', '1Y', '6M', '1M', '1W'). It also features action buttons for exporting and refreshing analytics data. This section is accessible by Administrator and Financial Analyst personas only. Ensure that the breadcrumb navigation conditionally displays links based on user access rights. This section depends on the DashboardSidebar from the Dashboard page. Page access: Administrator, Financial Analyst only.

As a frontend developer, implement the ProfileHeader section for the Profile page. This section includes an editable user profile header with avatar upload functionality. It uses state hooks to manage editing mode, user name, email, and avatar image. The avatar can be uploaded and previewed before saving. This section is accessible by Administrator and General User personas. Ensure it integrates with the Dashboard page as it depends on task ID 48e03cc4-1a6b-4722-a9e2-37dd03f9a457. Page access: Administrator, General User only.

As a frontend developer, implement the MarketsHeader section which includes a search bar with recent searches, market status indicators, and a list of major indices with their current values and changes. This section uses state hooks for managing search queries and view modes. It is accessible by Financial Analyst and General User personas. Ensure the search functionality triggers the onSearch callback with the correct symbol. This section depends on the DashboardSidebar from the Dashboard page. Page access: Financial Analyst, General User only.

As a frontend developer, implement the WatchlistPageHeader section for the Watchlist page. This section includes a header with the title 'My Watchlist', a subtitle, and metadata showing the item count and last updated time. It features a sort dropdown and a view toggle button to switch between grid and list views. The section also includes an export button. This page is accessible by Financial Analysts only. Page access: Financial Analyst only.

As a frontend developer, implement the ChatHeader section for the Chat page. This section includes a header with a title and buttons for starting a new conversation, viewing conversation history, and accessing chat settings. The buttons use SVG icons and are interactive, triggering functions like onNewConversation, onHistoryClick, and onSettingsClick. This section is accessible by Financial Analysts and General Users. Ensure the component integrates with the existing DashboardHeader from the Dashboard page. Page access: Financial Analyst, General User only.

As a frontend developer, implement the AlertsHeader section which includes a title, subtitle, breadcrumb navigation, and a 'Create Alert' button. The button uses the 'Plus' icon from 'lucide-react' and triggers the 'onCreate' callback when clicked. This section is accessible by Financial Analyst and General User personas. Ensure breadcrumb navigation is accessible and the 'Create Alert' button is functional. Page access: Financial Analyst, General User only.

As a frontend developer, implement the HistoryHeader section for the History page. This section includes a title and subtitle describing the page's purpose. It features a view toggle with buttons to switch between 'timeline' and 'list' views, using SVG icons for visual representation. The buttons update the viewMode state and provide accessible labels. This page is accessible by Financial Analysts only. Ensure the component integrates with the Dashboard page as per the dependency. Page access: Financial Analyst only.

As a frontend developer, implement the PortfolioHeader section which displays the total portfolio value, total gain/loss, and percentage gain/loss with trend indicators. This section uses the formatCurrency function to format values and conditionally applies CSS classes for positive or negative trends. It also shows the last updated timestamp. This section is accessible by General User ONLY and depends on the DashboardSidebar from the Dashboard page. Page access: General User only.

Implement middleware for authentication and persona-based route protection.

Implement authorization rules for API endpoints based on persona roles.

Develop API client service for frontend to interact with backend services.

Create integration tests for critical workflows including authentication and chat.

As a frontend developer, implement the AdminHeader section for the Admin page. This section includes a breadcrumb navigation, a dynamic title based on the current section, and action buttons such as 'Add User', 'Export', and 'Refresh'. The 'Add User' button should trigger a modal for adding new users. Ensure the header is styled according to the Admin page design and is accessible only to the Administrator persona. Page access: Administrator only.

As a frontend developer, implement the UserTable section for the Admin page. This section displays a table of users with sortable columns, inline editing capabilities, and bulk actions. It includes pagination controls and manages user selection state. Ensure the table is styled according to the Admin page design and is accessible only to the Administrator persona. Page access: Administrator only.

As a frontend developer, implement the RoleCards section for the Admin page. This section displays cards for each role with options to edit, delete, or create new roles. It includes a prompt for creating new roles and confirmation dialogs for deletions. Ensure the cards are styled according to the Admin page design and are accessible only to the Administrator persona. Page access: Administrator only.

As a frontend developer, implement the ConfigTabs section for the Admin page. This section includes tabbed navigation for different configuration panels such as 'API Keys' and 'Notification Settings'. It manages the active tab state and renders the corresponding panel content. Ensure the tabs are styled according to the Admin page design and are accessible only to the Administrator persona. Page access: Administrator only.

As a frontend developer, implement the ProfileSettings section for the Settings page. This section allows the Administrator to update their profile information, including name, organization, and avatar. It includes interactive elements such as file input for avatar upload and state management for form fields. Page access: Administrator only.

As a frontend developer, implement the PasswordSettings section for the Settings page. This section allows the Administrator to change their password with fields for current, new, and confirm password. It includes password strength calculation and validation logic. Page access: Administrator only.

As a frontend developer, implement the TwoFactorAuth section for the Settings page. This section allows the Administrator to enable or disable two-factor authentication. It includes modals for enabling/disabling 2FA and displays backup codes. Page access: Administrator only.

As a frontend developer, implement the NotificationPrefs section for the Settings page. This section allows the Administrator to configure email and in-app notification preferences. It includes toggle switches for different notification types. Page access: Administrator only.

As a frontend developer, implement the AppearanceSettings section for the Settings page. This section allows the Administrator to customize the application's appearance, including theme, language, and font size. It includes interactive elements for selecting options. Page access: Administrator only.

As a frontend developer, implement the IntegrationSettings section for the Settings page. This section allows the Administrator to manage third-party integrations. It includes toggles for connecting/disconnecting integrations and displays integration details. Page access: Administrator only.

As a frontend developer, implement the DangerZone section for the Settings page. This section includes critical actions such as exporting data, resetting data, and deleting the account. It features modals for confirmation and requires specific text input for destructive actions. Page access: Administrator only.

As a frontend developer, implement the AnalyticsMetrics section for the Analytics page. This section displays various financial metrics such as 'Total Portfolio Value', 'YTD Return', and 'Daily P&L', each with animated value updates and sparklines. The section uses state hooks to manage the animation of metric values and includes visual indicators for positive and negative changes. This section is accessible by Administrator and Financial Analyst personas only. Page access: Administrator, Financial Analyst only.

As a frontend developer, implement the AnalyticsCharts section for the Analytics page. This section includes multiple chart types such as AreaChart, PieChart, and ScatterChart using the Recharts library. It displays data on portfolio performance, asset allocation, and risk-return analysis. The section uses state hooks to manage chart legends and custom tooltips for enhanced data interaction. This section is accessible by Administrator and Financial Analyst personas only. Page access: Administrator, Financial Analyst only.

As a frontend developer, implement the AnalyticsPerformance section for the Analytics page. This section provides a tabbed interface to view performance data by asset class, sector, and region. It includes sorting and filtering capabilities, allowing users to interactively manage the displayed data. The section uses useMemo for efficient data processing and state hooks for managing active tabs and sort configurations. This section is accessible by Administrator and Financial Analyst personas only. Page access: Administrator, Financial Analyst only.

As a frontend developer, implement the AnalyticsActivity section for the Analytics page. This section displays a timeline of recent financial activities with filtering options for different event types such as 'Buy', 'Sell', and 'Dividend'. It uses state hooks to manage the filter and the number of visible events. The section is styled with color-coded event types and includes a load more functionality. This section is accessible by Administrator and Financial Analyst personas only. Page access: Administrator, Financial Analyst only.

As a frontend developer, implement the MessageList section for the Chat page. This section displays a list of messages with timestamps formatted using the formatTimestamp function. It handles empty states with a prompt to start a conversation and supports message actions like copy and retry. The component dynamically styles messages based on the sender's role and message status. This section is accessible by Financial Analysts and General Users. Page access: Financial Analyst, General User only.

As a frontend developer, implement the TypingIndicator section for the Chat page. This section shows an animated typing indicator with three dots to indicate when a user is typing. It is a simple visual component that enhances the chat experience. This section is accessible by Financial Analysts and General Users. Page access: Financial Analyst, General User only.

As a frontend developer, implement the FileUploadList section for the Chat page. This section displays a list of uploaded files with icons representing file types, using the getFileIcon function. It allows users to remove files with an interactive button. This section is accessible by Financial Analysts and General Users. Page access: Financial Analyst, General User only.

As a frontend developer, implement the FileUploadZone section for the Chat page. This section allows users to drag and drop files or click to browse for file uploads. It supports multiple file types and provides visual feedback when files are dragged over the zone. This section is accessible by Financial Analysts and General Users. Page access: Financial Analyst, General User only.

As a frontend developer, implement the ChatInputArea section for the Chat page. This section includes a resizable textarea for message input, with auto-resizing functionality based on content. It supports sending messages with Ctrl+Enter. This section is accessible by Financial Analysts and General Users. Page access: Financial Analyst, General User only.

As a frontend developer, implement the AlertsFilter section which includes status and type filters, a search input, and a sort dropdown. The section uses 'lucide-react' icons for search and clear actions. It manages filter state using the 'setFilters' callback and supports clearing all filters. This section is accessible by Financial Analyst and General User personas. Page access: Financial Analyst, General User only.

As a frontend developer, implement the AlertsCards section which displays a grid of alert cards. Each card shows alert details like symbol, type, condition, status, and creation date. It includes actions for editing, deleting, and dismissing alerts using 'lucide-react' icons. The section handles empty states and is accessible by Financial Analyst and General User personas. Page access: Financial Analyst, General User only.

As a frontend developer, implement the AlertsActions section which includes an alert form for creating or editing alerts and a confirmation dialog for deleting alerts. The form manages state for symbol, type, and condition fields and uses 'lucide-react' icons for UI elements. This section is accessible by Financial Analyst and General User personas. Page access: Financial Analyst, General User only.

As a frontend developer, implement the AlertsPagination section which provides pagination controls for navigating through alert pages. It includes input for direct page navigation and buttons for previous and next page actions using 'lucide-react' icons. This section is accessible by Financial Analyst and General User personas. Page access: Financial Analyst, General User only.

As a frontend developer, implement the HistoryFilters section for the History page. This section includes search input, date range, session type, and sort by filters, each with corresponding SVG icons and accessible labels. The filters update their respective states and include a clear filters button. This page is accessible by Financial Analysts only. Page access: Financial Analyst only.

As a frontend developer, implement the SessionsList section for the History page. This section displays a list of sessions in either 'timeline' or 'list' view based on the viewMode state. Each session item includes a type badge, duration, title, summary, and metadata such as date, questions, insights, and documents. The list is interactive, allowing selection of a session. This page is accessible by Financial Analysts only. Page access: Financial Analyst only.

As a frontend developer, implement the PortfolioControls section which includes time period selection buttons and an export menu for CSV and PDF formats. This section handles state for the export menu and time period selection, and provides buttons for adding new holdings. This section is accessible by General User ONLY. Page access: General User only.

As a frontend developer, implement the PortfolioAllocationChart section which displays a donut chart of asset allocation. This section uses SVG for rendering and includes interactive features such as hover effects and segment click handling. It manages state for hovered segments and tooltip positioning. This section is accessible by General User ONLY. Page access: General User only.

As a frontend developer, implement the PortfolioMetrics section which displays various portfolio metrics such as total holdings, average return, YTD performance, and volatility. This section uses sparklines for visualizing trends and calculates metrics based on holdings data. This section is accessible by General User ONLY. Page access: General User only.

As a frontend developer, implement the PortfolioHoldingsList section which displays a sortable table of holdings. This section includes sorting functionality, filter badges, and integrates with PortfolioHoldingActions for editing and removing holdings. This section is accessible by General User ONLY. Page access: General User only.

As a frontend developer, implement the PortfolioEmpty section which displays a message and a call-to-action button when there are no holdings. This section includes an SVG illustration and a button to add the first holding. This section is accessible by General User ONLY. Page access: General User only.

As a frontend developer, implement the ResearchHeader section which includes a page title and subtitle, and a view toggle button group to switch between 'list' and 'grid' view modes. Ensure the toggle buttons update the viewMode state and reflect the active state visually. This section is accessible by Financial Analysts only and depends on the Markets page implementation. Page access: Financial Analyst only.

As a frontend developer, implement the DocumentsTitle section which includes a heading displaying 'Documents' and a badge showing the number of documents. It also features an 'Upload' button that scrolls to the UploadZone section when clicked. This section is accessible only by Financial Analysts. Page access: Financial Analyst only.

As a Backend Developer, implement API endpoints for managing documents, including upload, list, preview, and delete functionalities. Ensure endpoints are secure and accessible only by Financial Analysts.

As a Backend Developer, implement API endpoints for chat functionalities, including message streaming, history retrieval, and file uploads. Ensure endpoints support markdown, financial citations, and are accessible by Financial Analysts and General Users.

As a Backend Developer, implement API endpoints for managing user portfolios, including retrieval, update, and analytics functionalities. Ensure endpoints are secure and accessible only by General Users.

As a Backend Developer, implement API endpoints for managing alerts, including creation, update, and deletion functionalities. Ensure endpoints are secure and accessible by Financial Analysts and General Users.

As a Backend Developer, implement API endpoints for accessing research reports, including retrieval and filtering functionalities. Ensure endpoints are secure and accessible only by Financial Analysts.

As a Backend Developer, implement API endpoints for accessing user session history, including retrieval and filtering functionalities. Ensure endpoints are secure and accessible only by Financial Analysts.

As a Backend Developer, implement API endpoints for managing watchlists, including add, remove, and list functionalities. Ensure endpoints are secure and accessible only by Financial Analysts.

As a Backend Developer, implement API endpoints for accessing analytics data, including retrieval and filtering functionalities. Ensure endpoints are secure and accessible by Administrator and Financial Analysts.

As a Backend Developer, implement API endpoints for managing user sessions, including retrieval, filtering, and termination functionalities. Ensure endpoints are secure and accessible only by Administrators.

As a Backend Developer, implement API endpoints for admin functionalities, including user management, role configuration, and system settings. Ensure endpoints are secure and accessible only by Administrators.

As a Tech Lead, verify the end-to-end integration between the Dashboard frontend implementation and the Dashboard backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the Profile frontend implementation and the Profile backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

Set up CI/CD pipeline for automated deployment and health checks.

As a frontend developer, implement the AddUserModal section for the Admin page. This modal allows administrators to add new users by filling out a form with fields for email, name, role, and password. It includes client-side validation and error handling. Ensure the modal is styled according to the Admin page design and is accessible only to the Administrator persona. Page access: Administrator only.

As a frontend developer, implement the EditRoleModal section for the Admin page. This modal allows administrators to edit role permissions and status. It includes a toggle for enabling/disabling roles and checkboxes for managing permissions. Ensure the modal is styled according to the Admin page design and is accessible only to the Administrator persona. Page access: Administrator only.

As a frontend developer, implement the ApiKeysPanel section for the Admin page. This panel displays the current API key with options to copy or regenerate it. It includes a confirmation dialog for regeneration and manages the copied state. Ensure the panel is styled according to the Admin page design and is accessible only to the Administrator persona. Page access: Administrator only.

As a frontend developer, implement the NotificationSettings section for the Admin page. This section allows administrators to configure notification preferences such as email, SMS, and in-app alerts. It includes toggles for each notification type and a dropdown for alert frequency. Ensure the settings are styled according to the Admin page design and are accessible only to the Administrator persona. Page access: Administrator only.

As a frontend developer, implement the ChatInputActions section for the Chat page. This section includes buttons for sending messages, opening an emoji picker, and starting voice input. The send button is conditionally enabled based on the canSend prop. This section is accessible by Financial Analysts and General Users. Page access: Financial Analyst, General User only.

As a frontend developer, implement the SessionDetail section for the History page. This section provides detailed information about a selected session, including type badge, timestamp, title, summary, key findings, metrics, transcript, and related files. It features a close button to exit the detail view. This page is accessible by Financial Analysts only. Page access: Financial Analyst only.

As a frontend developer, implement the PortfolioHoldingActions component which provides edit and remove actions for each holding. This component includes a confirmation dialog for removal and manages its own state for dialog visibility. This section is accessible by General User ONLY. Page access: General User only.

As a frontend developer, implement the ResearchFilters section which includes a search bar, category, date range, and sort dropdowns, and a clear filters button. Ensure the filters update the respective states and display active filters as chips. This section is accessible by Financial Analysts only. Page access: Financial Analyst only.

As a frontend developer, implement the ReportsCards section which displays a list or grid of report cards based on the viewMode. Each card should be clickable, showing report details like title, description, author, and date. Ensure accessibility features like keyboard navigation are supported. This section is accessible by Financial Analysts only. Page access: Financial Analyst only.

As a frontend developer, implement the DocumentsControls section which includes search functionality, filter and sort options, and view toggles between list and grid. This section uses state hooks to manage view, filter, and sort states. It is accessible only by Financial Analysts. Page access: Financial Analyst only.

As a frontend developer, implement the UploadZone section which allows users to drag and drop files or click to browse files for upload. It supports PDF, CSV, Excel, and image files. This section uses state hooks to manage drag-over state and is accessible only by Financial Analysts. Page access: Financial Analyst only.

As a frontend developer, implement the DocumentsList section which displays a list of documents with details such as name, type, size, date, and status. It uses a sample list of documents and is accessible only by Financial Analysts. Page access: Financial Analyst only.

As a Tech Lead, verify the end-to-end integration between the Chat frontend implementation and the Chat backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the Portfolio frontend implementation and the Portfolio backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the Research frontend implementation and the Research backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the History frontend implementation and the History backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the Watchlist frontend implementation and the Watchlist backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the Analytics frontend implementation and the Analytics backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the Sessions frontend implementation and the Sessions backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the Admin frontend implementation and the Admin backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

Set up global state management for shared data across the application.

Develop reusable form utilities for validation and state management.

As a frontend developer, implement the ReportViewer section which displays detailed information about a selected report, including title, author, date, category, and key findings. Include a close button to exit the viewer. This section is accessible by Financial Analysts only. Page access: Financial Analyst only.

As a frontend developer, implement the UploadProgress section which displays the progress of file uploads, including file name, percentage completed, speed, and remaining size. It uses static state for demonstration and is accessible only by Financial Analysts. Page access: Financial Analyst only.

As a frontend developer, implement the DocumentPreview section which shows a preview of a selected document with metadata and AI-generated insights. It includes actions like 'Analyze' and 'Add to Chat'. This section is accessible only by Financial Analysts. Page access: Financial Analyst only.

As a Tech Lead, verify the end-to-end integration between the Documents frontend implementation and the Documents backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a Tech Lead, verify the end-to-end integration between the Alerts frontend implementation and the Alerts backend API. Ensure data flows correctly, API responses are handled properly in the UI, and all interactions work as expected.

As a frontend developer, implement the ReportActions section which provides action buttons for saving, sharing, downloading, and printing a report. Ensure each button triggers the appropriate function passed as props. This section is accessible by Financial Analysts only. Page access: Financial Analyst only.