Device-hook telemetry is fully written behind the gate that returns false.
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
Strings lifted out of the shipped bundle, so the claim above can be checked against them.