@fufu1437/dsh-delete-chat

LIMITATIONS

Known limitations

- **A conversation that is generating a response cannot be deleted** until it stops; that is the one hard refusal, and it is deliberate. - **A conversation that was merely opened can be deleted, but its live session object survives** until the Harness restarts (DSH has no public session-release API): the bytes are overwritten and unlinked, yet the session can still appear in the list or create a fresh empty log if you keep sending messages in its open tab. - **Telemetry already exported cannot be recalled**: `session-telemetry-otel` may already have shipped a log prefix to a remote collector in `FEEDBACK_ONLY` mode; this plugin can only erase local data. - **Derived-cache boundary**: removing a request-image cache entry requires the matching record in `files-v3.json`; other derived copies that leave no attachment reference in the log are out of scope. - The legacy `message_feedback.json` sidecar is not read by the current service; this plugin reads and rewrites it directly. - `workspace.json` is edited through the workspace registry API when that service exists, and directly only when it does not (so nothing can overwrite the change from memory). - The default local spill root is a temp directory; if a Harness once used a different `root` that has since been cleaned up, there is nothing left to delete.