red-a

As a Frontend Developer, implement the approved Todo List page design and the task-owned sections below. Implementation contract: - Outcome: Implement Todo List page - Requirement sources: - src-3e67214c50b02f99 - src-e0893c916cd140fc - src-4c3fb7dbf2a79746 - src-fe0a28089d09f4e5 - src-90358274cef30b7c - Owned behavior: - Load task list on component mount - Submit task creation form - Mark task as complete - Handle form validation - Refresh task list after changes - Display loading, error, and empty states - Cancel task creation - Provide form field feedback - Create Task (Personal User) — trigger: User adds a new task; inputs: Task title, Task description, Due date; outcomes: Task is added to the task list - Complete Task (Personal User) — trigger: User marks a task as complete; inputs: Task identifier; outcomes: Task is marked as completed - View Tasks (Personal User) — trigger: User opens the task list; outcomes: Display list of tasks - Implement the accepted behavior View Tasks with authoritative outcomes and failure handling. - Interfaces: - tasks API for loading, creation, and completion - Input contract for Create Task: Task title, Task description, Due date - Input contract for Complete Task: Task identifier - Consume task.creation: Handle creation of new tasks with durable state. - Consume task.completion: Handle marking tasks as complete with durable state. - Provide accepted.behavior.de334902b141f772: Implement the accepted behavior View Tasks with authoritative outcomes and failure handling. - State transitions: - Transition to loading state - Display error on load failure - Display error on creation failure - Display error on completion failure - Show success feedback - Clear form after successful submission - When User adds a new task: New task entry - When User marks a task as complete: Task status update - When User opens the task list: Display list of tasks - Failure and safety behavior: - Task list load failure - Task creation failure - Task completion failure - If Create Task cannot complete: Task not added. - If Complete Task cannot complete: Task not marked as complete. - If View Tasks cannot complete: Tasks not displayed. Acceptance criteria: - The task-owned behavior is implemented and verified without undeclared mocks or downstream assumptions. - The Todo List page must render exactly once - Display the task list with title, description, and due date - Allow input and submission of new tasks with validation feedback - Toggle tasks between pending and completed states with visual indicators - Handle backend integration for task list loading, task creation, and task completion - When User adds a new task, Personal User produces Task is added to the task list. - Create Task includes the required human touchpoint: Task creation interface. - When User marks a task as complete, Personal User produces Task is marked as completed. - Complete Task includes the required human touchpoint: Task completion interface. - When User opens the task list, Personal User produces Display list of tasks. - View Tasks includes the required human touchpoint: Task list interface. - Capability task.creation implements Handle creation of new tasks with durable state. and is verified through its declared interfaces. - Capability task.completion implements Handle marking tasks as complete with durable state. and is verified through its declared interfaces. - Capability accepted.behavior.de334902b141f772 implements Implement the accepted behavior View Tasks with authoritative outcomes and failure handling. and is verified through its declared interfaces.