Plugin version caching could stage and atomically move entries, but only with the off-by-default storage backend.
A staged publish path for the plugin version cache exists but runs only when a default-off storage flag is on.
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: 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
What's wrong with this entry?
Caching a plugin version can now build the entry in a staging directory and move it into place atomically, with named handling for interrupted or concurrent writes. It runs only when the storage backend flag tengu_hover_rest is on, which is off by default; otherwise the old copy-in-place behaviour is used.
- Explicit cases handled: a stray symlink sitting at the cache path, leftover debris with no payload, another session recorded as using the entry, and an archive write that fails after the copy succeeded (the completed directory is kept rather than deleted).
- Failure paths carry distinct diagnostic labels, such as "plugin cache staged publish could not complete".
plugin cache staged tree swapped before publishing
Strings lifted out of the shipped bundle, so the claim above can be checked against them.