gstack/supabase/functions/telemetry-ingest
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
..
index.ts fix(telemetry): ingest keeps error_message/failed_step instead of dropping them 2026-08-14 20:21:00 -07:00