weight type narrowed number→integer; backoff enum "none" renamed "default"

BreakingBreaking change

This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.

What changed

Three distinct breaking changes in one diff:

The weight field in two allocation-related schemas is narrowed from type: number to type: integer — clients sending decimal weights will now fail validation.
The backoff_type enum loses the value "none" and gains "default" — any client sending or matching "none" will break.
The phone-provider-protection endpoints (GET/PATCH) are promoted from Early Access (EA) to General Availability (GA) — informational, but the x-release-lifecycle change signals a stability commitment.