mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-10-30 17:27:09 +00:00
The first 24h of v0.8.47 telemetry showed 30 declines against 25 successes on the dom family, and 26 of those 30 were `ineligible_operation` -- a single opaque string standing in for four unrelated causes. That made the number unactionable: a structural edit the SDK has no vocabulary for (expected, and permanent until the op mapping grows) looked exactly like a reserved-attribute or unsafe-attribute decline (narrow, and possibly worth fixing). `sdkCutoverIneligibleReason` now names which check failed: unsupported_op_type, child_scoped_op, reserved_attribute, unsafe_html_attribute, no_ops, or target_unaddressable. `shouldUseSdkCutover` is derived from it rather than duplicating the conjunction, so the predicate and its explanation cannot drift -- a test pins that agreement across every case. Also separates the two conditions that are not properties of the op batch at all: with the dom family disabled, sdkCutoverPersist reported `ineligible_operation`, which read as "the SDK cannot express this edit" when the truth was "this family is switched off". It now reports feature_disabled and session_unavailable distinctly, matching the other four chokepoints. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>