@andrewhmir/dsh-plan-review

LIMITATIONS

Known limitations

- **The `[plan-review]` protocol only.** The harness's native plan-mode review (`exit_plan_mode`, architect preset) is a separate, shipped surface and is deliberately not touched — this plugin exists to render superpowers plan files. - **Plan files must live under a workspace root.** A plan outside every registered root is refused by design (the error names the path so it can be fixed). The route only serves markdown/text plan files (`.md`, `.markdown`, `.mdown`, `.mkd`, `.mdx`, `.txt`), never arbitrary workspace files. - **Drafts are per browser tab.** Comments survive closing and reopening the review in the same tab (`sessionStorage`); they are not synced to another tab or device, and answering the review clears them. - **Malformed answers are capped.** The encoded answer stays under the profile's tool-result pruner budget; if it had to shrink, the payload says `"truncated": true` so the agent can ask rather than silently missing notes. - **English panel copy.** Package metadata is bilingual; in-panel strings are English in this version. - **Web GUI only.** The host route is generic, but the takeover and comments are Web-client features. - **The composer is occupied while reviewing.** That is the same seat the shipped question card takes; dismissing the review returns the composer. - **Quote-based anchoring.** A comment is tied to the exact text the user selected; if a plan is rewritten mid-review (it is not, by this plugin), the comment shows `passage not found`. - **A future host protocol change can shadow this plugin.** Claiming depends on the documented `conversation.composer` chain and the `[plan-review]` header; if a future harness ships its own renderer for that header, its composer entry may win.