db-mcp 2.0.0 → 3.0.1

package/test-server/test-advanced/README.md

@@ -1,70 +0,0 @@
-# db-mcp Advanced Stress Tests
-
-> **This document is optimized for AI agent consumption.** It provides context and execution rules for the advanced stress testing suite located in this directory.
-
-This directory contains the "Second-Pass" advanced tests for the `db-mcp` tool groups. These tests simulate complex, edge-case, and boundary interactions using exclusively **Code Mode** (`sqlite_execute_code`).
-
-## Pre-requisites
-
-1. Basic deterministic tool group checklists (located in `../test-tool-groups/*.md`) MUST be successfully passed before running these advanced tests.
-2. Code Mode basic tests (located in `../test-tool-groups-codemode/*.md`) MUST be successfully passed.
-3. The testing database MUST be freshly seeded via `Set-Location C:\Users\chris\Desktop\db-mcp\test-server; .\reset-database.ps1` to ensure deterministic results.
-
-## File Inventory
-
-| File                                      | Primary Focus | Key Validations                                                                           |
-| ----------------------------------------- | ------------- | ----------------------------------------------------------------------------------------- |
-| `test-codemode-advanced-core.md`          | Core          | Boundary values, empty states, state pollution, idempotency, error quality, payload sizes |
-| `test-codemode-advanced-json.md`          | JSON          | Deep nesting, merge conflicts (RFC 7396), type coercion, write safety                     |
-| `test-codemode-advanced-text.md`          | Text          | Regex edge cases, fuzzy/phonetic stress, FTS5 state integrity `[NATIVE ONLY]`             |
-| `test-codemode-advanced-stats.md`         | Stats         | Empty/single-row/NULL-heavy stats, extreme values, window functions `[NATIVE ONLY]`       |
-| `test-codemode-advanced-vector.md`        | Vector        | Empty tables, distance metrics, dimension mismatch, batch operations                      |
-| `test-codemode-advanced-admin.md`         | Admin         | View lifecycle, virtual tables, backup/restore, pragma edge cases                         |
-| `test-codemode-advanced-transactions.md`  | Transactions  | Abort recovery, savepoint stress, execute rollback `[NATIVE ONLY]`                        |
-| `test-codemode-advanced-geo.md`           | Geo           | Haversine boundary conditions, nearby edge cases, SpatiaLite `[NATIVE ONLY]`              |
-| `test-codemode-advanced-introspection.md` | Introspection | Graph analysis, schema snapshot, storage/index audit, query plan depth                    |
-| `test-codemode-advanced-migration.md`     | Migration     | Lifecycle, state pollution, SHA-256 dedup, error paths                                    |
-
-## Agent Execution Protocol
-
-1. **Strict Code Mode Only:** All advanced stress tests must be executed entirely via `sqlite_execute_code`. Direct tool calls are forbidden unless specifically instructed for baseline comparison.
-2. **Sequential Grouping:** Execute only **one markdown file at a time**. Report findings, fix errors, apply updates to the changelog, and commit before advancing to the next file.
-3. **Payload Optimization (Token Monitoring):** Monitor `metrics.tokenEstimate` on every response. If extremely large unbounded responses are produced, flag as 📦 **Payload Issue**.
-4. **Structured Error Adherence:** When testing boundary failure parameters, assert that the handler outputs a proper structured error (`{success: false, error: "..."}`) rather than leaking raw SQLite errors.
-5. **No Persistent Pollution:** After finishing a file, verify all `stress_*` tables/views/indexes are dropped. No test state should bleed into the next run.
-6. **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.
-7. **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.
-8. **Testing Limits**: 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.
-
-### 9. WASM Mode Execution
-
-When testing against a **WASM backend** (`--sqlite` flag, sql.js adapter), follow these additional rules:
-
-#### Skip Rules
-
-- **`[NATIVE ONLY]` items**: Skip all categories and individual test items annotated with `[NATIVE ONLY]`.
-- **Transactions prompt**: Skip entirely — all 8 transaction tools are `[NATIVE ONLY]`.
-- **Window function items** (stats Category 4): Skip — 6 window tools are Native-only.
-- **SpatiaLite items** (geo Category 5): Skip — 7 SpatiaLite tools are Native-only.
-- **FTS5 items** (text Category 6): Skip — 5 FTS5 tools are Native-only.
-
-#### 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.admin.backup(...)`           | `{success: false, error: "...WASM mode"}`      |
-| `sqlite.admin.restore(...)`          | `{success: false, error: "...WASM mode"}`      |
-| `sqlite.admin.verifyBackup(...)`     | `{success: false, error: "...WASM mode"}`      |
-| `sqlite.admin.createCsvTable(...)`   | `{success: false}` — CSV extension unavailable |
-| `sqlite.admin.analyzeCsvSchema(...)` | `{success: false}` — CSV extension unavailable |
-| `sqlite.admin.createRtreeTable(...)` | `{success: false}` — R-Tree module unavailable |
-
-#### Adjusted Expectations
-
-| Item                                                 | Native Behavior             | WASM Behavior                    |
-| ---------------------------------------------------- | --------------------------- | -------------------------------- |
-| `sqlite.admin.dbstat({summarize: true})`             | Per-table storage breakdown | Counts-only (JS fallback)        |
-| `sqlite.admin.pragmaCompileOptions({filter: "FTS"})` | Matches FTS5                | Matches FTS3                     |
-| `test_articles_fts` in `listVirtualTables`           | Present and queryable       | May appear but FTS5 queries fail |

