db-mcp 2.0.0 → 3.0.1

package/test-server/test-tool-groups/README.md

@@ -1,100 +0,0 @@
-# db-mcp Standard Testing Suite
-
-**Directory Purpose**: This folder contains 10 self-contained, modular test prompts covering every tool group in `db-mcp`. Each file is a **complete, standalone prompt** — paste it directly into a conversation to test that tool group without needing any other files.
-
-## File Inventory
-
-| File                                | Group                     | Tools          | Notes                            |
-| ----------------------------------- | ------------------------- | -------------- | -------------------------------- |
-| `test-core-data.md`                 | core-data                 | 7              | Identical Native/WASM            |
-| `test-core-schema.md`               | core-schema               | 8 + Code Mode  | Identical Native/WASM            |
-| `test-json-read.md`                 | json-read                 | 18             | Identical Native/WASM            |
-| `test-json-write.md`                | json-write                | 7              | Identical Native/WASM            |
-| `test-text-basic.md`                | text-basic                | 11 + Code Mode | Identical Native/WASM            |
-| `test-text-advanced.md`             | text-advanced             | 9N/4W          | FTS5 tools `[NATIVE ONLY]`       |
-| `test-stats-basic.md`               | stats-basic               | 16 + Code Mode | Identical Native/WASM            |
-| `test-stats-advanced.md`            | stats-advanced            | 6N/0W          | Window functions `[NATIVE ONLY]` |
-| `test-vector-read.md`               | vector-read               | 7 + Code Mode  | Identical Native/WASM            |
-| `test-vector-write.md`              | vector-write              | 4              | Identical Native/WASM            |
-| `test-admin-core.md`                | admin-core                | 19 + Code Mode | Identical Native/WASM            |
-| `test-admin-extensions.md`          | admin-extensions          | 8              | CSV, series, rtree               |
-| `test-transactions.md`              | transactions              | 8 + Code Mode  | `[NATIVE ONLY]`                  |
-| `test-geo-haversine.md`             | geo-haversine             | 4 + Code Mode  | Identical Native/WASM            |
-| `test-geo-spatialite.md`            | geo-spatialite            | 7N/0W          | SpatiaLite `[NATIVE ONLY]`       |
-| `test-introspection-schema.md`      | introspection-schema      | 6              | Identical Native/WASM            |
-| `test-introspection-diagnostics.md` | introspection-diagnostics | 3 + Code Mode  | Identical Native/WASM            |
-| `test-migration.md`                 | migration                 | 6 + Code Mode  | Identical Native/WASM            |
-
-**Total**: 151 Native / 125 WASM tools across 10 groups + Code Mode.
-
-## Agent Instructions
-
-When tasked with running tests from this folder, adhere to the following protocol:
-
-### 1. Execution Strictness
-
-- **Direct Calls Exclusive**: Test tools ONLY using direct MCP tool calls (e.g., calling `mcp_sqlite_sqlite_read_query`). Do not use Code Mode (`sqlite_execute_code`) or scripts to batch the tests, except for checklist items explicitly testing Code Mode.
-- **No Scripted Loops**: Each happy and error path must be tested individually with a distinct tool call. This simulates exact client interaction behavior.
-
-### 2. Validation Targets
-
-- **Happy Path Consistency**: Validate that each tool outputs exactly what is expected from the explicit checklist items given in the prompt.
-- **Structured Error Path**: Ensure domain errors (e.g., nonexistent table) return an object `{"success": false, "error": "..."}`. A raw MCP error indicates a missing try/catch in the handler.
-- **Zod Exceptions**: Pass `{}` with missing required parameters or invalid types. The response must be a handler error, not a raw MCP `-32602` error.
-- **Payload Limits**: Watch for payload bloat and explicitly log it as a 📦 warning if it risks overflowing context window token limits.
-- **Code Over Docs (When Standards Violated)**: If the code deviates from established standards (e.g., throwing raw MCP errors instead of Structured Errors, or failing Zod validation), **fix the handler code**. Do not modify documentation, prompts, or `gotchas.md` to accommodate buggy code.
-- **Documentation Parity & Test Prompt Integrity**: Only update files in `src/constants/server-instructions` (or test prompts) if the code's behavior is mathematically/logically correct and intended, but the documentation is inaccurate, outdated, or lacking specificity. You SHOULD directly edit the markdown test files in this directory to fix factual errors, broken code blocks, or incorrect test assertions.
-
-### 2.5 Testing Limits
-
-- **No Automated Execution**: Do not run build or tests automatically (`npm run lint`, `npm run typecheck`, `npm run test:e2e`, `vitest`, or `playwright`). The user will execute them manually. When you reach the validate step, explicitly instruct the user to run the validations.
-
-### 2.6 WASM Mode Execution
-
-When testing against a **WASM backend** (`sqlite-wasm` server entry, sql.js adapter), follow these additional rules:
-
-#### Skip Rules
-
-- **`[NATIVE ONLY]` items**: Skip all checklist items and Zod sweep items for tools annotated with `[NATIVE ONLY]`.
-- **Transactions prompt**: Skip entirely — all 8 transaction tools are `[NATIVE ONLY]`.
-- **Window function tools** (stats items 20-25): Skip — 6 window tools are Native-only.
-- **SpatiaLite tools** (geo items 8-14): Skip — 7 SpatiaLite tools are Native-only.
-- **FTS5 tools** (text items 18-22): Skip — 5 FTS5 tools are Native-only.
-- **Unregistered tools**: In WASM mode, `[NATIVE ONLY]` tools are not registered at all. Direct MCP calls to them will fail with an "unknown tool" error — this is expected, not a bug.
-
-#### Graceful Degradation (Don't Skip — Validate Errors)
-
-Several admin tools are **registered in WASM mode but return structured errors**. Test these as **negative validation**:
-
-| Tool                        | Expected WASM Behavior                         |
-| --------------------------- | ---------------------------------------------- |
-| `sqlite_backup`             | `{success: false, error: "...WASM mode"}`      |
-| `sqlite_restore`            | `{success: false, error: "...WASM mode"}`      |
-| `sqlite_verify_backup`      | `{success: false, error: "...WASM mode"}`      |
-| `sqlite_create_csv_table`   | `{success: false}` — CSV extension unavailable |
-| `sqlite_analyze_csv_schema` | `{success: false}` — CSV extension unavailable |
-| `sqlite_create_rtree_table` | `{success: false}` — R-Tree module unavailable |
-
-#### Adjusted Expectations
-
-| Item                                                | Native Behavior             | WASM Behavior                    |
-| --------------------------------------------------- | --------------------------- | -------------------------------- |
-| `sqlite_dbstat({summarize: true})`                  | Per-table storage breakdown | Counts-only (JS fallback)        |
-| `sqlite_pragma_compile_options({filter: "FTS"})`    | Matches FTS5                | Matches FTS3                     |
-| `test_articles_fts` in `sqlite_list_virtual_tables` | Present and queryable       | May appear but FTS5 queries fail |
-
-### 3. Tracking Metrics & Progress
-
-- **Strict Coverage Matrix**: Maintain a table tracking your progress in `tmp/task.md` logging completion for:
-  `| Tool | Direct Call (Happy Path) | Domain Error | Zod Empty Param | Alias Acceptance |`
-  Never proceed to the final step until every tool in a given group is fully checked off.
-
-### 4. Cleanup & Scope
-
-- Direct write tests should operate on temporary tables or objects prefixed with `temp_`.
-- When completed, explicitly drop all `temp_` artifacts.
-- Update `code-map.md`, handlers, and instructions if bugs are uncovered, then update the Changelog with fixes before summarizing your work.
-
-## Execution
-
-Begin with any requested group prompt from this folder (e.g., `test-admin.md`), and execute the deterministic checklist line-by-line using direct tool calls only.

