[senadir]

Related issues

• Related to Fix BINARY and VARBINARY column defaults WordPress/sqlite-database-integration#596

How AI was used in this PR

Indent bumped the pinned version and compared the v3.1.2 and v3.1.3 release zips to check nothing Studio depends on changed.

Proposed Changes

• Updates the bundled SQLite integration from v3.1.2 to v3.1.3. It includes the fix for BINARY and VARBINARY column defaults (Fix BINARY and VARBINARY column defaults WordPress/sqlite-database-integration#596), plus identifier quoting fixes in LOCK TABLES, SHOW TABLES and compound primary key indexes, and MySQL lexer fixes.
• db.copy is unchanged between the two releases (drop-in still 1.8.0), and the WP_SQLite_Driver / WP_SQLite_Connection constructors the phpMyAdmin DBI extension uses are unchanged. Studio doesn't reference the lexer token constants that Proof-of-concept: Calling /me/sites API endpoint #607 renamed.
• Existing sites pick up the new plugin through keepSqliteIntegrationUpdated on next start, as with previous bumps.

Testing Instructions

• Run node --experimental-strip-types scripts/download-wp-server-files.ts (or npm install, which runs it in postinstall) and check wp-files/sqlite-database-integration/load.php reports Version: 3.1.3.
• Run npm run cli:build, create a site and start it. Confirm wp-content/mu-plugins/sqlite-database-integration/load.php is 3.1.3 and the site loads.
• Start an existing site and confirm it still loads with its content intact.
• Import a SQL dump containing a table with a BINARY or VARBINARY column that has a default value; it should import correctly.
• Open phpMyAdmin for the site and check the tables are listed.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

Tag @indent to continue the conversation here.