package/test-server/test-advanced/test-codemode-advanced-admin.md

@@ -1,174 +0,0 @@
-# db-mcp Advanced Stress Test — [admin]
-
-> [!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:** Execute each numbered stress test below using `sqlite_execute_code` (code mode).
-
-**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:
-
-- **Category 2**: Item 6 (`createRtreeTable`) — returns `{success: false}` in WASM (R-Tree unavailable). Treat as **negative validation**. Item 7 (`listVirtualTables`) — `test_articles_fts` may appear but is not queryable.
-- **Category 3**: All 3 items (11-13) return `{success: false, error: "...WASM mode"}`. Treat as **negative validation** — verify the structured error, do not skip.
-- **Category 4**: Item 16 (`pragmaCompileOptions` FTS filter) — WASM shows FTS3 instead of FTS5.
-- **Category 5**: Items 21-22 (`analyzeCsvSchema`, `createCsvTable`) — return `{success: false}` in WASM (CSV extension unavailable). Treat as **negative validation**.
-- All other categories are WASM-compatible.
-
-## Code Mode Execution
-
-- **Code Over Docs**: Fix the handler code if standards (Structured Errors/Zod) are violated. Do NOT change docs/prompts to accommodate broken code.
-
-All tests via `sqlite_execute_code`. Use `sqlite.admin.*` for admin tools, `sqlite.core.*` for read/write.
-State persists across calls. Do NOT pass `readonly: true`. Group related tests into single calls.
-
-## Test Database Schema
-
-| Table             | Rows | Key Columns                                            |
-| ----------------- | ---- | ------------------------------------------------------ |
-| test_products     | 16   | id, name, price, category, created_at                  |
-| test_orders       | 20   | id, product_id (FK→test_products), total_price, status |
-| test_articles_fts | —    | FTS5 virtual table (title, body) `[NATIVE ONLY]`       |
-
-> **CSV testing**: Use absolute path `C:\Users\chris\Desktop\db-mcp\test-server\sample.csv`.
-
-## Naming & Cleanup
-
-- **Temporary tables**: `stress_*` prefix
-- **Temporary views**: `stress_view_*` prefix
-- Drop at end. If DROP fails due to lock, note and move on.
-
-## Reporting Format
-
-- ❌ Fail | ⚠️ Issue | 📦 Payload (monitor `metrics.tokenEstimate`) | ✅ Confirmed (inline only)
-
-### Error Message Quality Rating
-
-| Level                                  | Verdict |
-| -------------------------------------- | ------- |
-| 5 - Excellent (name + code + context)  | ✅      |
-| 4 - Good (name)                        | ✅      |
-| 3 - Adequate (raw SQLite, informative) | ⚠️      |
-| 2 - Poor (no object name)              | ⚠️      |
-| 1 - Useless (generic)                  | ❌      |
-
-## Structured Error Response Pattern
-
-Handler error ✅ = JSON with `success` + `error`. MCP error ❌ = raw text, `isError: true`.
-
----
-
-## admin Group Tools (26)
-
-1. sqlite_pragma_database_list
-2. sqlite_pragma_compile_options
-3. sqlite_pragma_settings
-4. sqlite_pragma_table_info
-5. sqlite_pragma_optimize
-6. sqlite_index_stats
-7. sqlite_integrity_check
-8. sqlite_analyze
-9. sqlite_dbstat
-10. sqlite_vacuum
-11. sqlite_optimize
-12. sqlite_create_view
-13. sqlite_list_views
-14. sqlite_drop_view
-15. sqlite_list_virtual_tables
-16. sqlite_virtual_table_info
-17. sqlite_drop_virtual_table
-18. sqlite_create_csv_table
-19. sqlite_analyze_csv_schema
-20. sqlite_create_rtree_table
-21. sqlite_create_series_table
-22. sqlite_generate_series
-23. sqlite_backup
-24. sqlite_restore
-25. sqlite_verify_backup
-26. sqlite_append_insight
-
----
-
-### Category 1: View Lifecycle Stress
-
-1. `sqlite.admin.createView({viewName: "stress_view_orders", selectQuery: "SELECT product_id, COUNT(*) as cnt FROM test_orders GROUP BY product_id"})` → success
-2. `sqlite.admin.listViews()` → verify `stress_view_orders` present
-3. `sqlite.admin.dropView({viewName: "stress_view_orders"})` → success
-4. `sqlite.admin.dropView({viewName: "stress_view_orders"})` → structured error or "not found" (not raw crash)
-5. `sqlite.admin.createView({viewName: "stress_view_orders", selectQuery: "SELECT product_id, COUNT(*) as cnt FROM test_orders GROUP BY product_id"})` → recreate success
-
----
-
-### Category 2: Virtual Table Edge Cases
-
-6. `sqlite.admin.createRtreeTable({tableName: "stress_rtree_test", dimensions: 2})` → success
-7. `sqlite.admin.listVirtualTables()` → verify `stress_rtree_test` present alongside `test_articles_fts` (Native)
-8. `sqlite.admin.virtualTableInfo({tableName: "stress_rtree_test"})` → correct module and column info
-9. `sqlite.admin.dropVirtualTable({tableName: "stress_rtree_test"})` → success
-10. `sqlite.admin.virtualTableInfo({tableName: "nonexistent_vtable_xyz"})` → structured error
-
----
-
-### Category 3: Backup/Restore Integrity
-
-> Use absolute path: `C:\Users\chris\Desktop\db-mcp\test-server\stress-backup.db`
-
-11. `sqlite.admin.backup({targetPath: "C:\\Users\\chris\\Desktop\\db-mcp\\test-server\\stress-backup.db"})` → success
-12. `sqlite.admin.verifyBackup({backupPath: "C:\\Users\\chris\\Desktop\\db-mcp\\test-server\\stress-backup.db"})` → integrity verified
-13. `sqlite.admin.verifyBackup({backupPath: "nonexistent_file.db"})` → structured error
-14. Note backup file for manual removal
-
----
-
-### Category 4: Pragma Edge Cases
-
-15. `sqlite.admin.pragmaCompileOptions({filter: "THREAD"})` → filtered result subset
-16. `sqlite.admin.pragmaCompileOptions({filter: "FTS"})` → filtered to FTS options
-17. `sqlite.admin.pragmaSettings({pragma: "journal_mode"})` → `{value: "wal"}`
-18. `sqlite.admin.pragmaTableInfo({table: "nonexistent_table_xyz"})` → report behavior
-
----
-
-### Category 5: Series & CSV Edge Cases
-
-19. `sqlite.admin.generateSeries({start: 1, stop: 100, step: 1})` → 100 values — check payload size
-20. `sqlite.admin.generateSeries({start: 1, stop: 1, step: 1})` → single value
-21. `sqlite.admin.analyzeCsvSchema({filePath: "C:\\Users\\chris\\Desktop\\db-mcp\\test-server\\sample.csv"})` → inferred types
-22. `sqlite.admin.createCsvTable({tableName: "stress_csv", filePath: "nonexistent_file.csv"})` → structured error
-
----
-
-### Category 6: Error Message Quality
-
-23. `sqlite.admin.dropView({viewName: "nonexistent_view_xyz"})` → structured error
-24. `sqlite.admin.verifyBackup({backupPath: "nonexistent_backup.db"})` → structured error
-25. `sqlite.admin.createCsvTable({tableName: "stress_csv", filePath: "nonexistent_file.csv"})` → structured error
-
----
-
-### Category 7: WASM Boundary Verification
-
-For WASM testing only:
-
-26. Verify that backup/restore/verify, CSV, and R-Tree tools return `{success: false}` structured errors (not crashes). Confirm all other admin tools produce identical results in WASM and Native.
-
----
-
-### Final Cleanup
-
-Drop all `stress_*` tables and views. Confirm `test_products` (16 rows) and `test_orders` (20 rows) unchanged.
-
-## Post-Test Procedures
-
-1. **Cleanup**: Drop all `stress_*` objects
-2. **Fix EVERY finding** — ❌, ⚠️, 📦
-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. **Re-test**: After server rebuild
-6. **Token audit**: Report most expensive block

package/test-server/test-advanced/test-codemode-advanced-core.md

@@ -1,193 +0,0 @@
-# db-mcp Advanced Stress Test — [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.
-
-**Step 1:** Read `C:\Users\chris\Desktop\db-mcp\src\constants\server-instructions\gotchas.md` using `view_file`.
-
-**Step 2:** Execute each numbered stress test below using `sqlite_execute_code` (code mode), not scripts/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): All 14 core tools are fully WASM-compatible. No categories to skip or adjust.
-
-## Code Mode Execution
-
-- **Code Over Docs**: Fix the handler code if standards (Structured Errors/Zod) are violated. Do NOT change docs/prompts to accommodate broken code.
-
-All tests via `sqlite_execute_code`. Translation table:
-
-| Direct Tool Call                            | Code Mode Equivalent                        |
-| ------------------------------------------- | ------------------------------------------- |
-| `sqlite_read_query({query: "..."})`         | `sqlite.core.readQuery({query: "..."})`     |
-| `sqlite_write_query({query: "..."})`        | `sqlite.core.writeQuery({query: "..."})`    |
-| `sqlite_create_table({...})`                | `sqlite.core.createTable({...})`            |
-| `sqlite_describe_table({tableName: "..."})` | `sqlite.core.describeTable("...")`          |
-| `sqlite_drop_table({tableName: "..."})`     | `sqlite.core.dropTable({tableName: "..."})` |
-| `sqlite_create_index({...})`                | `sqlite.core.createIndex({...})`            |
-| `sqlite_get_indexes({...})`                 | `sqlite.core.getIndexes({...})`             |
-
-**Key rules:** State persists across calls. Do NOT pass `readonly: true`. Group related tests into single calls.
-
-## Test Database Schema
-
-| Table             | Rows | Key Columns                                               |
-| ----------------- | ---- | --------------------------------------------------------- |
-| test_products     | 16   | id, name, description, price (REAL), category, created_at |
-| test_orders       | 20   | id, product_id (FK→test_products), total_price, status    |
-| test_measurements | 200  | id, sensor_id (1-5), temperature, humidity, pressure      |
-| test_events       | 100  | id, event_type, user_id, payload (JSON), event_date       |
-
-## Naming & Cleanup
-
-- **Temporary tables**: `stress_*` prefix
-- **Temporary indexes**: `stress_idx_*` prefix
-- If DROP fails due to lock, note and move on.
-
-## Reporting Format
-
-- ❌ Fail: Tool errors or produces incorrect results
-- ⚠️ Issue: Unexpected behavior or improvement opportunity
-- 📦 Payload: Unnecessarily large response — monitor `metrics.tokenEstimate`. Report size in KB.
-- ✅ Confirmed: Edge case handled correctly (inline only; omit from Final Summary)
-
-### Error Message Quality Rating
-
-| Quality Level     | Example                                                             | Verdict |
-| ----------------- | ------------------------------------------------------------------- | ------- |
-| **5 - Excellent** | `Table 'stress_empty_table' does not exist (code: TABLE_NOT_FOUND)` | ✅      |
-| **4 - Good**      | `Table 'stress_empty_table' does not exist`                         | ✅      |
-| **3 - Adequate**  | `SQLITE_ERROR: no such table: stress_empty_table`                   | ⚠️      |
-| **2 - Poor**      | `SQLITE_ERROR: no such table`                                       | ⚠️      |
-| **1 - Useless**   | `Query failed` or generic `Error occurred`                          | ❌      |
-
-### Error Code Consistency
-
-Flag any generic code (`RESOURCE_ERROR`, `UNKNOWN_ERROR`) that should be specific (e.g., `TABLE_NOT_FOUND`, `COLUMN_NOT_FOUND`). Treat as ⚠️.
-
-## Structured Error Response Pattern
-
-Handler error ✅ = JSON with `success` + `error` fields. MCP error ❌ = raw text, `isError: true`.
-
----
-
-## core Group Tools (14 + codemode)
-
-1. sqlite_read_query
-2. sqlite_write_query
-3. sqlite_create_table
-4. sqlite_list_tables
-5. sqlite_describe_table
-6. sqlite_drop_table
-7. sqlite_get_indexes
-8. sqlite_create_index
-9. sqlite_drop_index
-10. sqlite_count
-11. sqlite_exists
-12. sqlite_upsert
-13. sqlite_batch_insert
-14. sqlite_truncate
-
----
-
-### Category 1: Boundary Values & Empty States
-
-**1.1 Empty Table Operations**
-
-Create `stress_empty_table (id INTEGER PRIMARY KEY, name TEXT, value REAL)`, then test:
-
-1. `sqlite.core.readQuery({query: "SELECT COUNT(*) AS n FROM stress_empty_table"})` → `{rows: [{n: 0}]}`
-2. `sqlite.core.describeTable("stress_empty_table")` → valid schema with 3 columns
-3. `sqlite.core.getIndexes({table: "stress_empty_table"})` → empty or primary key only
-4. `sqlite.core.count({table: "stress_empty_table"})` → `{count: 0}`
-5. `sqlite.core.exists({table: "stress_empty_table"})` → `{exists: false}` (no rows)
-
-**1.2 Single-Row Table**
-
-Insert one row: `(1, 'solo', 42.0)`, then:
-
-6. `sqlite.core.readQuery({query: "SELECT * FROM stress_empty_table"})` → exactly 1 row
-7. `sqlite.core.exists({table: "stress_empty_table"})` → `{exists: true}`
-8. `sqlite.core.count({table: "stress_empty_table"})` → `{count: 1}`
-
-**1.3 NULL-Heavy Data**
-
-Insert 4 more rows: 3 with `name IS NULL AND value IS NULL`, 1 with actual values:
-
-9. `sqlite.core.readQuery({query: "SELECT COUNT(*) AS n FROM stress_empty_table WHERE value IS NULL"})` → `{rows: [{n: 3}]}`
-10. `sqlite.core.readQuery({query: "SELECT COUNT(value) AS n FROM stress_empty_table"})` → `{rows: [{n: 2}]}` (COUNT of non-null)
-11. `sqlite.core.count({table: "stress_empty_table", column: "value"})` → 2 (non-null count)
-
-**1.4 Extreme Numeric Values**
-
-Insert: `(value: 99999999.99)`, `(value: -99999999.99)`, `(value: 0.0)`, `(value: 0.01)`:
-
-12. `sqlite.stats.statsBasic({table: "stress_empty_table", column: "value"})` → verify min/max/avg handle extreme values
-
----
-
-### Category 2: State Pollution & Idempotency
-
-**2.1 Create-Drop-Recreate Cycles**
-
-13. `sqlite.core.createTable(...)` → create `stress_cycle_table (id INTEGER PRIMARY KEY, data TEXT)`
-14. `sqlite.core.createIndex({table: "stress_cycle_table", columns: ["data"], indexName: "stress_idx_cycle"})` → success
-15. `sqlite.core.dropTable({table: "stress_cycle_table"})` → success
-16. `sqlite.core.dropTable({table: "stress_cycle_table"})` → expect structured error or `{existed: false}` (not raw crash)
-17. `sqlite.core.createTable(...)` → recreate `stress_cycle_table` → success (no orphaned metadata)
-18. Cleanup: drop `stress_cycle_table`
-
-**2.2 Duplicate Object Detection**
-
-19. `sqlite.core.createTable(...)` with table name `test_products` → expect error or "already exists"
-20. `sqlite.core.createIndex(...)` on existing `idx_orders_status` → expect error or "already exists"
-
----
-
-### Category 3: Error Message Quality
-
-For each test, verify **structured response** (`{success: false, error: "..."}`). Rate each error message 1-5.
-
-**3.1 Nonexistent Objects**
-
-21. `sqlite.core.describeTable("nonexistent_table_xyz")` → error should mention table name
-22. `sqlite.core.readQuery({query: "SELECT * FROM nonexistent_table_xyz"})` → error should mention table name
-23. `sqlite.core.getIndexes({table: "nonexistent_table_xyz"})` → report behavior
-24. `sqlite.core.writeQuery("INSERT INTO nonexistent_table_xyz VALUES (1)")` → structured error
-
-**3.2 Invalid SQL**
-
-25. `sqlite.core.readQuery({query: "SELEKT * FROM test_products"})` → structured error with SQL syntax context
-26. `sqlite.core.writeQuery("INSERT INTO test_products (nonexistent_col) VALUES (1)")` → structured error mentioning column
-
-**3.3 Type/Constraint Violations**
-
-27. `sqlite.core.writeQuery("INSERT INTO test_products (id, name, price, category) VALUES (1, 'dup', 10.0, 'cat')")` → duplicate primary key error (id=1 exists)
-
----
-
-### Category 4: Large Payload & Truncation Verification
-
-28. `sqlite.core.readQuery({query: "SELECT * FROM test_measurements"})` → 200 rows — verify response size, check if truncation is applied
-29. `sqlite.core.readQuery({query: "SELECT * FROM test_measurements LIMIT 5"})` → exactly 5 rows
-30. `sqlite.core.readQuery({query: "SELECT * FROM test_events"})` → 100 rows — check payload size
-
----
-
-### Final Cleanup
-
-Drop all `stress_*` tables. Confirm `test_products` row count is still 16 (no pollution).
-
-## Post-Test Procedures
-
-1. **Cleanup**: Drop all `stress_*` objects
-2. **Fix EVERY finding** — ❌ Fails, ⚠️ Issues, 📦 Payloads. All changes consistent with `code-map.md`
-3. **Scope of fixes**: Handler code, server-instructions, test database, 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. **Re-test**: After server rebuild, re-test fixes with code mode calls
-7. **Token audit**: Report most expensive block

