dsh-plugin-backlog-md

LIMITATIONS

Known limitations

- **Markdown is preserved, not parsed.** Descriptions are displayed and edited as Markdown source in a monospace textarea. The plugin deliberately does not add a second Markdown parser. Renderers elsewhere in Harness still own rich rendering. - **Permanent delete needs the CLI.** Backlog.md exposes archive, not hard delete, over HTTP. The permanent delete action is therefore archive plus the official `backlog task delete` CLI; it can refuse a task that still has subtasks or links, and the panel reports that refusal. - **External server discovery is bounded.** The manager can verify an existing server only on the project's configured default port. Servers on arbitrary ports are not probed. - **One Host, one manager.** Servers are shared across sessions in the same Harness Host. Separate DSH processes each manage their own server; the plugin does not coordinate across processes. - **Agent activity is not inferred.** The panel shows task state. It does not claim an agent is working on a task merely because its status is In Progress. - **Send to Chat depends on the composer.** It uses the official `inputActions.setDraft` when the panel receives it, with a launcher event fallback. If the composer is unavailable, the panel reports that it could not reach it.