db-mcp 1.1.1 → 2.0.0

package/test-server/test-codemode/test-codemode-migration.md

@@ -0,0 +1,278 @@
+# db-mcp Code Mode Testing: [migration]
+
+> [!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.
+
+**Step 1:** Read `C:\Users\chris\Desktop\db-mcp\src\constants\server-instructions\gotchas.md` using `view_file`.
+
+**Step 2:** Conduct an exhaustive test of the **migration** tool group using ONLY `sqlite_execute_code`. Do not use direct tool calls or terminal.
+
+**Step 3:** The agent should update C:\Users\chris\Desktop\db-mcp\UNRELEASED.md with any/all changes/fixes.
+
+> **⚠️ After testing, run `Set-Location C:\Users\chris\Desktop\db-mcp\test-server; .\reset-database.ps1`** — migration testing creates the `_mcp_migrations` tracking table and modifies schema. Always reset after.
+
+## WASM Mode
+
+> When testing against a **WASM backend** (`--sqlite` / sql.js): All 6 migration tools are fully WASM-compatible. No phases to skip or adjust.
+
+## Reporting Format
+
+- ❌ Fail: Tool errors or produces incorrect results
+- ⚠️ Issue: Unexpected behavior or improvement opportunity
+- 📦 Payload: Unnecessarily large response — monitor `metrics.tokenEstimate`.
+
+## Test Database Schema
+
+| Table         | Rows | Key Columns                              |
+| ------------- | ---- | ---------------------------------------- |
+| test_products | 16   | id, name, price, category                |
+| test_orders   | 20   | id, product_id (FK), total_price, status |
+
+## Testing Requirements
+
+> [!CAUTION]
+> **Zero tolerance for raw MCP errors.** Report as ❌.
+
+1. **Batched scripting**: Bundle checks with `failures` array where possible.
+2. **Error path testing**: Every tool with `{}` (Zod) and domain error.
+3. **Token tracking**: Monitor `metrics.tokenEstimate`.
+4. **Coverage Matrix**: `| Tool | Happy Path | Domain Error | Zod Error |`
+5. **Deterministic checklist first**.
+6. **Code Over Docs**: Fix the handler code if standards (Structured Errors/Zod) are violated. Do NOT change docs/prompts to accommodate broken code.
+
+> **⚠️ Migration ordering matters**: Migration tests are stateful — each depends on the previous. Run lifecycle tests sequentially, not batched.
+
+## Structured Error Response Pattern
+
+Handler error ✅ = JSON with `success` + `error`. MCP error ❌ = raw text, `isError: true`.
+
+---
+
+## Phase 1: Initialization & Recording — Happy Paths (sequential)
+
+### 1.1 — Init migrations
+
+```javascript
+return await sqlite.migration.migrationInit();
+```
+
+Expected: `{success: true}`, creates `_mcp_migrations` table (idempotent).
+
+### 1.2 — Init again (idempotency)
+
+```javascript
+return await sqlite.migration.migrationInit();
+```
+
+Expected: Succeeds without error.
+
+### 1.3 — Check status (empty)
+
+```javascript
+return await sqlite.migration.migrationStatus();
+```
+
+Expected: No migrations applied.
+
+### 1.4 — Record a migration (no execution)
+
+```javascript
+return await sqlite.migration.migrationRecord({
+  version: "1.0.0",
+  description: "Create temp table",
+  migrationSql:
+    "CREATE TABLE temp_cm_mig_test (id INTEGER PRIMARY KEY, name TEXT)",
+});
+```
+
+Expected: Recorded (SQL not executed — only logged).
+
+### 1.5 — Check status (1 migration)
+
+```javascript
+return await sqlite.migration.migrationStatus();
+```
+
+Expected: Count incremented.
+
+### 1.6 — Check history
+
+```javascript
+return await sqlite.migration.migrationHistory();
+```
+
+Expected: Version 1.0.0 listed.
+
+---
+
+## Phase 2: Apply & Execute — Happy Paths (sequential)
+
+### 2.1 — Apply a migration (SQL executed)
+
+```javascript
+return await sqlite.migration.migrationApply({
+  version: "1.0.1",
+  description: "Create applied table",
+  migrationSql:
+    "CREATE TABLE temp_cm_mig_applied (id INTEGER PRIMARY KEY, value TEXT)",
+});
+```
+
+Expected: Applied (SQL executed AND recorded).
+
+### 2.2 — Verify table exists
+
+```javascript
+return await sqlite.core.readQuery(
+  "SELECT name FROM sqlite_master WHERE name = 'temp_cm_mig_applied'",
+);
+```
+
+Expected: Table exists.
+
+### 2.3 — Check history (2 migrations)
+
+```javascript
+return await sqlite.migration.migrationHistory();
+```
+
+Expected: Both 1.0.0 and 1.0.1 listed.
+
+---
+
+## Phase 3: SHA-256 Deduplication
+
+### 3.1 — Duplicate SQL detection
+
+```javascript
+return await sqlite.migration.migrationRecord({
+  version: "1.0.2",
+  description: "Duplicate test",
+  migrationSql:
+    "CREATE TABLE temp_cm_mig_test (id INTEGER PRIMARY KEY, name TEXT)",
+});
+```
+
+Expected: Fail — duplicate SQL hash detected.
+
+---
+
+## Phase 4: Rollback — Happy Paths (sequential)
+
+### 4.1 — Rollback without rollback SQL
+
+```javascript
+return await sqlite.migration.migrationRollback({ version: "1.0.1" });
+```
+
+Expected: Informative error (no rollbackSql was provided).
+
+### 4.2 — Apply with rollback SQL
+
+```javascript
+return await sqlite.migration.migrationApply({
+  version: "1.0.3",
+  description: "With rollback",
+  migrationSql: "CREATE TABLE temp_cm_mig_rollback (id INTEGER PRIMARY KEY)",
+  rollbackSql: "DROP TABLE IF EXISTS temp_cm_mig_rollback",
+});
+```
+
+Expected: Applied with rollback SQL stored.
+
+### 4.3 — Execute rollback
+
+```javascript
+return await sqlite.migration.migrationRollback({ version: "1.0.3" });
+```
+
+Expected: Rollback SQL executed.
+
+### 4.4 — Verify table gone
+
+```javascript
+return await sqlite.core.readQuery(
+  "SELECT name FROM sqlite_master WHERE name = 'temp_cm_mig_rollback'",
+);
+```
+
+Expected: Table does NOT exist.
+
+---
+
+## Phase 5: Migration Domain Errors (batched)
+
+🔴 5.1. `sqlite.migration.migrationApply({version: "bad version!", description: "Invalid", migrationSql: "SELECT 1"})` → report behavior
+🔴 5.2. `sqlite.migration.migrationRollback({version: "nonexistent_version"})` → `{success: false}`
+
+---
+
+## Phase 6: Migration Zod Validation (batched)
+
+🔴 6.1. `sqlite.migration.migrationInit({})` → success (no required params)
+🔴 6.2. `sqlite.migration.migrationRecord({})` → `{success: false}` (missing required params)
+🔴 6.3. `sqlite.migration.migrationApply({})` → `{success: false}` (missing required params)
+🔴 6.4. `sqlite.migration.migrationRollback({})` → `{success: false}` (missing `version`)
+🔴 6.5. `sqlite.migration.migrationHistory({})` → success (no required params)
+🔴 6.6. `sqlite.migration.migrationStatus({})` → success (no required params)
+
+---
+
+## Phase 7: Multi-Step Workflow
+
+### 7.1 — Full migration lifecycle
+
+```javascript
+const failures = [];
+// Init
+await sqlite.migration.migrationInit();
+
+// Apply
+await sqlite.migration.migrationApply({
+  version: "9.9.1",
+  description: "Lifecycle test",
+  migrationSql:
+    "CREATE TABLE temp_cm_mig_lifecycle (id INTEGER PRIMARY KEY, val TEXT)",
+  rollbackSql: "DROP TABLE IF EXISTS temp_cm_mig_lifecycle",
+});
+
+// Verify
+const status = await sqlite.migration.migrationStatus();
+const history = await sqlite.migration.migrationHistory();
+const tableExists = await sqlite.core.readQuery(
+  "SELECT name FROM sqlite_master WHERE name = 'temp_cm_mig_lifecycle'",
+);
+
+if (!tableExists.rows || tableExists.rows.length === 0)
+  failures.push("table not created after apply");
+
+// Rollback
+await sqlite.migration.migrationRollback({ version: "9.9.1" });
+const afterRollback = await sqlite.core.readQuery(
+  "SELECT name FROM sqlite_master WHERE name = 'temp_cm_mig_lifecycle'",
+);
+if (afterRollback.rows && afterRollback.rows.length > 0)
+  failures.push("table still exists after rollback");
+
+return {
+  failures,
+  success: failures.length === 0,
+  statusBefore: status,
+  historyEntries: history,
+};
+```
+
+---
+
+## Post-Test Procedures
+
+1. **⚠️ Explicit Cleanup**: Execute a final Code Mode script to `DROP TABLE IF EXISTS` all `temp_*` tables created during the test, as the active MCP server lock prevents the reset script from clearing them.
+2. **⚠️ Reset database**: Run `Set-Location C:\Users\chris\Desktop\db-mcp\test-server; .\reset-database.ps1` to re-seed the test database.
+3. **Triage findings**: Create implementation plan if issues found
+4. **Scope of fixes**: Handler code, server-instructions, this prompt
+5. **Validate**: Instruct the user to run the test suite (Vitest/Playwright), lint, and typecheck. Do NOT run them yourself.
+6. **Commit**: Stage and commit — do NOT push
+7. **Token audit**: Report most expensive block
+8. **Final summary**: After testing/re-testing

package/test-server/test-codemode/test-codemode-sandbox.md

@@ -0,0 +1,413 @@
+# db-mcp Code Mode Testing: [sandbox]
+
+> [!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.
+
+**Step 1:** Read `C:\Users\chris\Desktop\db-mcp\src\constants\server-instructions\gotchas.md` using `view_file`.
+
+**Step 2:** Conduct an exhaustive test of the **Code Mode sandbox** using ONLY `sqlite_execute_code`. Do not use direct tool calls or terminal.
+
+**Step 3:** The agent should update C:\Users\chris\Desktop\db-mcp\UNRELEASED.md with any/all changes/fixes.
+
+## WASM Mode
+
+> When testing against a **WASM backend** (`--sqlite` / sql.js), apply these adjustments:
+
+- **Phase 2.1** (top-level help): Expect fewer than 10 groups — `transactions` is not listed (0 tools registered in WASM). `totalMethods` will be ~125 instead of ~151.
+- **Phase 2.3** (all groups exist): The `transactions` group property exists on the `sqlite` object but returns 0 methods. Adjust the assertion to allow 0 methods for `transactions`.
+- **Phase 4.5** (stats read-only): Stats tools are fully WASM-compatible — no adjustment needed.
+
+## Reporting Format
+
+- ❌ Fail: Tool errors or produces incorrect results (include error message)
+- ⚠️ Issue: Unexpected behavior or improvement opportunity
+- 📦 Payload: Unnecessarily large response — **blocking, equally important as ❌ bugs**. You **MUST** monitor `metrics.tokenEstimate` for every operation. Report the response size in tokens/KB and suggest optimization.
+
+## Test Database Schema
+
+| Table         | Rows | Key Columns                                                                                 |
+| ------------- | ---- | ------------------------------------------------------------------------------------------- |
+| test_products | 16   | id, name, description, price (REAL), category (TEXT lowercase), created_at                  |
+| test_orders   | 20   | id, product_id (FK→test_products), customer_name, quantity, total_price, order_date, status |
+
+> **Note:** This prompt tests the sandbox execution environment, not specific tool groups. It uses `test_products` and `test_orders` as representative tables for validation.
+
+## Testing Requirements
+
+> [!CAUTION]
+> **Zero tolerance for raw MCP errors.** Any response that is a raw MCP error (no `success` field) is a bug — report as ❌.
+
+1. **Error path testing**: Validate structured error responses for invalid inputs.
+2. **Token tracking**: Monitor `metrics.tokenEstimate` on every response. Report the most expensive block.
+3. **Deterministic checklist first**: Complete ALL numbered items before freeform exploration.
+4. **Code Over Docs**: Fix the handler code if standards (Structured Errors/Zod) are violated. Do NOT change docs/prompts to accommodate broken code.
+
+## Structured Error Response Pattern
+
+```json
+{ "success": false, "error": "Human-readable error message" }
+```
+
+| Type                 | What you see                                  | Verdict |
+| -------------------- | --------------------------------------------- | ------- |
+| **Handler error** ✅ | JSON object with `success` and `error` fields | Correct |
+| **MCP error** ❌     | Raw text, `isError: true`, no `success` field | Bug     |
+
+---
+
+## Phase 1: Sandbox Basics (9 tests)
+
+> These tests validate the Code Mode sandbox itself — run them first.
+
+### 1.1 — Simple return value
+
+```javascript
+return 42;
+```
+
+Expected: `{success: true, result: 42}`
+
+### 1.2 — Object return
+
+```javascript
+return { name: "test", values: [1, 2, 3] };
+```
+
+### 1.3 — Async/await support
+
+```javascript
+const result = await Promise.resolve("async works");
+return result;
+```
+
+### 1.4 — Runtime error handling
+
+```javascript
+const x = undefinedVariable;
+return x;
+```
+
+Expected: `{success: false, error: "...not defined..."}` — structured, not crash.
+
+### 1.5 — Empty code
+
+Call `sqlite_execute_code` with `code: ""`.
+Expected: `{success: false}` with validation error, not raw MCP error.
+
+### 1.6 — Empty params
+
+Call `sqlite_execute_code` with `{}` (no `code` param).
+Expected: structured handler error, NOT raw MCP `-32602`.
+
+### 1.7 — Return null
+
+```javascript
+return null;
+```
+
+Expected: `{success: true, result: null}` — sandbox must handle null return values.
+
+### 1.8 — Return undefined
+
+```javascript
+return undefined;
+```
+
+Expected: `{success: true}` — sandbox must handle undefined without crashing. `result` may be absent or null.
+
+### 1.9 — Return large nested object
+
+```javascript
+const nested = {};
+let current = nested;
+for (let i = 0; i < 10; i++) {
+  current.level = i;
+  current.child = {};
+  current = current.child;
+}
+current.leaf = "deep value";
+return nested;
+```
+
+Expected: `{success: true}` — sandbox must serialize deeply nested objects.
+
+---
+
+## Phase 2: API Discoverability (7 tests)
+
+### 2.1 — Top-level help
+
+```javascript
+return await sqlite.help();
+```
+
+Expected: `{groups: [...], totalMethods: <number>, usage: "..."}` with 10 groups listed (including transactions). **WASM**: Fewer groups — `transactions` is absent; `totalMethods` ≈ 125.
+
+### 2.2 — Group help (core)
+
+```javascript
+return await sqlite.core.help();
+```
+
+Expected: `{group: "core", methods: [...]}` with methods including `readQuery`, `writeQuery`, `listTables`, `describeTable`, `upsert`, `batchInsert`, `count`, `exists`, `truncate`.
+
+### 2.3 — All groups exist
+
+```javascript
+const groups = [
+  "core",
+  "json",
+  "text",
+  "stats",
+  "vector",
+  "admin",
+  "transactions",
+  "geo",
+  "introspection",
+  "migration",
+];
+const results = {};
+for (const g of groups) {
+  const h = await sqlite[g].help();
+  results[g] = h.methods.length;
+}
+return results;
+```
+
+Expected: All 10 groups return >0 methods. **WASM**: `transactions` returns 0 methods — adjust assertion to allow this.
+
+### 2.4 — Method aliases resolve
+
+```javascript
+const r1 = await sqlite.core.query("SELECT 1 AS num");
+const r2 = await sqlite.core.readQuery("SELECT 1 AS num");
+return { aliasResult: r1, canonicalResult: r2 };
+```
+
+Expected: Both return identical results.
+
+### 2.5 — Top-level convenience aliases
+
+```javascript
+const tables = await sqlite.listTables();
+return { success: true, tableCount: tables.tables?.length };
+```
+
+### 2.6 — Positional args
+
+```javascript
+return await sqlite.core.readQuery("SELECT name FROM test_products LIMIT 2");
+```
+
+Expected: Works with string positional arg (not just object).
+
+### 2.7 — Built-in tools not in sandbox
+
+```javascript
+return {
+  serverInfo: typeof sqlite.serverInfo,
+  serverHealth: typeof sqlite.serverHealth,
+  listAdapters: typeof sqlite.listAdapters,
+  server_info: typeof sqlite.server_info,
+  server_health: typeof sqlite.server_health,
+  list_adapters: typeof sqlite.list_adapters,
+};
+```
+
+Expected: All values are `"undefined"`. The 3 built-in tools (`server_info`, `server_health`, `list_adapters`) are always-on MCP tools available outside Code Mode but must NOT be accessible in the `sqlite.*` sandbox namespace.
+
+---
+
+## Phase 3: Security & Error Handling (7 tests)
+
+### 3.1 — Blocked pattern (require)
+
+```javascript
+const fs = require("fs");
+return fs.readFileSync("/etc/passwd");
+```
+
+Expected: `{success: false, code: "CODEMODE_VALIDATION_FAILED"}`
+
+### 3.2 — Blocked pattern (process)
+
+```javascript
+return process.env;
+```
+
+Expected: `{success: false}` — blocked pattern or runtime error.
+
+### 3.3 — Blocked pattern (eval)
+
+```javascript
+return eval("1+1");
+```
+
+Expected: `{success: false, code: "CODEMODE_VALIDATION_FAILED"}`
+
+### 3.4 — Timeout enforcement
+
+```javascript
+while (true) {}
+```
+
+Call with `timeout: 2000`. Expected: `{success: false}` with timeout error within ~2s.
+
+### 3.5 — Timeout enforcement (tight tolerance)
+
+```javascript
+const start = Date.now();
+while (Date.now() - start < 1000) {} // busy-wait 1s
+return "completed";
+```
+
+Call with `timeout: 500`. Expected: `{success: false}` with timeout error — the 500ms timeout must fire before the 1s loop completes.
+
+### 3.6 — Invalid tool call via API
+
+```javascript
+return await sqlite.core.readQuery({ query: "SELECT * FROM nonexistent_xyz" });
+```
+
+Expected: Returns `{success: false, error: "..."}` — sandbox must not crash.
+
+### 3.7 — Undefined API group
+
+```javascript
+return await sqlite.nonexistent.help();
+```
+
+Expected: runtime error, not crash.
+
+---
+
+## Phase 4: Readonly Mode (5 tests)
+
+All tests use `readonly: true` on the `sqlite_execute_code` call.
+
+### 4.1 — Read operations work
+
+```javascript
+// readonly: true
+return await sqlite.core.readQuery("SELECT COUNT(*) AS cnt FROM test_products");
+```
+
+Expected: `{success: true, rows: [{cnt: 16}]}`
+
+### 4.2 — Write operations blocked
+
+```javascript
+// readonly: true
+return await sqlite.core.writeQuery(
+  "INSERT INTO test_products (name) VALUES ('blocked')",
+);
+```
+
+Expected: `{success: false, code: "CODEMODE_READONLY_VIOLATION"}`
+
+### 4.3 — Read methods still discoverable
+
+```javascript
+// readonly: true
+const help = await sqlite.core.help();
+return {
+  hasWriteQuery: help.methods.includes("writeQuery"),
+  methods: help.methods,
+};
+```
+
+Expected: `writeQuery` still appears in help (for discoverability) but is guarded.
+
+### 4.4 — Create table blocked
+
+```javascript
+// readonly: true
+return await sqlite.core.writeQuery(
+  "CREATE TABLE temp_readonly_test (id INTEGER)",
+);
+```
+
+Expected: `{success: false, code: "CODEMODE_READONLY_VIOLATION"}`
+
+### 4.5 — Stats read-only works
+
+```javascript
+// readonly: true
+return await sqlite.stats.statsBasic({
+  table: "test_products",
+  column: "price",
+});
+```
+
+Expected: succeeds — stats tools are read-only.
+
+---
+
+## Phase 5: State Isolation (2 tests)
+
+### 5.1 — Variables don't persist between calls
+
+Run two separate `sqlite_execute_code` calls:
+
+**Call 1:**
+
+```javascript
+var persistTest = "should not persist";
+return persistTest;
+```
+
+**Call 2:**
+
+```javascript
+try {
+  return { persisted: typeof persistTest !== "undefined", value: persistTest };
+} catch (e) {
+  return { persisted: false, error: e.message };
+}
+```
+
+Expected: Call 2 returns `{persisted: false}` — variables from Call 1 must not leak.
+
+### 5.2 — Database state persists between calls
+
+Run two separate `sqlite_execute_code` calls:
+
+**Call 1:**
+
+```javascript
+await sqlite.core.createTable({
+  table: "temp_cm_iso_test",
+  columns: [
+    { name: "id", type: "INTEGER", primaryKey: true },
+    { name: "val", type: "TEXT" },
+  ],
+});
+await sqlite.core.writeQuery(
+  "INSERT INTO temp_cm_iso_test VALUES (1, 'persisted')",
+);
+return "created";
+```
+
+**Call 2:**
+
+```javascript
+const result = await sqlite.core.readQuery("SELECT * FROM temp_cm_iso_test");
+await sqlite.core.dropTable({ table: "temp_cm_iso_test", ifExists: true });
+return result;
+```
+
+Expected: Call 2 reads the row inserted in Call 1 — database state persists across sandbox invocations (sandbox is stateless, database is not).
+
+---
+
+## Post-Test Procedures
+
+1. **Cleanup**: Confirm all `temp_*` tables are removed
+2. **Triage findings**: Create implementation plan if issues found
+3. **Scope of fixes**: Handler code, server-instructions, this prompt
+4. **Validate**: Instruct the user to run the test suite (Vitest/Playwright), lint, and typecheck. Do NOT run them yourself.
+5. **Commit**: Stage and commit — do NOT push
+6. **Token audit**: Report `metrics.tokenEstimate` for the most expensive block
+7. **Final summary**: After testing/re-testing