Integration Pulse - let partners see their own broken integrations

Audit what an external developer can find out about their own failing integration, find whose fault each breaking integration is, then write the visibility design and the outreach. Free in your browser: the support-ticket pile classified by failure class against what integrators see today, with the self-serve baseline and the coverage gaps; every integration's error rate split into 4xx, 5xx and 429 against its own baseline; silent integrations caught by a volume drop; blame read against your deploys and their releases; breaking integrations ranked by installs; the visibility, request-ID and notification rungs ranked; the gates - failure-class coverage, request-ID resolvability, tagging at ingestion, retention against time to notice, no alert per failure - an audit table and a fleet CSV. A metered run writes the visibility design, or the outreach. Built on the SkillSafe skill @samber/integration-error-observability, from samber/developer-platform-skills (MIT), by Samuel Berthe.