Caching a plugin version now writes to a staged directory that gets atomically moved into place, with explicit handling for a stray symlink already at the cache path, leftover payload-free debris, another session recorded as using the same cache entry, and an archive write that fails after the copy already succeeded (in which case the completed directory is kept rather than discarded). Failure paths carry distinct diagnostic labels, such as "plugin cache staged publish could not complete".
This storage-backed behavior sits behind the tengu_hover_rest gate, which v2.1.234 compiled on by default; no reading of it has been taken under this release yet, and the flag server has returned off for both this site's account and the anonymous baseline.
tengu_hover_rest Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.235: off
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
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.