package/test-server/test-tool-groups/test-admin-core.md

@@ -1,165 +0,0 @@
-# db-mcp Tool Group Testing: [admin-core]
-
-> [!IMPORTANT]
-> **Do not track progress in this file.** Track your test progress, coverage matrix, and findings in your internal task tracking system (artifact). However, you SHOULD edit this file to fix any factual errors, broken code, or incorrect assertions in the test prompts.
-> If there is nothing to fix, don't update UNRELEASED.md.
-> We're currently testing Native mode.
-
-## WASM Mode
-
-> When testing against a **WASM backend** (`sqlite-wasm` / sql.js), apply these adjustments:
->
-> - **Items 13-15** (`sqlite_backup`, `sqlite_verify_backup`, `sqlite_restore`) — return `{success: false, error: "...WASM mode"}`. Treat as **negative validation** — verify the structured error, do not skip.
-> - **Item 10** (`sqlite_pragma_compile_options` FTS filter) — WASM shows FTS3 instead of FTS5.
-> - **Item 3** (`sqlite_dbstat` with `summarize: true`) — WASM returns counts-only (JS fallback) instead of per-table storage breakdown.
-
-**Step 1:** Confirm you read the server help content sourced from `C:\Users\chris\Desktop\db-mcp\src\constants\server-instructions\gotchas.md` using `view_file` (not grep or search) — to understand documented behaviors, edge cases, and response structures for this tool group.
-
-**Step 2:** Please conduct an exhaustive test of the **admin-core** tool group specified in the group-specific checklist below using live MCP server tool calls directly — not scripts/terminal.
-
-**Step 3:** The agent should update C:\Users\chris\Desktop\db-mcp\UNRELEASED.md with any/all changes/fixes.
-
-**Note** If temp tables are present from a previous test pass, it's because the database is locked. Ignore them.
-
-## Reporting Format
-
-- ❌ Fail: Tool errors or produces incorrect results (include error message)
-- ⚠️ Issue: Unexpected behavior or improvement opportunity
-- 📦 Payload: Unnecessarily large response that should be optimized — **blocking, equally important as ❌ bugs**.
-
-## Test Database Schema
-
-| Table             | Rows | Columns                                                                       | JSON Columns                                                                              |
-| ----------------- | ---- | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
-| test_products     | 16   | id, name, description, price, category, created_at                            | —                                                                                         |
-| test_orders       | 20   | id, product_id (FK), customer_name, quantity, total_price, order_date, status | —                                                                                         |
-| test_jsonb_docs   | 6    | id, doc, metadata, tags, created_at                                           | **doc**, **metadata** (nested), **tags** (array)                                          |
-| test_articles     | 8    | id, title, body, author, category, published_at                               | —                                                                                         |
-| test_users        | 9    | id, username, email, phone, bio, created_at                                   | —                                                                                         |
-| test_measurements | 200  | id, sensor_id, temperature, humidity, pressure, measured_at                   | —                                                                                         |
-| test_embeddings   | 20   | id, content, category, embedding                                              | **embedding** (8-dim float array); category values: database, fitness, food, tech, travel |
-| test_locations    | 15   | id, name, city, latitude, longitude, type                                     | —                                                                                         |
-| test_categories   | 17   | id, name, path, level                                                         | —                                                                                         |
-| test_events       | 100  | id, event_type, user_id (INT, 8 values), payload, event_date                  | **payload** (JSON)                                                                        |
-
-## Testing Requirements
-
-> [!CAUTION]
-> **Zero tolerance for raw MCP errors.** ANY response that is a raw MCP error (e.g., `-32602`, `isError: true`, no `success` field) is a **bug that must be reported and fixed**.
-
-1. Use existing `test_*` tables for read operations
-2. Create temporary views with `temp_view_*` prefix for write operations
-3. **Error path testing**: For **every** tool, test (a) domain error and (b) Zod validation error (`{}`). Both must return `{success: false, error: "..."}`.
-4. **Output schema testing**: For tools with `outputSchema`, confirm valid calls return structured JSON.
-
-## Structured Error Response Pattern
-
-```json
-{ "success": false, "error": "Human-readable error message" }
-```
-
-| Type                 | Source                                                             | What you see                                                | Verdict            |
-| -------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------- | ------------------ |
-| **Handler error** ✅ | Handler catches error and returns `{success: false, error: "..."}` | Parseable JSON object with `success` and `error` fields     | Correct            |
-| **MCP error** ❌     | Uncaught throw propagates to MCP framework                         | Raw text error string, `isError: true` — no `success` field | Bug — report as ❌ |
-
-### Zod Validation Errors
-
-**Zod refinement leak pattern:** `.partial()` does NOT strip `.min(N)` / `.max(N)` refinements. **Fix:** Remove refinements from schema, validate inside handler.
-
-### Output Schema Validation Errors
-
-If valid inputs return raw MCP `-32602` mentioning "output schema", report as ❌.
-
----
-
-## Group Focus: admin-core
-
-> **Instructions**: Execute every numbered checklist item with the exact inputs shown. Compare responses against the expected results. Report any deviation.
-
-### admin-core Group Tools (19)
-
-1. sqlite_create_view
-2. sqlite_list_views
-3. sqlite_drop_view
-4. sqlite_dbstat
-5. sqlite_vacuum
-6. sqlite_backup
-7. sqlite_analyze
-8. sqlite_integrity_check
-9. sqlite_optimize
-10. sqlite_restore
-11. sqlite_verify_backup
-12. sqlite_index_stats
-13. sqlite_pragma_compile_options
-14. sqlite_pragma_database_list
-15. sqlite_pragma_optimize
-16. sqlite_pragma_settings
-17. sqlite_pragma_table_info
-18. sqlite_append_insight
-19. sqlite_execute_code
-
-**Checklist — Pragma & Inspection:**
-
-1. `sqlite_pragma_database_list` → verify database path matches `test.db`
-2. `sqlite_index_stats` → verify index statistics for test database
-3. `sqlite_dbstat({summarize: true})` → per-table storage metrics
-4. `sqlite_integrity_check` → `ok` result
-5. `sqlite_analyze` → success
-6. `sqlite_vacuum` → success
-7. `sqlite_optimize` → success with optimization details
-8. `sqlite_pragma_optimize` → success (note: distinct from `sqlite_optimize` — this runs `PRAGMA optimize`)
-9. `sqlite_pragma_compile_options` → verify list of compile options returned
-10. `sqlite_pragma_compile_options({filter: "FTS"})` → filtered subset containing FTS-related options (`ENABLE_FTS3`, `ENABLE_FTS4`, `ENABLE_FTS5`)
-11. `sqlite_pragma_settings({pragma: "journal_mode"})` → `{value: "wal"}`
-12. `sqlite_pragma_table_info({table: "test_products"})` → verify columns: id, name, description, price, category, created_at
-
-**Checklist — Backup/Restore:**
-
-13. `sqlite_backup({targetPath: "<absolute-path>/test-server/test-backup.db"})` → success with backup file info (⚠️ use absolute path — relative paths resolve from IDE CWD)
-14. `sqlite_verify_backup({backupPath: "<absolute-path>/test-server/test-backup.db"})` → integrity verified
-15. `sqlite_restore({sourcePath: "<absolute-path>/test-server/test-backup.db"})` → restore from backup, verify success
-16. Cleanup: note backup file location for manual removal if desired
-
-**Checklist — View Management:**
-
-17. `sqlite_create_view({viewName: "temp_view_orders", selectQuery: "SELECT product_id, COUNT(*) as order_count, SUM(total_price) as revenue FROM test_orders GROUP BY product_id"})` → success
-18. `sqlite_list_views` → verify `temp_view_orders` present
-19. `sqlite_drop_view({viewName: "temp_view_orders"})` → success
-
-**Checklist — Insights:**
-
-20. `sqlite_append_insight({insight: "Test insight for verification"})` → success
-
-**Code mode testing:**
-
-21. `sqlite_execute_code({code: "const result = await sqlite.admin.integrityCheck(); return result;"})` → `ok` result
-22. `sqlite_execute_code({code: "const result = await sqlite.admin.pragmaSettings({pragma: 'journal_mode'}); return result;"})` → `{pragma: "journal_mode", value: "wal"}`
-
-**Error path testing:**
-
-🔴 23. `sqlite_pragma_table_info({table: "nonexistent_table_xyz"})` → report behavior
-🔴 24. `sqlite_verify_backup({backupPath: "nonexistent_file.db"})` → structured error
-
-**Zod validation sweep** — call each tool with `{}` (empty params). Must return handler error, NOT raw MCP error:
-
-🔴 25. `sqlite_backup({})` → handler error
-🔴 26. `sqlite_restore({})` → handler error
-🔴 27. `sqlite_verify_backup({})` → handler error
-🔴 28. `sqlite_pragma_table_info({})` → handler error
-🔴 29. `sqlite_pragma_settings({})` → handler error (has required `pragma` param)
-🔴 30. `sqlite_append_insight({})` → handler error
-🔴 31. `sqlite_create_view({})` → handler error
-🔴 32. `sqlite_drop_view({})` → handler error
-🔴 33. `sqlite_dbstat({})` → handler error (or success if no required params)
-
----
-
-## Post-Test Procedures
-
-1. **Triage findings**: Create implementation plan if issues found
-2. **Scope of fixes**: Handler code, server-instructions, test database, this prompt
-3. **Validate**: Instruct the user to run the test suite (Vitest/Playwright), lint, and typecheck. Do NOT run them yourself.
-4. **Commit**: Stage and commit — do NOT push
-5. **Live re-test**: After server rebuild
-6. **Final summary**: After testing/re-testing

