Kysely ParseJSONResultsPlugin silently auto-parses TEXT columns

Kysely's ParseJSONResultsPlugin (which many codebases install in the global plugin list — alongside CamelCasePlugin, BooleanPlugin, etc.) walks every SELECT result and runs JSON.parse on ANY TEXT-typed column whose value happens to start with { or [. There is no opt-in, no per-column annotation, no consideration of the declared schema type. So if you write data: JSON.stringify(obj) on INSERT and then JSON.parse(row.data) on SELECT — the natural symmetry — the read side blows up with SyntaxError: "[object Object]" is not valid JSON because the plugin already parsed row.data to an object before your code touched it, and your redundant JSON.parse(object) coerces via toString to literal "[object Object]" and then throws. The whole API endpoint 500s, the client dropdown silently stays empty because the optimistic local cache hides the failure, and meanwhile the rows are landing fine in SQLite. Confirm with sqlite3 from outside the app and you see valid JSON on disk — divergence between disk and API response is the diagnostic. Fix is to remove JSON.parse from the read path entirely; keep JSON.stringify on the write path (the plugin is read-only). Worth knowing: optimistic local caching that mirrors a save into Redux makes silent server-side failures invisible until you check the API in a fresh session, so any sync feature should round-trip-verify by reading back from the server during the save UX, not trust the cache.