dsh-delete-session

LIMITATIONS

Known limitations

<a id="known-limitations-and-deferred-work"></a> - **The entry points are DOM-injected.** The sidebar exposes no additive slot in either location, so both attach to product-owned markup. The CSS-module suffix match (`_sectionHeader`, `_headerActions`) is the deliberate stability boundary — the prefix hash changes every upstream build — but a markup change beyond it needs a plugin update. - **A live conversation is only hidden.** Deleting a conversation the host still holds in memory removes its files and its row, and the archive set keeps it out of every grouping, but the process keeps the object until it restarts. - **Deleting the conversation you are viewing leaves you on the empty state.** The product's archive watcher clears the selection; the plugin does not pick a replacement conversation for you. - **Deletion is one-way in both directions.** There is no unarchive or restore: the archive set hides, the log directory is gone. - **Only two paths are removed.** The log directory and the projection-cache entry. Attachment blobs, workspace records, and anything else a deployment stores for a session are left in place. <a id="dev-note"></a> ### Dev Note <details> <summary>Maintainer context — click to expand</summary> Two dependency-free smoke tests cover both halves and run without DSH: ```sh npm test