dsh-edit-turn

LIMITATIONS

Known limitations

- **Human prompts and model replies** are both editable; injected context rows and the system prompt offer no edit entry. - **Editing a reply replaces it with plain text**: the tool calls and reasoning inside it are removed (the editor warns first), because their results are no longer valid. - **Editing a user message replaces that one message and leaves the rest of the conversation untouched - no re-run unless `rerun: true`**; editing a model reply only replaces the text and never asks the model again. - **A prompt edit touches only that message.** The reply under it and the whole conversation after it are kept - no re-run unless `rerun: true`. A **reply edit** removes that answer and everything built on it, because a changed answer invalidates what followed. Keeping the original as a branch needs `sessionController.fork({ sessionId, atSeq })`, which is not implemented. - **Text only.** A message carrying image or file attachments keeps its text and drops them (the editor warns first). - **The session must be open in DSH**, otherwise the route answers `409 session-not-active`. - **Running work is refused**: an unclosed turn or an in-flight compaction answers `409 busy`. - **The rollback is durable; the hiding is not.** Once written, the rollback permanently changes the model context. Hiding those rows in the transcript is this plugin's browser half. Uninstall the plugin and the old rows reappear - while the rollback in the model context still stands, because the replacement is an official event that outlives the plugin. - **The system prompt is never touched**: the window can never include surface node 0, and that node is never editable. - **Old sessions (v3-format logs) cannot be read under DSH 0.1.7**: the session reader answers `session-not-found` for them, so the plugin does not work in one at all (the visible symptom is no edit entry). Newly written sessions are v4 and work normally.