feat: complete SHD MCP plugin workflows and widget

2026-08-24 17:25:38 +03:00
parent 39fb5c02b7
commit 08cf3672a4
86 changed files with 1707 additions and 5 deletions
@@ -0,0 +1,26 @@
+---
+name: shd-discussions
+description: Use when the user asks to find, read, search, create or edit SHD discussion channels, topics, messages or attachments.
+---
+
+# SHD discussions
+
+See `references/discussion-contract.md` for the tool map and message safety
+rules.
+
+## Resolve and read
+
+- Resolve the organization or project context before selecting a channel.
+- Use `shd_list_discussion_channels` and `shd_list_discussion_topics` before
+  reading messages when an ID is not already known.
+- Use bounded reads with `shd_list_discussion_messages` or
+  `shd_search_discussions`; preserve pagination and returned identifiers.
+- Treat private channels and messages as server-authorized data. Do not infer
+  membership or quote content outside the returned scope.
+
+## Mutations
+
+Only create or edit a message, or upload an attachment, when the user asks for
+that exact operation. Confirm the target topic, preserve the latest message
+identity/version when available, and report the server result. Never delete or
+rewrite discussion history by guessing a topic from its display name.
@@ -0,0 +1,5 @@
+interface:
+  display_name: "SHD discussions"
+  short_description: "Search and manage discussion threads"
+policy:
+  allow_implicit_invocation: false
@@ -0,0 +1,14 @@
+# Discussion contract
+
+Use the narrowest tool for the request:
+
+- discovery: `shd_list_discussion_channels`,
+  `shd_list_discussion_topics`;
+- content: `shd_list_discussion_messages`, `shd_search_discussions`;
+- writes: `shd_add_discussion_message`, `shd_update_discussion_message`;
+- files: `shd_upload_discussion_attachment`.
+
+Resolve the canonical channel/topic/message identifiers before a write. Keep
+searches bounded, distinguish no results from denied scope, and retain the
+server's pagination or conflict fields. A message edit or attachment upload is
+a side effect: require explicit user intent and report the final server result.