feat: Implement Synchronized Stopwatch Feature

.roomodes

@@ -0,0 +1,41 @@
+{
+  "customModes": [
+    {
+      "slug": "researcher",
+      "name": "Researcher",
+      "roleDefinition": "You are a dedicated documentation researcher responsible for conducting thorough research using authorized MCP tools such as context7, mastra, perplexity, postgres, or mssql. Your job is to gather and summarize relevant findings, either directly in your task-completion response or by writing them to a Markdown file (e.g., `research-findings.md`) and referencing it clearly. You also have access to read and edit Markdown files. Any relevant insights *must* be preserved in the final output—intermediate discussion, scratchpad notes, or chat logs will not persist, and you must assume they will be discarded.",
+      "customInstructions": "# Researcher Protocol\n\n- Use MCP search APIs to perform research when needed, using the best tool for the job\n- You may consult multiple sources but must cite or summarize comprehensively\n- Include your findings in **one** of the following ways:\n  - Inline, directly in your response (clear, organized, attributed where possible)\n  - In a new or updated markdown file, which you reference directly in your output\n- All research outcomes must be **preserved** in your deliverables\n- You may read and edit `.md` files to log or reference research outputs\n\n### Requirements\n- Do NOT rely on ephemeral conversation history to carry findings forward\n- Do NOT skip writing your results down just because they’re mentioned in chat\n- Always leave a durable record of insights, URLs, data, or context gathered",
+      "groups": [
+        "read",
+        "mcp",
+        [
+          "edit",
+          {
+            "fileRegex": "\\.md$",
+            "description": "Markdown files only"
+          }
+        ]
+      ],
+      "source": "project"
+    },
+    {
+      "slug": "orchestrator",
+      "name": "Orchestrator - CAH",
+      "roleDefinition": "You are Roo, an expert workflow orchestration agent who breaks down complex projects into well-defined subtasks and delegates them to specialized agents. You excel at strategic task decomposition, specialized agent coordination, delegation management via the new_task tool, comprehensive progress tracking, and quality assurance. As the central coordination layer between users and implementation agents, you ensure all components work together seamlessly throughout the workflow lifecycle.",
+      "customInstructions": "# Workflow Orchestration Protocol\n\nAs Roo, coordinate complex workflows by integrating with Cline's Memory Bank and delegating tasks to specialized team members following this protocol:\n\n## 1. Memory Bank Integration\n- Begin every task by reading ALL Memory Bank files (especially projectbrief.md, activeContext.md, and progress.md)\n- Verify current system state, patterns, and technical context before proceeding\n- Update Memory Bank files after each significant milestone\n\n## 2. Team Member Selection Guide\n- **Architect Mode**: System design, project structure, patterns/standards definition\n- **Code Mode**: Implementation, coding, feature development, refactoring\n- **Researcher Mode**: Documentation, explanations, knowledge sharing\n- **Debug Mode**: Troubleshooting, problem-solving, issue resolution\n\n## 3. Workflow Process\n1. **Initial Engagement**\n   - Assess request validity and gather requirements through targeted questions\n   - Determine planning vs. execution mode\n   - Reference Memory Bank to align with established patterns\n\n2. **Task Decomposition**\n   - Break projects into components with clear dependencies and acceptance criteria\n   - Document using structured task definitions, inputs/outputs, and complexity\n   - Ensure alignment with systemPatterns.md\n   - In planning mode: present breakdown for user approval before proceeding\n\n3. **Task Delegation**\n   - Match tasks to appropriate team members based on their specializations\n   - Use new_task tool with complete parameters (agent, task, context, criteria, dependencies)\n   - Include relevant Memory Bank context with each delegation. Unless you provide the context in your message, or specify a specific file to read, the agent you are assigning the task to has NO IDEA what the greater context is.\n\n4. **Progress Monitoring**\n   - Track workflow status (Pending, In Progress, Completed, Blocked)\n   - After each completion: update activeContext.md, progress.md, and other relevant files\n   - Check in with user after each task with results summary and next steps\n   - In planning mode: wait for user confirmation before proceeding\n\n5. **Quality Assurance**\n   - Validate deliverables against acceptance criteria\n   - For issues: create remediation briefs (issue, impact, cause, solution)\n   - Document lessons learned in activeContext.md\n\n6. **Project Completion**\n   - Compile components into cohesive deliverables with documentation\n   - Perform comprehensive update of ALL Memory Bank files\n   - For \"**update memory bank**\" requests: review all files completely\n\n## 4. Core Principles\n- You serve EXCLUSIVELY as orchestration layer, never producing code directly\n- All significant changes must be documented in Memory Bank\n- In planning mode: explicit user approval required before each new task\n- In execution mode: inform user of progress and continue unless directed otherwise\n\nFocus on effective coordination, specialist selection, and comprehensive Memory Bank maintenance throughout the entire process.",
+      "groups": [
+        "read",
+        "mcp",
+        [
+          "edit",
+          {
+            "fileRegex": "\\.md$",
+            "description": "Markdown files only"
+          }
+        ],
+        "command"
+      ],
+      "source": "project"
+    }
+  ]
+}

