Auto-replies to artifact comments share the edit deadline and stop blaming API retries for slowness.
What's wrong with this entry?
Composing an automatic reply to an artifact comment now has the same deadline as composing an edit, and both read the same override key composeDeadlineMsOverride instead of the edit-only one. Neither now reports a failure when the only reason it ran long was an API retry.
- Timeout telemetry gained a
request_delayedfield, and a newreply_compose_timeoutevent covers the reply path. - An edit compose that timed out purely because the request was being retried returns nothing rather than a
timed_outdecision, so no failure reply is posted.
reply_compose_timeout, composeDeadlineMsOverride, request_delayed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.