Three more telemetry shapes cover hook template runs, uploads and expiring registrations.
Template telemetry emits only from the gated device-hook handlers.
What's wrong with this entry?
Three more event shapes cover the template path: a per-run event with template id, outcome, duration and dropped fields; an upload event with outcome, template and byte count; and one for a registration lease expiring. Emitted only from the gated device-hook handlers.
- The existing registration event gained a count of templates installed alongside those awaiting upload and those refused.
- It also records how long the handler waited for the account flags, capped at 5000 ms, and whether it shared an already in-flight flag read.
tengu_device_hook_template_upload
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook