Write Failures at Commit for market_data Database with Internal MotherDuck Error After Storage Engine Migration

Hi team — all writes to ONE of my databases (`market_data`) have failed at COMMIT for ~17 hours. Every COMMIT returns "internal MotherDuck error" with a fresh error ID each time. Error IDs (sample): 0996dd57, 8e639180 — many more since ~2026-06-25 20:40 CST. I've already isolated it to the `market_data` database specifically: • Reads from market_data: WORK • CREATE DATABASE / DROP DATABASE: WORK • CREATE TABLE + INSERT + COMMIT into a *freshly created* database: WORK • CREATE TABLE / INSERT (even 5 rows) into `market_data`: FAIL at COMMIT • Both a scheduled job and manual queries fail identically — only on market_data So account / billing / compute are all fine; the commit/catalog path for the `market_data` database itself looks wedged — likely since the recent DuckLake / storage-engine migration. Versions: DuckDB v1.5.3, MotherDuck client v1.5.3-2026-06-237. Could someone please investigate and repair the write path for `market_data`? Thanks!