Under the hood
SDK's outbound message schema-check sampling now uses a renamed rate variable
What
The SDK's internal check that occasionally validates outbound messages against a schema (and reports mismatches via the tengu_sdk_schema_violation telemetry event) still decides randomly whether to run, but now reads its sampling rate from a renamed internal variable, and some of its supporting schema/parsing helper functions were renamed.
Why
This looks like an internal refactor rather than a behavior change readers would notice.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether the sampling rate value itself changed, or only the variable's name, isn't stated; the gate `tengu_sdk_schema_violation` hasn't been…