Diagnostic
$500
- One target surface reviewed.
- One reduced repro or risk report when a bug is found.
- Short mitigation plan if no clean fix is feasible.
48-hour compatibility pass for database, sync, and query teams
Find one real engine or SDK bug before your users do.
I run a focused fuzzing and differential-testing sprint against one narrow surface: SQL compatibility, query planning, schema rewrites, sync edge cases, SDK adapters, or import/export paths. The deliverable is a reduced repro, a fix PR when feasible, and a maintainer-grade writeup.
Recent 90-minute trace
2 PRs + 1 open issue
Differential fuzzer signalSQLite succeeded while Turso rejected a temp-trigger schema rewrite
Find
Three-statement reproReduced to CREATE TABLE, CREATE TEMP TRIGGER, ALTER TABLE RENAME COLUMN
Reduce
Patch and testsNormal and MVCC regression, CLI repro, exact fuzzer seed all pass
Fix
Upstream PRTurso PR #7144 was submitted from a clean branch with the regression attached
Ship
Invalid SQL mutation reportSQLite rejects an undefined CTE column while Turso accepts the UPDATE and mutates data
Report
Fixed-scope sprint
Best fit when you have a risky compatibility surface but not enough time for broad QA.
48-hour sprint
$1,000
- Focused fuzzing or differential test harness pass.
- Reduced repro and failing test.
- Patch PR when the fix is inside a small, safe scope.
Handoff plus
$1,500
- Everything in the sprint.
- Repro suite and maintainer notes.
- Follow-up hardening checklist for your team.
Shipped proof
These are real public artifacts, not screenshots of intent.
Turso issue #7146
Reduced invalid CTE UPDATE repro: SQLite errors and leaves data unchanged, while Turso accepts the statement and mutates a row.
Turso PR #7144
Fixes ALTER TABLE RENAME COLUMN when a TEMP trigger targets a main table. Includes the regression and exact fuzzer seed validation.
Turso PR #7143
Fixes a subquery scheduling panic around aggregate arguments and FILTER predicates.
Context OS
Installable GitHub Action for agent-context cost and failure-surface checks.
Agent cost leak checker
Public repo scanner showing how I package technical findings into operator-readable outputs.
Send one risky surface.
Good inputs: a repo link, a failing compatibility area, a query feature, an SDK adapter, or one engine behavior you do not fully trust.