feat: add dynamic text search/filter for tasks

[Copilot]

Users had no way to search or filter tasks in the current list. This adds a live text filter that narrows the visible task list as the user types.

Changes

• frontend/index.html — added #searchInput field between the add-task form and #taskList
• frontend/style.css — styled #searchInput using existing CSS custom properties to match the current design system
• frontend/script.js
  • allTasks[] caches the full task list from the API
  • filterTasks() performs a case-insensitive substring match on task.title, bound to the input event for live filtering
  • fetchTasks() now calls filterTasks() instead of renderTasks(allTasks) directly, preserving any active filter across toggle/delete refreshes
  • Submitting a new task clears searchInput before re-rendering so the new task is always visible

function filterTasks() {
  const query = searchInput.value.trim().toLowerCase();
  const filtered = allTasks.filter(task =>
    task.title.toLowerCase().includes(query)
  );
  renderTasks(filtered);
}

searchInput.addEventListener('input', filterTasks);

Original prompt

Start implementation

The user has attached the following file paths as relevant context:

• .github\copilot-instructions.md

[Chronological Review: The conversation began with the user requesting an analysis of the project structure and commands to run the application using Docker Compose. The user then shifted focus to opening the FrontEnd app in the integrated browser of VS Code. Next, the user requested the addition of a search functionality for tasks within the current list, specifying that it should include a dynamic text filter. The user concluded by requesting to start the implementation of this feature.]

[Intent Mapping:

1. "Analiza la estructura del proyecto y ejecuta los comandos necesarios para levantar la aplicación utilizando Docker Compose." - User wants to analyze the project structure and run the application.
2. "Abre la app FrontEnd en el navegador integrado de vs code." - User requests to open the FrontEnd app in VS Code.
3. "Agrega funcionalidad que permita al usuario buscar tareas específicas dentro de la lista actual mediante un filtro de texto." - User wants to implement a search functionality for tasks.
4. "Start implementation." - User indicates readiness to begin the implementation of the search feature.]

[Technical Inventory:

• Docker Compose: Used for container orchestration to run the application.
• VS Code: Integrated development environment for opening the FrontEnd app.
• JavaScript/React (implied): Likely technologies for implementing the search functionality.]

[Code Archaeology: No specific files or code changes have been discussed yet, but the search functionality will likely involve modifications to task list components and possibly state management.]

[Progress Assessment:

• Completed Tasks: None explicitly completed yet.
• Partially Complete Work: User has outlined the requirements for the search functionality and indicated readiness to start implementation.
• Validated Outcomes: No features have been confirmed working yet.]

[Context Validation: All necessary context for continuing the work on the search functionality is captured, including user requirements and the current focus on implementation.]

[Recent Commands Analysis:

• Last Agent Commands: User requested to "Start implementation."
• Tool Results Summary: No tool results were generated as the conversation focused on user requests.
• Pre-Summary State: The agent was preparing to begin the implementation of the search functionality when the token budget was exceeded.
• Operation Context: The commands executed relate directly to the user's goal of enhancing the task management application with a search feature.]

1. Conversation Overview: - Primary Objectives: 1. "Analiza la estructura del proyecto y ejecuta los comandos necesarios para levantar la aplicación utilizando Docker Compose." 2. "Abre la app FrontEnd en el navegador integrado de vs code." 3. "Agrega funcionalidad que permita al usuario buscar tareas específicas dentro de la lista actual mediante un filtro de texto." 4. "Start implementation." - Session Context: The conversation has progressed from analyzing project structure and running the application to implementing a search feature for tasks. - User Intent Evolution: The user has moved from general project setup to specific feature implementation, indicating a clear focus on enhancing user experience.

2. Technical Foundation:

• Docker Compose: Used for orchestrating application containers.
• VS Code: Integrated development environment for development tasks.
• JavaScript/React (implied): Technologies likely involved in the task list and search functionality.

3. Codebase Status:

• No specific files have been discussed yet, but the implementation of the search functionality will require updates to task list components.

4. Problem Resolution:

• Issues Encountered: No specific technical problems have been reported yet.
• Solutions Implemented: No solutions have been implemented as the focus is on planning the search feature.
• Debugging Context: No ongoing troubleshooting efforts have been mentioned.
• Lessons Learned: No insights have been documented yet.

5. Progress Tracking:

• Completed Tasks: None yet.
• Partially Complete Work: User has defined the search functionality requirements and is ready to start implementation.
• Validated Outcomes: No features have been validated yet.

6. Active Work State:

• Current Focus: User is ready to start implementing the search functionality for tasks.
• Recent Context: The last few exchanges focused on defining and preparing for the implementation of the search feature.
• Working Code: No specific code snippets have been discussed yet.
• Immediate Context: The user is poised to begin coding the search functionality.

7. Recent Operations:

• Last Agent Commands: User requested to "Start implementation."
• Tool Results Summary: No tool results were generated as the conversation focused on user requests.
• Pre-S...

Created from VS Code.