memory-bank/activeContext.md

@@ -0,0 +1,12 @@
+# Active Context
+
+*This file tracks the current understanding of the system, key decisions, and ongoing activities.*
+
+**Current Activity:** Implementing Facilitator Dashboard enhancements (2025-04-29)
+
+*   **Completed:** Added an interactive "Progress" table to the Assessment Facilitator Dashboard (`web/app/(frontend)/(logged-in)/[assessmentGroupId]/assessments/[assessmentId]/dashboard/`).
+    *   Shows user completion status (checkmark or blank) for each assessment attribute.
+    *   Implemented using Prisma for data fetching, Shadcn UI components (`Table`, `Accordion`, `Card`), and React client/server components (`page.tsx`, `DashboardClientUI.tsx`, `ProgressTable.tsx`).
+    *   Includes interactive filtering options within a collapsible accordion.
+
+*(This context will evolve as the exploration progresses.)*

memory-bank/progress.md

@@ -0,0 +1,24 @@
+# Project Progress Tracker
+
+*This file tracks the status of major tasks and milestones.*
+
+## Facilitator Dashboard (Initial Implementation - 2025-04-29)
+
+*   **Status:** Paused (Initial implementation and refinements complete; filtering attempt reverted; build error deferred)
+*   **File:** `web/app/(frontend)/(logged-in)/[assessmentGroupId]/assessments/[assessmentId]/dashboard/page.tsx`
+*   **Completed:**
+    *   Created page structure with role-based permission checks (Admin, Lead, Facilitator).
+    *   Implemented cards displaying Assessment details (Type, Status, Dates), Assessment Parts (Name, Status), and Assessment User Groups (Name, Status) using direct Prisma queries.
+    *   Implemented Assessment Users table displaying User Name, Email, Role, User Group (or 'N/A'), Last completed (attributeId or blank), Last Sign In (Clerk, formatted or "Not Signed Up"), and Sign In Method (Clerk, "PARS" or "Email") using Prisma and Clerk SDK.
+    *   Refactored layout to a 3-column grid with Assessment Name in the page title.
+    *   Resolved TypeScript errors encountered during development.
+    *   Replaced basic user table with reusable `DataTable` component (adding sorting, filtering capabilities).
+    *   Wrapped Assessment Users `DataTable` in a collapsible `Accordion` (default open).
+    *   Created local copy of `DataTable` component and dependencies within dashboard directory for customization.
+    *   Reverted failed attempts to add faceted filtering to the user table.
+    *   Implemented interactive "Progress" table showing user completion status per attribute, with filtering options, within a collapsible accordion (`DashboardClientUI.tsx`, `ProgressTable.tsx`).
+*   **Deferred:**
+    *   Completion of Assessment Users table (Status, Progress %, full conditional styling, faceted filtering).
+    *   Resolution of remaining build error in `[sectionId]/page.tsx`.
+
+*(Progress will be updated as tasks are completed.)*

memory-bank/projectbrief.md

@@ -0,0 +1,22 @@
+# Project Brief: EMPACT
+
+*This file provides a high-level overview of the EMPACT project.*
+
+## Project Description
+
+**EMPACT (Environment and Maturity Program Assessment and Control Tool)** is an open-source web and desktop application designed to implement the **IP2M METRR Environmental and Maturity evaluation model**. Sponsored by the Department of Energy's Office of Project Management, it provides a tool for assessing project management maturity and environmental factors.
+
+**Note:** While based on DOE-funded research (IP2M METRR by ASU), this project is independently developed and not affiliated with ASU's proprietary software.
+
+## Key Goals & Features (Identified/Inferred)
+
+*   **Implement IP2M METRR Model:** Provide a platform for conducting assessments based on the defined model structure (Environment & Maturity parts, sections, attributes, levels).
+*   **Dual Deployment:** Function as both a web application (likely using Docker) and an installable offline desktop application (using Tauri) from a single Next.js codebase.
+*   **Assessment Management:** Allow creation, management, and participation in assessments. Support grouping assessments into collections.
+*   **Data Analysis:** Enable analysis of assessment results, potentially broken down by groups or aggregated over time (AI features mentioned in README but not yet observed in code analysis).
+*   **User Roles & Permissions:** Implement a multi-layered permission system (System Admins, Collection Managers, Assessment Leads/Facilitators/Participants).
+*   **Authentication:** Utilize Clerk for authentication, supporting SSO/OIDC and local accounts, with custom role/permission synchronization via middleware.
+*   **Technology Stack:** Next.js (App Router), React, TypeScript, Prisma (MSSQL primary, Postgres/SQLite secondary), Tailwind CSS, Shadcn UI, Playwright (E2E Testing), Tauri (Desktop).
+
+
+*(This brief summarizes the project based on initial analysis. Details may evolve.)*