package/test-server/test-tool-groups/test-admin-extensions.md

@@ -1,133 +0,0 @@
-# db-mcp Tool Group Testing: [admin-extensions]
-
-> [!IMPORTANT]
-> **Do not track progress in this file.** Track your test progress, coverage matrix, and findings in your internal task tracking system (artifact). However, you SHOULD edit this file to fix any factual errors, broken code, or incorrect assertions in the test prompts.
-> If there is nothing to fix, don't update UNRELEASED.md.
-> We're currently testing Native mode.
-
-## WASM Mode
-
-> When testing against a **WASM backend** (`sqlite-wasm` / sql.js), apply these adjustments:
->
-> - **Items 3-4** (`sqlite_create_csv_table`, `sqlite_analyze_csv_schema`) — return `{success: false}` in WASM (CSV extension unavailable). Treat as **negative validation**.
-> - **Item 5** (`sqlite_create_rtree_table`) — returns `{success: false}` in WASM (R-Tree unavailable). Treat as **negative validation**.
-> - **Item 1** (`sqlite_list_virtual_tables`) — `test_articles_fts` may appear but is not queryable.
-
-**Step 1:** Confirm you read the server help content sourced from `C:\Users\chris\Desktop\db-mcp\src\constants\server-instructions\gotchas.md` using `view_file` (not grep or search) — to understand documented behaviors, edge cases, and response structures for this tool group.
-
-**Step 2:** Please conduct an exhaustive test of the **admin-extensions** tool group specified in the group-specific checklist below using live MCP server tool calls directly — not scripts/terminal.
-
-**Step 3:** The agent should update C:\Users\chris\Desktop\db-mcp\UNRELEASED.md with any/all changes/fixes.
-
-**Note** If temp tables are present from a previous test pass, it's because the database is locked. Ignore them.
-
-## Reporting Format
-
-- ❌ Fail: Tool errors or produces incorrect results (include error message)
-- ⚠️ Issue: Unexpected behavior or improvement opportunity
-- 📦 Payload: Unnecessarily large response that should be optimized.
-
-## Test Database Schema
-
-| Table             | Rows | Columns                                                                       | JSON Columns                                                                              |
-| ----------------- | ---- | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
-| test_products     | 16   | id, name, description, price, category, created_at                            | —                                                                                         |
-| test_orders       | 20   | id, product_id (FK), customer_name, quantity, total_price, order_date, status | —                                                                                         |
-| test_jsonb_docs   | 6    | id, doc, metadata, tags, created_at                                           | **doc**, **metadata** (nested), **tags** (array)                                          |
-| test_articles     | 8    | id, title, body, author, category, published_at                               | —                                                                                         |
-| test_users        | 9    | id, username, email, phone, bio, created_at                                   | —                                                                                         |
-| test_measurements | 200  | id, sensor_id, temperature, humidity, pressure, measured_at                   | —                                                                                         |
-| test_embeddings   | 20   | id, content, category, embedding                                              | **embedding** (8-dim float array); category values: database, fitness, food, tech, travel |
-| test_locations    | 15   | id, name, city, latitude, longitude, type                                     | —                                                                                         |
-| test_categories   | 17   | id, name, path, level                                                         | —                                                                                         |
-| test_events       | 100  | id, event_type, user_id (INT, 8 values), payload, event_date                  | **payload** (JSON)                                                                        |
-
-## Testing Requirements
-
-> [!CAUTION]
-> **Zero tolerance for raw MCP errors.** ANY response that is a raw MCP error (e.g., `-32602`, `isError: true`, no `success` field) is a **bug that must be reported and fixed**.
-
-1. Use existing `test_*` tables for read operations
-2. Create temporary tables with `temp_*` prefix for write operations
-3. **Error path testing**: For **every** tool, test (a) domain error and (b) Zod validation error (`{}`). Both must return `{success: false, error: "..."}`.
-4. **Output schema testing**: For tools with `outputSchema`, confirm valid calls return structured JSON.
-
-## Structured Error Response Pattern
-
-```json
-{ "success": false, "error": "Human-readable error message" }
-```
-
-| Type                 | Source                                                             | What you see                                                | Verdict            |
-| -------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------- | ------------------ |
-| **Handler error** ✅ | Handler catches error and returns `{success: false, error: "..."}` | Parseable JSON object with `success` and `error` fields     | Correct            |
-| **MCP error** ❌     | Uncaught throw propagates to MCP framework                         | Raw text error string, `isError: true` — no `success` field | Bug — report as ❌ |
-
-### Zod Validation Errors
-
-**Zod refinement leak pattern:** `.partial()` does NOT strip `.min(N)` / `.max(N)` refinements. **Fix:** Remove refinements from schema, validate inside handler.
-
-### Output Schema Validation Errors
-
-If valid inputs return raw MCP `-32602` mentioning "output schema", report as ❌.
-
----
-
-## Group Focus: admin-extensions
-
-> **Instructions**: Execute every numbered checklist item with the exact inputs shown. Compare responses against the expected results. Report any deviation.
-
-> **CSV Testing Note:** Use `test-server/sample.csv` (columns: id, name, category, price, quantity, created_at) with **absolute paths** for CSV tool testing — relative paths resolve from IDE CWD.
-
-### admin-extensions Group Tools (8)
-
-1. sqlite_generate_series
-2. sqlite_list_virtual_tables
-3. sqlite_virtual_table_info
-4. sqlite_drop_virtual_table
-5. sqlite_create_csv_table
-6. sqlite_analyze_csv_schema
-7. sqlite_create_rtree_table
-8. sqlite_create_series_table
-
-**Checklist:**
-
-**Virtual Tables:**
-
-1. `sqlite_list_virtual_tables` → verify `test_articles_fts` present (Native)
-2. `sqlite_virtual_table_info({tableName: "test_articles_fts"})` → verify module and column info (Native)
-3. `sqlite_generate_series({start: 1, stop: 5, step: 1})` → 5 values
-4. `sqlite_create_rtree_table({tableName: "temp_rtree_test", dimensions: 2})` → R-Tree virtual table created with 2D bounding box columns
-5. `sqlite_create_series_table({tableName: "temp_series_test", start: 1, stop: 10})` → regular table created with 10 rows (not a virtual table — see gotcha #14)
-6. Cleanup: `sqlite_drop_virtual_table({tableName: "temp_rtree_test"})` and `sqlite_drop_table({table: "temp_series_test"})` (series is a regular table — use core `sqlite_drop_table`)
-
-**CSV:**
-
-7. `sqlite_analyze_csv_schema({filePath: "<absolute-path>/test-server/sample.csv"})` → inferred column types (⚠️ CSV requires absolute paths — see gotcha #13)
-8. `sqlite_create_csv_table({tableName: "temp_csv_test", filePath: "<absolute-path>/test-server/sample.csv"})` → virtual table created
-9. Cleanup: `sqlite_drop_virtual_table({tableName: "temp_csv_test"})`
-
-**Error path testing:**
-
-🔴 10. `sqlite_virtual_table_info({tableName: "nonexistent_table_xyz"})` → structured error
-
-**Zod validation sweep** — call each tool with `{}` (empty params). Must return handler error, NOT raw MCP error:
-
-🔴 11. `sqlite_virtual_table_info({})` → handler error
-🔴 12. `sqlite_drop_virtual_table({})` → handler error
-🔴 13. `sqlite_create_csv_table({})` → handler error
-🔴 14. `sqlite_analyze_csv_schema({})` → handler error
-🔴 15. `sqlite_create_rtree_table({})` → handler error
-🔴 16. `sqlite_create_series_table({})` → handler error
-🔴 17. `sqlite_generate_series({})` → handler error
-
----
-
-## Post-Test Procedures
-
-1. **Triage findings**: Create implementation plan if issues found
-2. **Scope of fixes**: Handler code, server-instructions, test database, this prompt
-3. **Validate**: Instruct the user to run the test suite (Vitest/Playwright), lint, and typecheck. Do NOT run them yourself.
-4. **Commit**: Stage and commit — do NOT push
-5. **Live re-test**: After server rebuild
-6. **Final summary**: After testing/re-testing