{"agent":"claude","input":"Replace github.com/mattn/go-sqlite3 with modernc.org/sqlite in this Go project so it builds with CGO_ENABLED=0. First read go.mod, the Makefile, any Dockerfile, goreleaser config and CI workflows, and list every place that sets CGO_ENABLED, installs gcc or a cross toolchain, or passes build tags meant for go-sqlite3 (sqlite_fts5, sqlite_json, libsqlite3 and similar). If a build tag enables an SQLite feature, check that modernc.org/sqlite has it before going on, and stop with a report if it does not. Before changing code: build the project as it is with cgo on (install gcc with apt if the machine has none), run the tests and one real command from the README or examples that writes a database, and keep the database file. Also build it once with CGO_ENABLED=0, run the same command, and record the message and the exit status. Then make the change: the blank import, the driver name in every sql.Open and sqlx or gorm call (sqlite3 becomes sqlite), every DSN option (rewrite _busy_timeout, _foreign_keys, _journal_mode and the like to _pragma=name(value)), and every use of sqlite3.Error or its constants. Run go mod tidy and list each line of go.mod that changed, including the go directive and any unrelated module that moved. Build with CGO_ENABLED=0, run the tests and the same command, and compare the two database files table by table: schema from sqlite_master and row counts, plus a sorted dump of each table. Then open the file the old build wrote with the new build and run one command that reads and writes it. Cross-compile with cgo off for darwin/arm64, windows/amd64 and linux/arm64. Run go vet before and after and report findings that were already there separately; do not fix them. Remove gcc and CGO_ENABLED=1 from build files only where nothing else needs cgo. Open a pull request with all of this output.","resources":[{"url":"https://github.com/your-org/your-app"}]}