From ed8cbc582bb66adc08f12393f8dc5cbe5e64df90 Mon Sep 17 00:00:00 2001 From: Mark Kats Date: Sat, 17 Oct 2026 12:17:55 +0300 Subject: [PATCH] docs(discussions): define router fallback, post-edit confirmation, and retry guidance --- .../references/discussion-contract.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/plugins/shd-mcp-plugin/skills/shd-discussions/references/discussion-contract.md b/plugins/shd-mcp-plugin/skills/shd-discussions/references/discussion-contract.md index 471058b..a486c67 100644 --- a/plugins/shd-mcp-plugin/skills/shd-discussions/references/discussion-contract.md +++ b/plugins/shd-mcp-plugin/skills/shd-discussions/references/discussion-contract.md @@ -8,7 +8,19 @@ Use the narrowest tool for the request: - writes: `shd_add_discussion_message`, `shd_update_discussion_message`; - files: `shd_upload_discussion_attachment`. +If a required direct discussion tool is absent from the active MCP tool list, +search for it with `shd_mcp_search` before reporting it unavailable. If the +router finds the tool, invoke the discovered operation through +`shd_mcp_write`, using its returned schema and required fields (including +confirmation or idempotency fields when specified). If the router is not +available or does not find the operation, report that limitation; never +replace an edit with a new message. + 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. +After an edit, read the target message again and confirm the stored content. +If a write returns an error or times out, check the target state before retrying. +Retry only when the operation supports idempotency, reusing the same key and +payload; otherwise report the uncertain outcome and stop.