Garry Tan 8e46c6e521 fix(telemetry): ingest keeps error_message/failed_step instead of dropping them ... The telemetry_events columns exist and bin/gstack-telemetry-log already sends error_message + failed_step, but the Supabase ingest function dropped both fields on insert — every error report arrived with no message and no failing step. Map them through with the same bounded-length sanitization as error_class (500/100 chars). The completion-status resolver now also passes --error-message/--failed-step in the generated skill telemetry block, with instructions to leave them empty on success. Resolver only for the template side; generated SKILL.md files regenerate from this source in the docs lane. Contributed by @sunnnybala (PR #769). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-08-14 20:21:00 -07:00
..
community-pulse	v1.58.4.0 fix: high-priority community bug wave + PTY plan-mode smoke gate (#2077)	2026-06-21 07:15:19 -07:00
telemetry-ingest	fix(telemetry): ingest keeps error_message/failed_step instead of dropping them	2026-08-14 20:21:00 -07:00
update-check	feat: opt-in usage telemetry + community intelligence platform (v0.8.6) (#210)	2026-03-19 17:21:05 -07:00