Task Status Legend
| Status | Syntax | Description |
|---|---|---|
| - [ ] | - [ ] | To Do - Task that needs to be completed |
| - [/] | - [/] | In Progress - Task currently being worked on |
| - [-] | - [-] | Cancelled - Task that has been cancelled or deprecated |
| - [x] | - [x] | Completed - Task that has been finished |
| - [?] | - [?] | Question - Task that needs clarification or discussion |
| - [n] | - [n] | DevNote - Technical note or reminder for developers |
| - [I] | - [I] | Idea - Potential feature or enhancement to consider |
| - [p] | - [p] | Pro Feature - Advanced feature planned for future release |
| - [c] | - [c] | Con/Limitation - Known limitation or constraint |
Evidence Dashboard & Build Issues
- Fix Evidence dashboard to only use supported SQL and table blocks (no dynamic table row counts)
- [/] Investigate and resolve SvelteKit/Evidence build error: ENOENT: no such file or directory, open ‘.evidence/template/.svelte-kit/types/src/pages//$types.d.ts’
- [n] Evidence does not support dynamic SQL for row counts across all tables; must use static queries or scripting
- [c] DuckDB/Evidence integration does not support referencing tables dynamically in SQL (e.g., cannot use main."" || table_name)
- [c] Evidence SQL blocks must be directly above their corresponding table blocks with no extra lines or formatting issues
- [n] Ensure all referenced tables (e.g., service_log) exist in the DuckDB database before querying