Compaction, history purge, session moves, recordings and skill reads all gained storage-backed twins that never run.
Six subsystems have a second implementation routed through an optional storage layer whose factory has an empty body, so every branch falls back to the filesystem.
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?
Transcript compaction, history-purge counting and rewriting, session-directory moves, asciicast recording writes, a deep-link registration marker and skill-as-plugin SKILL.md reads all gained a second implementation that goes through an optional storage layer. None of it can run here: the factory that would build that layer has an empty body and returns nothing, so every one of these branches falls back to the normal filesystem code.
- Each branch is selected only when the gate
tengu_hover_rest(fallback off) is on and a backend object exists, and the gate value is read once per process. - The alternative compaction path carries its own failure reasons
snapshot_mid_line,shared_inodeandsource_changed, reported undertengu_transcript_compact_failed. - The session-move path includes a warning for leftovers stranded by a partial move.
performCompactTranscriptV5
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.223
Compare-and-swap retry helper for versioned storage keys
Both mention storage backend
-
v2.1.223
Daemon lock and auto-update lock gained storage-backend implementations
Both mention storage backend
-
v2.1.223
Deep-link registration and cleanup sentinels can be stored as state keys
Both mention storage backend