Tool outputs show literal 'undefined' and DuckDB concurrent access crashes

[anandgupta42]

Problem

1. 8 tools output literal undefined in their formatted output when native handlers return missing/optional fields. This is visible to users as broken text like [high] undefined: undefined in safety analysis output.

2. DuckDB driver crashes with database is locked when concurrent sessions access the same database file. No retry or fallback to read-only mode.

3. 3 tools don't propagate exceptions to metadata.error in their catch blocks, which means telemetry can't classify these errors.

Impact

• Users see garbage undefined text in tool outputs across sql-analyze, schema-inspect, sql-translate, dbt-manifest, finops-analyze-credits, warehouse-list, altimate-core-check, altimate-core-rewrite
• DuckDB users experience random crashes when running multiple queries
• Telemetry misses error classification for schema-inspect, dbt-manifest, warehouse-list failures

Found via

1,185 automated simulations (839 mock + 346 real E2E) across 10 personas, 11 dialects, and 14 use-case categories.