mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-26 18:31:34 +01:00
Review revisions to the connector telemetry proposal (#13578): - One completion event per gateway execution: success paths emit only after post-save bookkeeping settles, so a bookkeeping failure that overwrites the row to failed cannot produce a contradictory succeeded+failed pair for the same execution. - Policy denies and rate limits (rows born terminal in recordInvocation) now emit at their only completion boundary. - Composio child disable/restore emit from committed .returning() rows only; a concurrently deleted child or failed write emits nothing. Adds a test seam to reproduce that race deterministically. - The invocation emitter skips its database read entirely while the proposed event name is unregistered (TelemetryClient. isRegisteredEventName), and loads invocation+connection in a single joined query once registered. - Integration tests against the real gateway and tool-access services (embedded Postgres): success, post-success audit failure, execution failure, deny/rate-limit, approval pending/decline/approve, setup-test origin, idempotent replay, telemetry failure isolation, composio cascade/no-op/concurrent-delete/failed-write/restore. - Shared tests prove the proposal wrappers cannot queue or send through the real TelemetryClient and cover disabled/CI suppression. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>