Under the hood
Useful1 Signal3
Six telemetry events for machine-run cloud hooks exist but cannot fire in this build.
Device-hook telemetry is fully written behind the gate that returns false.
What's wrong with this entry?
Anonymous. No account, no email.
What
The machine-side hook client reports each forwarded hook it serves and each registration attempt, plus consent notices, lapse lines and pinning outcomes. All of it sits behind the device-hooks gate that returns false in this build.
Details
tengu_device_hook_servedcarries event, kind, outcome, exit class, duration, whether paths were translated, and whether the run was a replay, blocked, staged, repinned, or waited.tengu_device_hooks_client_registercarries outcome, trigger, counts of forwarded, templates, held and accepted or ignored entries, and attempt number.- Also
tengu_device_hooks_consent_notice,tengu_device_hooks_lapse_line,tengu_device_hooks_reach_pinned,tengu_device_hooks_source_pinned. - Successful lease renewals are deliberately not reported.
- None of these names exist in 2.1.241.
Evidence
tengu_device_hook_served
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