added testcases

.github/workflows/test.yml

@@ -7,6 +7,7 @@ on:
 
 jobs:
     build:
+
         strategy:
             fail-fast: true
             matrix:
@@ -18,7 +19,9 @@ jobs:
             - uses: actions/checkout@v4
             - uses: actions/setup-node@v4
               with:
+
                   node-version: 'lts/*'
                   cache: 'npm'
+
             - run: npm install
             - run: npm test

AGENTS.md

@@ -36,6 +36,7 @@ rules in mind as new files are created:
 - **Non‑blocking audio** – heavy processing must stay off the UI thread.
 - **Tests** – every new feature requires tests once the test suite is available.
 
+
 ## Shadcn and Electron
 
 The interface is being rebuilt with [shadcn/ui](https://ui.shadcn.com) components.
@@ -51,6 +52,7 @@ Follow these guidelines when working on UI code:
 - **Tailwind theming** – rely on CSS variables and utilities in `@/utils/tailwind` for styling.
 - **Testing without running** – confirm `npm run typecheck` and module resolution with `node -e "require('<file>')"`.
 
+
 ## Tests
 
 No automated tests yet. When a suite is added, run `npm test` before each
@@ -94,8 +96,10 @@ uses Electron. Key goals are:
 3. Investigate speaker diarization options and integrate when feasible.
 4. Plan a migration path toward a proper testing setup (Jest or similar).
 5. Document security considerations for audio storage and processing.
+
 6. Rebuild the entire UI using shadcn components.
 
+
 These plans are aspirational; implement them gradually while keeping the app
 functional.