Andrey Avtomonov 5d17469601 fix(telemetry): classify daemon query rejections as expected, not faults (#335) ... * fix(telemetry): classify daemon query rejections as expected, not faults Semantic-layer query rejections and warehouse-execution rejections from the sl_query MCP tool were wrapped as generic Errors, so reportException filed them as PostHog $exception faults indistinguishable from real ktx bugs. The daemon already separates a caller rejection (planner ValueError -> exit 3 / HTTP 400) from a crash. The Node runner now carries that distinction as a typed KtxDaemonComputeError, and a shared throwClassifiedQueryError promotes daemon input-rejections and warehouse rejections to KtxQueryError while daemon crashes and native JS faults still reach Error Tracking. query_semantic_layer stops report_exception-ing expected ValueErrors, and a missing 'file:' secret now raises KtxExpectedError so absent .ktx/secrets/<conn>-password stops filing faults. * chore: sync uv.lock to ktx-daemon/ktx-sl 0.15.0		2026-07-03 22:39:34 +02:00
..
__snapshots__	feat: query_policy semantic-layer-only restricts agents to predefined semantic-layer measures (#334)	2026-07-03 08:54:17 +00:00
connection-list-federated.test.ts	feat(duckdb): cross-database federation via derived DuckDB connection (#295)	2026-06-15 15:01:39 +00:00
dialect-notes.test.ts	feat: Add duckdb connector (#308)	2026-07-01 12:06:02 +00:00
local-project-ports-federated.integration.test.ts	feat(duckdb): cross-database federation via derived DuckDB connection (#295)	2026-06-15 15:01:39 +00:00
local-project-ports.test.ts	fix(telemetry): classify daemon query rejections as expected, not faults (#335)	2026-07-03 22:39:34 +02:00
logger.test.ts	feat: ktx batch — scan resilience, analytics SQL craft, connector hardening (#312)	2026-06-29 16:35:57 +00:00
server.test.ts	feat: ktx batch — scan resilience, analytics SQL craft, connector hardening (#312)	2026-06-29 16:35:57 +00:00