feat: Refined issue filters and search (Closes #815)

Author: timothyfroehlich

.github/workflows/ci.yml

@@ -297,6 +297,9 @@ jobs:
         with:
           version: latest
 
+      - name: Generate config.toml from template
+        run: cp supabase/config.toml.template supabase/config.toml
+
       - name: Start Supabase (minimal services for migrations)
         run: |
           supabase start -x "studio,realtime,storage-api,edge-runtime,logflare,vector,imgproxy,supavisor,postgres-meta"
@@ -355,6 +358,9 @@ jobs:
         with:
           version: latest
 
+      - name: Generate config.toml from template
+        run: cp supabase/config.toml.template supabase/config.toml
+
       - name: Make Supabase integration script executable
         run: chmod +x ./scripts/run-supabase-integration-tests.sh ./scripts/supabase-init-for-tests.sh
 
@@ -415,6 +421,9 @@ jobs:
         if: steps.playwright-cache.outputs.cache-hit != 'true'
         run: pnpm exec playwright install --with-deps chromium
 
+      - name: Generate config.toml from template
+        run: cp supabase/config.toml.template supabase/config.toml
+
       - name: Make E2E script executable
         run: chmod +x ./scripts/supabase-init-for-tests.sh
 
@@ -486,6 +495,9 @@ jobs:
         if: steps.playwright-cache.outputs.cache-hit != 'true'
         run: pnpm exec playwright install --with-deps chromium
 
+      - name: Generate config.toml from template
+        run: cp supabase/config.toml.template supabase/config.toml
+
       - name: Make E2E script executable
         run: chmod +x ./scripts/supabase-init-for-tests.sh
 
@@ -557,6 +569,9 @@ jobs:
         if: steps.playwright-cache.outputs.cache-hit != 'true'
         run: pnpm exec playwright install --with-deps chromium
 
+      - name: Generate config.toml from template
+        run: cp supabase/config.toml.template supabase/config.toml
+
       - name: Make E2E script executable
         run: chmod +x ./scripts/supabase-init-for-tests.sh
 
@@ -631,6 +646,9 @@ jobs:
         if: steps.playwright-cache.outputs.cache-hit != 'true'
         run: pnpm exec playwright install webkit
 
+      - name: Generate config.toml from template
+        run: cp supabase/config.toml.template supabase/config.toml
+
       - name: Make E2E script executable
         run: chmod +x ./scripts/supabase-init-for-tests.sh
 

.gitignore

@@ -79,6 +79,8 @@ node_modules/
 supabase/.temp/
 supabase/.branches/
 supabase/config.toml.bak.*
+# Generated from config.toml.template (worktree-specific)
+supabase/config.toml
 
 # Archived v1 test artifacts and build caches
 # (should have been ignored in v1, preventing future similar issues)

.jules/bolt.md

@@ -7,3 +7,8 @@
 
 **Learning:** Independent DB queries in Server Components often default to serial execution (waterfall). Always wrap independent queries in `Promise.all`. Fetching large datasets just to count them (e.g. `array.length`) is an anti-pattern; use `count()` in SQL instead.
 **Action:** Audit page loaders for serial `await` calls on independent data and replace array-based counting with SQL aggregation.
+
+## 2025-02-14 - Composite Index Optimization
+
+**Learning:** Replacing an index on `(A)` with `(A, B)` is a safe optimization when queries filter by `A` and sort by `B`. It allows the DB to fetch pre-sorted data, avoiding a sort operation, while still supporting lookups on `A`.
+**Action:** Always check if a frequently sorted column can be added to an existing filter index to create a composite index.

.jules/palette.md

@@ -17,3 +17,8 @@
 
 **Learning:** When placing interactive elements (like `Select` or `Button`) inside data tables, relying solely on column headers is insufficient for screen reader users navigating by control. A simple "Edit" or "Select" announcement lacks context.
 **Action:** Pass the row entity's name (e.g., user name) to the interactive component and use it in a dynamic `aria-label` (e.g., "Change role for John Doe").
+
+## 2025-05-21 - [Dynamic Accessible Names for Select Triggers]
+
+**Learning:** Shadcn UI `SelectTrigger` with a static `aria-label` overrides the screen reader announcement of the selected value. This leaves users knowing "Select Status" but not the _current_ status.
+**Action:** Use a dynamic `aria-label` that includes the current value (e.g., `aria-label={\`Status: ${valueLabel}\`}`) to provide full context.

.jules/sentinel.md

@@ -29,3 +29,9 @@
 **Vulnerability:** Found `TestAdminButton` containing hardcoded test credentials was statically imported into the login form, including the credentials in the production JavaScript bundle.
 **Learning:** Static imports of development-only components include their code (and secrets) in production bundles unless tree-shaken, which is unreliable for side-effect imports or complex components.
 **Prevention:** Use `next/dynamic` to lazily load development-only components, ensuring their code is split into a separate chunk that is never requested in production unless the component is rendered.
+
+## 2026-01-25 - Sensitive Information Exposure in User Invitation
+
+**Vulnerability:** Admin invitation actions (`inviteUser`, `resendInvite`) were throwing raw error messages (including potential SMTP error details) which were then displayed to the user via toast notifications.
+**Learning:** Even admin-only actions must be secure against information disclosure. Relying on `throw new Error(details)` in Server Actions often propagates the details to the client unless intercepted.
+**Prevention:** Always wrap external service calls (like Email, DB) in `try/catch` blocks in Server Actions. Log the full error securely on the server, and throw a generic, sanitized error message to the client.

AGENTS.md

@@ -38,7 +38,18 @@ If your tool does not support skills, read the file path directly.
 
 ### Worktrees & Ports
 
-We use git worktrees for parallel environments. Run `python3 scripts/sync_worktrees.py` to sync config.
+We use git worktrees for parallel environments. Config is managed via templates to prevent local leaks.
+
+**Workflow**:
+
+1. Run `python3 scripts/sync_worktrees.py` to generate `supabase/config.toml` and `.env.local` from templates.
+2. `supabase/config.toml` is ignored by git; do not track it.
+
+**Troubleshooting**:
+
+- _Config Mismatch_: If ports don't match the table below, re-run `python3 scripts/sync_worktrees.py`.
+- _Supabase Failures_: Run `supabase stop --all` then re-run the sync script.
+- _Template Changes_: If you need to change shared config, edit `supabase/config.toml.template` in the project root.
 
 | Worktree    | Next.js | Supabase API | Postgres |
 | :---------- | :------ | :----------- | :------- |

README.md

@@ -86,8 +86,7 @@ cd PinPoint
 pnpm install
 cp .env.example .env.local   # then fill in Supabase + DB vars
 
-supabase start               # in one terminal
-pnpm run dev                  # in another
+pnpm run dev                  # automatically ensures Supabase is running
 ```
 
 Open `http://localhost:<PORT>` (see `.env.local`) to use the app.
@@ -120,7 +119,6 @@ pnpm run test         # unit + PGlite integration tests
 pnpm run test:integration   # Supabase-backed integration tests
 pnpm run smoke        # Playwright smoke E2E tests
 pnpm run preflight    # full local CI gate before pushing
-# See docs/E2E_DOCKER.md for running Safari tests locally via Docker
 ```
 
 For more detail, see `docs/DEVELOPMENT.md` and `docs/TESTING_PLAN.md`.

docs/DEVELOPMENT.md

@@ -34,18 +34,15 @@ If you’re trying to understand how to implement something, read:
 
    ```bash
    pnpm install
-   cp .env.example .env.local
-   # Fill in Supabase + database env vars
+   python3 scripts/sync_worktrees.py
    ```
 
-3. **Start Supabase + Dev Server**
+   This generates `supabase/config.toml` and `.env.local` from templates. These files are ignored by git to keep your local environment clean.
 
-   ```bash
-   # In one terminal
-   supabase start
+3. **Start Dev Server**
 
-   # In another terminal
-   pnpm run dev
+   ```bash
+   pnpm run dev    # automatically ensures Supabase is running
    ```
 
 4. **Run Fast Checks While Iterating**

docs/E2E_DOCKER.md

@@ -0,0 +1,2 @@
+CREATE INDEX "idx_issues_severity" ON "issues" USING btree ("severity");--> statement-breakpoint
+CREATE INDEX "idx_issues_priority" ON "issues" USING btree ("priority");