Two Kite CLI releases tighten operator control over provider-signed webhook endpoints.
Version v0.2.1 added the option to provide a signing secret when creating the relevant endpoint. Version v0.2.2 followed with provider signing-secret rotation.
Why this belongs in the operator surface
Webhook providers and receiving systems have to agree on the secret used to authenticate a delivery. Treating that material as part of the endpoint lifecycle gives operators a deliberate place to establish and rotate the trust boundary instead of leaving it implicit.
Rotation is the important second half. A secret that can be configured but not replaced becomes operational debt the first time a team needs to change it.
Release record
The shipped scope is intentionally narrow: user-supplied provider signing secrets and rotation support in the Kite CLI release line. It does not imply support for every provider or every possible rotation workflow.
See v0.2.1 and v0.2.2 for the public release record.