package/test-server/test-advanced/test-codemode-advanced-geo.md

@@ -1,157 +0,0 @@
-# db-mcp Advanced Stress Test — [geo]
-
-> [!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:** Execute each numbered stress test below using `sqlite_execute_code` (code mode).
-
-**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:
-
-- **Skip Category 5** entirely (SpatiaLite Integration — items 15-23) — `[NATIVE ONLY]`.
-- **Category 6**: Skip item 26 (`spatialiteQuery`) — `[NATIVE ONLY]`.
-- **Category 7** (WASM Boundary Verification) — execute only in WASM mode.
-- Categories 1-4, 6 (items 24-25) are fully WASM-compatible (4 Haversine tools).
-
-## Code Mode Execution
-
-- **Code Over Docs**: Fix the handler code if standards (Structured Errors/Zod) are violated. Do NOT change docs/prompts to accommodate broken code.
-
-All tests via `sqlite_execute_code`. Use `sqlite.geo.*` for geo/SpatiaLite tools.
-State persists across calls. Do NOT pass `readonly: true`. Group related tests into single calls.
-
-## Test Database Schema
-
-| Table          | Rows | Key Columns                               |
-| -------------- | ---- | ----------------------------------------- |
-| test_locations | 15   | id, name, city, latitude, longitude, type |
-
-**Key coordinates:**
-
-| Name               | City          | Lat      | Lng       |
-| ------------------ | ------------- | -------- | --------- |
-| Central Park       | New York      | 40.7829  | -73.9654  |
-| Eiffel Tower       | Paris         | 48.8584  | 2.2945    |
-| Big Ben            | London        | 51.5007  | -0.1246   |
-| Tokyo Tower        | Tokyo         | 35.6586  | 139.7454  |
-| Sydney Opera House | Sydney        | -33.8568 | 151.2153  |
-| Golden Gate Bridge | San Francisco | 37.8199  | -122.4783 |
-
-## Naming & Cleanup
-
-- **Temporary tables**: `stress_*` prefix. Drop at end using `sqlite.core.dropTable({table: "..."})`. Do NOT use `writeQuery` for `DROP TABLE` as DDL commands are blocked by the query executor.
-
-## Reporting Format
-
-- ❌ Fail | ⚠️ Issue | 📦 Payload (monitor `metrics.tokenEstimate`) | ✅ Confirmed (inline only)
-
-## Structured Error Response Pattern
-
-Handler error ✅ = JSON with `success` + `error`. MCP error ❌ = raw text, `isError: true`.
-
----
-
-## geo Group Tools — Native (11)
-
-1. sqlite_geo_distance
-2. sqlite_geo_nearby
-3. sqlite_geo_bounding_box
-4. sqlite_geo_cluster
-5. sqlite_spatialite_load `[NATIVE ONLY]`
-6. sqlite_spatialite_create_table `[NATIVE ONLY]`
-7. sqlite_spatialite_query `[NATIVE ONLY]`
-8. sqlite_spatialite_analyze `[NATIVE ONLY]`
-9. sqlite_spatialite_index `[NATIVE ONLY]`
-10. sqlite_spatialite_transform `[NATIVE ONLY]`
-11. sqlite_spatialite_import `[NATIVE ONLY]`
-
-### WASM (4)
-
-Only the Haversine-based tools: items 1-4.
-
----
-
-### Category 1: Haversine Boundary Conditions
-
-1. `sqlite.geo.distance({lat1: 0, lon1: 0, lat2: 0, lon2: 0})` → distance = 0 (same point)
-2. `sqlite.geo.distance({lat1: 90, lon1: 0, lat2: -90, lon2: 0})` → antipodal ≈ 20,015 km (half Earth circumference)
-3. `sqlite.geo.distance({lat1: 0, lon1: -180, lat2: 0, lon2: 180})` → ≈ 0 (same point, opposite notation)
-4. `sqlite.geo.distance({lat1: 91, lon1: 0, lat2: 0, lon2: 0})` → report behavior for out-of-bounds latitude (>90°)
-5. `sqlite.geo.distance({lat1: 0, lon1: 181, lat2: 0, lon2: 0})` → report behavior for out-of-bounds longitude (>180°)
-
----
-
-### Category 2: Nearby Search Edge Cases
-
-6. `sqlite.geo.nearby({table: "test_locations", latColumn: "latitude", lonColumn: "longitude", centerLat: 40.7829, centerLon: -73.9654, radius: 0.1})` → very small radius — only Central Park (within 100m)
-7. `sqlite.geo.nearby({table: "test_locations", latColumn: "latitude", lonColumn: "longitude", centerLat: 40.7829, centerLon: -73.9654, radius: 50000})` → very large radius — ALL 15 locations
-8. `sqlite.geo.nearby({table: "test_locations", latColumn: "latitude", lonColumn: "longitude", centerLat: 0, centerLon: 0, radius: 100})` → no locations near (0,0) — 0 results (not error)
-
----
-
-### Category 3: Bounding Box Edge Cases
-
-9. `sqlite.geo.boundingBox({table: "test_locations", latColumn: "latitude", lonColumn: "longitude", minLat: -90, maxLat: 90, minLon: -180, maxLon: 180})` → all 15 locations (global bounding box)
-10. `sqlite.geo.boundingBox({table: "test_locations", latColumn: "latitude", lonColumn: "longitude", minLat: 0, maxLat: 0, minLon: 0, maxLon: 0})` → 0 results (point bounding box)
-11. `sqlite.geo.boundingBox({table: "test_locations", latColumn: "latitude", lonColumn: "longitude", minLat: 50, maxLat: 52, minLon: -1, maxLon: 1})` → London locations (Big Ben, Tower Bridge, Buckingham Palace)
-
----
-
-### Category 4: Clustering Edge Cases
-
-12. `sqlite.geo.cluster({table: "test_locations", latColumn: "latitude", lonColumn: "longitude", gridSize: 180})` → ~3 clusters (huge grid splits logically along Prime Meridian/Equator)
-13. `sqlite.geo.cluster({table: "test_locations", latColumn: "latitude", lonColumn: "longitude", gridSize: 0.001})` → ~15 clusters (tiny grid, one per location)
-14. `sqlite.geo.cluster({table: "test_locations", latColumn: "latitude", lonColumn: "longitude", gridSize: 0.1})` → approximately one cluster per city
-
----
-
-### Category 5: SpatiaLite Integration `[NATIVE ONLY]`
-
-15. `sqlite.geo.spatialiteLoad()` → verify version string returned
-16. `sqlite.geo.spatialiteCreateTable({tableName: "stress_geo_spatial", geometryColumn: "geom", geometryType: "POINT", srid: 4326, additionalColumns: [{name: "name", type: "TEXT"}, {name: "type", type: "TEXT"}]})` → success
-17. Import 3 points (NYC, Paris, Tokyo) via `sqlite.geo.spatialiteImport`
-18. `sqlite.geo.spatialiteQuery({query: "SELECT name, AsText(geom) FROM stress_geo_spatial"})` → 3 rows with WKT
-19. `sqlite.geo.spatialiteTransform({operation: "buffer", geometry1: "POINT(-73.9654 40.7829)", distance: 0.01})` → buffered polygon
-20. `sqlite.geo.spatialiteTransform({operation: "centroid", geometry1: "POLYGON((-74 40, -74 41, -73 41, -73 40, -74 40))"})` → centroid point
-21. `sqlite.geo.spatialiteIndex({tableName: "stress_geo_spatial", geometryColumn: "geom", action: "create"})` → R-Tree index
-22. `sqlite.geo.spatialiteIndex({tableName: "stress_geo_spatial", geometryColumn: "geom", action: "check"})` → index integrity
-23. `sqlite.geo.spatialiteAnalyze({analysisType: "spatial_extent", sourceTable: "stress_geo_spatial", geometryColumn: "geom"})` → spatial extent
-
----
-
-### Category 6: Error Message Quality
-
-24. `sqlite.geo.nearby({table: "nonexistent_table_xyz", latColumn: "lat", lonColumn: "lon", centerLat: 0, centerLon: 0, radius: 100})` → structured error
-25. `sqlite.geo.nearby({table: "test_locations", latColumn: "nonexistent_col", lonColumn: "longitude", centerLat: 0, centerLon: 0, radius: 100})` → structured error about column
-26. `sqlite.geo.spatialiteQuery({query: "SELECT * FROM nonexistent_table_xyz"})` `[NATIVE ONLY]` → structured error
-
----
-
-### Category 7: WASM Boundary Verification
-
-For WASM testing only:
-
-27. Confirm SpatiaLite tools (items 5-11) are NOT present in the tool list
-28. All 4 Haversine tools should produce identical results in WASM and Native
-
----
-
-### Final Cleanup
-
-Drop `stress_*` tables (if created) using `sqlite.core.dropTable({table: "..."})`. (Note: SpatiaLite index shadow tables like `idx_stress_*` will be automatically cleaned up by `Set-Location C:\Users\chris\Desktop\db-mcp\test-server; .\reset-database.ps1`). Confirm `test_locations` count is still 15.
-
-## Post-Test Procedures
-
-1. **Cleanup**: Drop all `stress_*` objects
-2. **Fix EVERY finding** — ❌, ⚠️, 📦
-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. **Re-test**: After server rebuild
-6. **Token audit**: Report most expensive block