Sunset Census - who breaks when you turn the old API off

Find the third-party integrations that will break on a known date - a version sunset, an SDK end of life, a credential expiry, a payload retirement - and decide when the old surface is safe to turn off, then write the outreach plan and the go/no-go memo. Free in your browser: the break-date catalog dated; every integration classified by the migrated rule (no old call for one full business-cycle lookback after the first replacement call, or written confirmation; short logs leave a row unknown; dormant credentials are not migrated; one replacement call proves nothing); the census ranked by days to break and end customers affected, with contract weight promoting a row and the top tier sized by outreach hours; the notification rungs ranked; the door, verified contacts and the five-line readiness gate read; a ranked census CSV and one notice skeleton per integration. A metered run writes the outreach plan, or the go/no-go memo. Built on the SkillSafe skill @samber/integration-health-monitoring, from samber/developer-platform-skills (MIT), by Samuel Berthe.