billing software

As a Frontend Developer, implement the approved Authentication page design and the task-owned sections below. Implementation contract: - Outcome: Implement Authentication page - Requirement sources: - src-621bddac110449e2 - Owned behavior: - Authenticate Owner and Cashier users via Supabase Auth - Route authenticated Owner to /owner-dashboard and Cashier to /pos-screen - Cohesive login form supporting authentication with Supabase. - Interfaces: - Supabase Auth API - Provide auth.form: Cohesive login form supporting authentication with Supabase. - State transitions: - User submits login form -> Supabase Auth validates -> User redirected based on role - Failure and safety behavior: - Display auth errors (invalid credentials, network failure, account disabled) - Web research: - RESEARCH BLOCKER: Official Supabase authentication documentation is not directly cited, so the implementation claims for authentication contract, scopes, API behaviors, failure modes, and limits are not confirmed. Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - Authentication page renders with AuthenticationForm - Form includes email, password, 'Remember Me', and submit button - Design adheres to provided CSS - Form integrates with Supabase Auth - Handles success and failure responses - Routes users based on role - Capability auth.form implements Cohesive login form supporting authentication with Supabase. and is verified through its declared interfaces.

As a Frontend Developer, implement the approved POS Screen page design and the task-owned sections below. Implementation contract: - Outcome: Implement POS Screen page - Requirement sources: - src-9a38c6fb1e7c7ea3 - src-85ef509c48844658 - src-8560ff16a309cf05 - Owned behavior: - Display and filter categorized menu items - Emit item selection events Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - POS Screen page renders with POSMenuItems section - Search and category filters function correctly - Menu items display correct information - Clicking an item adds it to the cart

As a Frontend Developer, implement the approved POS Screen page design and the task-owned sections below. Implementation contract: - Outcome: Implement POSCart section on POS Screen - Requirement sources: - src-65b4d92ef8930c25 - src-d3643c4932957582 - src-4b6d512197cc8473 - src-3c1dfd3102f28544 - src-63f3d93a6eca5dd1 - src-61bff96cae04a87b - Owned behavior: - Display cart items with live quantity controls and per-item totals - Calculate and display subtotal, tax, discount, and grand total in real-time - Allow cashier to adjust quantities, remove items, and apply discounts - Accept payment method selection - Validate cart before order creation - Trigger order save workflow and print dialog on CONFIRM & PRINT click - Interfaces: - consumed API, data, or event contracts - State transitions: - Cart state updates on item addition/removal - Order state transition on CONFIRM & PRINT - Failure and safety behavior: - Empty cart error - Invalid quantity error - Payment method not selected error Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - Render POSCart section on POS Screen - Display cart items with live quantity controls - Calculate and display totals in real-time - Allow cashier to adjust cart - Validate and save order on CONFIRM & PRINT

As a Frontend Developer, implement the approved Owner Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement Owner Dashboard Page Header - Requirement sources: - src-e64612b5d7f44062 - src-2bdebcc89bde8f11 - Owned behavior: - Display page title and role - Provide orientation to available features Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - The Owner Dashboard page must render the OwnerDashboardPageHeader component exactly once. - The header must display the page title, role badge, introductory text, and quick action hints as per the design. - The design structure and theme must be preserved. - The page must be accessible only to the 'Owner' persona, as per the access context.

As a Frontend Developer, implement the approved Owner Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement Menu Management Section for Owner Dashboard - Requirement sources: - src-0a563d11b71a7a13 - src-c9e385a66b27dc1c - src-9b4b0341f5d3099c - src-e81f4cab1ba06b4e - src-e7cf60b8b4538e75 - Owned behavior: - CRUD operations for categories and items - Feedback messaging for save success/failure - Interfaces: - Persist menu changes to database - State transitions: - Owner enters category or menu item details - Entered details are saved - Entered details fail to save - Failure and safety behavior: - Save operation fails due to validation errors or backend issues Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - MenuManagementSection renders once - Tabbed interface with 'Categories' and 'Menu Items' - CRUD operations with validation and feedback - Design adheres to CSS styles - Backend integration for persisting changes - Access restricted to 'Owner' persona

