Custom session titles can be written through the storage backend, falling back to plain files.
What's wrong with this entry?
Writing or deleting the small file that holds a session's custom title now tries the storage backend first, when that backend is enabled and a handle was supplied, and falls back to direct filesystem create and remove otherwise. Failures are logged at error level with a message ending in "via storage".
- The plugin and marketplace loaders use the same try-storage-then-filesystem shape, now threading credentials through catalog fetches, and gained a path for reading a preview catalog.
deleteSessionTitleSidecar:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.