Unclear No reading has been taken of either tengu_playful_lobster or tengu_playful_lobster_fired yet, so it's unclear what enforcement, if any, this telemetry is meant to precede.
When a file read is auto-allowed by the edit-implies-read rule or the working-directory rule, the permission evaluator now also stats the resolved path and checks whether it's a hardlinked file (nlink > 1). If so it fires tengu_playful_lobster_fired with the triggering step, the permission mode, and a hardcoded mode: "shadow", deduped per mode and path with a cap. The actual allow/deny outcome is unchanged; this only measures how often hardlinked files pass through these rules.
tengu_playful_lobster Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.235: on
Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you
No reading has been taken of either `tengu_playful_lobster` or `tengu_playful_lobster_fired` yet, so it's unclear what enforcement, if any…
New in this build: tengu_playful_lobster