As a Frontend Developer, implement the approved Owner Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement SalesDataSection for Owner Dashboard - Requirement sources: - src-9c4902aa652b7fc3 - src-8161551eb53b8057 - src-e0c645169e78755f - src-f00651870bf1c289 - Owned behavior: - select time period filter - apply filter to sales data - view filtered sales metrics - view filtered order list - Interfaces: - orders data API - State transitions: - Owner switches to the sales data view - Owner selects a Today/This Week/This Month filter - Failure and safety behavior: - display empty state when no orders exist for selected period Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - observable task-owned checks

As a Frontend Developer, implement the approved Owner Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement CategoryManagementTab for Owner Dashboard - Requirement sources: - src-0a563d11b71a7a13 - Owned behavior: - add category - edit category - delete category - Failure and safety behavior: - display error message when validation fails Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - observable task-owned checks

As a Frontend Developer, implement the approved Owner Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement FeedbackMessage for Owner Dashboard - Requirement sources: - src-c9e385a66b27dc1c - Owned behavior: - display success message - display error message - automatic dismissal - manual dismissal Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - observable task-owned checks

As a Frontend Developer, implement the approved Owner Dashboard page design and the task-owned sections below. Implementation contract: - Outcome: Implement Owner Dashboard page - Requirement sources: - src-9b4b0341f5d3099c - src-5ed5b68cea48810c - src-082d22d29c11cffb - src-77cc047ff6e3f123 - Owned behavior: - CRUD operations for menu items - Display of recent orders - Sales summary display - Time period filtering Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - Owner Dashboard renders once - MenuItemManagementTab supports CRUD with validation - OrderList displays orders correctly - SalesSummary shows sales metrics - TimePeriodFilter allows period selection

As a Frontend Developer, implement the approved Bills Page page design and the task-owned sections below. Implementation contract: - Outcome: Implement Bills Page - Requirement sources: - src-32495e82602a9b30 - src-beabfafa4ab676e5 - src-87807f86bd286ddb - src-5c03b87c79086486 - src-aca502db6aea55a2 - src-8e25fabf176b0705 - src-61bff96cae04a87b - Owned behavior: - search and filter bills - select bill to trigger detail panel - display selected bill invoice - click REPRINT button - print dialog opens - handle print failure - show error state - Interfaces: - fetch bill data from backend - canonical order and order_items records - State transitions: - bill selection state change - Selected bill cannot be shown or reprinted - Failure and safety behavior: - handle no-results and empty states - Invoice not found or unable to print Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - observable task-owned checks

As a Frontend Developer, implement the approved Bills Page page design and the task-owned sections below. Implementation contract: - Outcome: Implement SearchFilterControl for Bills Page - Requirement sources: - src-b1f1365f8ef659dd - Owned behavior: - search input interaction - date filter button toggle - State transitions: - searchQuery state update - dateFilter state update Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - SearchFilterControl renders once on Bills Page - Search input updates searchQuery state - Date filter buttons toggle active state and update dateFilter - Design tokens applied correctly - Access restricted to Cashier persona

As a Frontend Developer, implement the approved Invoice Generation page design and the task-owned sections below. Implementation contract: - Outcome: Implement Invoice Generation page - Requirement sources: - src-61bff96cae04a87b - Owned behavior: - Display a complete, print-friendly restaurant invoice - Interfaces: - Consume invoice.display: Display print-friendly invoice document. - State transitions: - Print dialog opens when print button is clicked - Failure and safety behavior: - Print dialog fails to open Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - InvoiceDisplay component renders once on Invoice Generation page - Displays restaurant header, order details, and payment information - Supports browser print functionality - Layout optimized for screen and print - Accessible to Cashier persona with login access - Capability invoice.display implements Display print-friendly invoice document. and is verified through its declared interfaces.

As a Frontend Developer, implement the approved Bill Creation page design and the task-owned sections below. Implementation contract: - Outcome: Implement Bill Creation page - Requirement sources: - src-85331ac557c0de3c - src-2dc4ff0d81bdcc41 - src-61bff96cae04a87b - Owned behavior: - Display cart items - Show calculated totals - Select payment method - Submit form and save order - Trigger print dialog on success - Interfaces: - Supabase API for order persistence - State transitions: - Order and order items saved - Print dialog opened - Failure and safety behavior: - Display error on validation/save failure - Handle print dialog open/close Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - observable task-owned checks