EventName:
| "worker.created"
| "worker.updated"
| "worker.deleted"
| "version.created"
| "version.deployed"
| "version.rolled-back"
| "version.reverted"
| "assets.synced"
| "secret.set"
| "secret.deleted"
| "resource.created"
| "resource.deleted"
| "conversion.started"
| "conversion.completed"
| "fleet.applied"
What happened, for whoever is counting.
This library emits; it never decides what an event costs. A CLI running on a customer's laptop self-reporting its own usage is not a meter anyone should bill from, and the boundary that makes that unnecessary is the credential: on a plane whose credential the control plane owns it observes by executing, and on a plane the customer owns the tier is flat so an exact count is not load-bearing for revenue.
A sink is optional. With none configured every operation behaves identically and the events go nowhere.