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
@@ -5,6 +5,9 @@ description: Use when the user asks to find, inspect, create, update, reschedule

 # SHD task workflow

+See `references/task-contract.md` for identifier resolution, conflict handling
+and mutation readback requirements.
+
 ## Read and resolve

 - Use `shd_list_task_projects` when the request concerns a task project or its
@@ -0,0 +1,5 @@
+interface:
+  display_name: SHD task workflow
+  short_description: Read and safely update tasks
+policy:
+  allow_implicit_invocation: false
@@ -0,0 +1,20 @@
+# Task workflow contract
+
+Resolve task context before acting:
+
+- use a canonical task-project identifier when the server returns one;
+- search by explicit project, task ID or bounded query rather than guessing
+  from a display name;
+- read task-project metadata before changing status, sprint, tags or custom
+  fields;
+- retain `updated_at`, version or equivalent conflict data from the latest
+  read whenever the mutation schema supports it.
+
+For a write, report the exact operation, task ID, changed fields, idempotency
+key when used, server validation, conflict result and readback state. A
+conflict or ambiguous match is a stop condition: show the current state and
+ask for a narrower target instead of overwriting it.
+
+Delete and archive operations require their server-side confirmation contract.
+Never treat a proposed task change or a natural-language suggestion as write
+authorization.