# Implementation Plans
Generated by the `improve` skill on 2026-07-12 from commit `12495f36`.
Execute in the order below unless dependencies say otherwise. Each executor
must read its plan fully, honor every STOP condition, and update its status row
when done.
## Execution order & status
| 001 | Verify intended compile-fail diagnostics | P1 | M | — | DONE |
| 002 | Execute relational-query suites in CI | P1 | S | 001 | DONE |
| 003 | Compile D1 and Durable drivers for WASM in CI | P1 | S | — | DONE |
| 004 | Remove unsafe implicit SQL interpolation | P1 | M | 001 | DONE |
| 005 | Validate and atomically publish migration artifacts | P1 | M | 001 | DONE |
| 006 | Fail closed on metadata and introspection errors | P1 | L | 001 | DONE |
| 007 | Honor PostgreSQL TLS with structured credentials | P1 | L | 001 | DONE |
## Dependency notes
- 002 follows 001 so the newly enabled `query` compile-fail cases validate the
intended diagnostic, not merely any compiler failure.
- 004–007 follow 001 because each changes correctness-sensitive code and must
retain the project's compile-time guarantees.
- 003 is independent and may run in parallel; it only adds target-specific CI
coverage for code already exported on WASM.
## Findings considered and deferred
- Turso CI currently masks failures with `continue-on-error` and `|| true`.
The maintainer explicitly deferred enforcement until Turso reaches feature
parity; do not fold that work into these plans.
- Other lower-priority audit findings (cache stability, async savepoint
parity, migration concurrency, documentation breadth, and broader
architectural consolidation) were not selected for this execution batch.