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,24 @@
+---
+name: shd-gitea
+description: Use when the user asks to inspect or manage SHD-linked Gitea issues, labels, comments or issue attachments.
+---
+
+# SHD Gitea
+
+See `references/gitea-contract.md` for repository and issue safety.
+
+## Read and resolve
+
+- Resolve the canonical repository and issue identifiers returned by SHD before
+  acting.
+- Read the issue, labels and current state before creating a comment or
+  changing labels.
+- Keep Gitea state separate from SHD project/task state; do not claim that a
+  label or issue update changed the SHD record unless the server says so.
+
+## Mutations
+
+Creating an issue, commenting, changing labels or uploading an attachment
+requires an explicit request. Report repository, issue number, changed labels,
+comment/attachment result and server validation. Never put credentials or
+private attachment URLs in the response or repository.
@@ -0,0 +1,5 @@
+interface:
+  display_name: "SHD Gitea"
+  short_description: "Review and update linked Gitea issues"
+policy:
+  allow_implicit_invocation: false
@@ -0,0 +1,11 @@
+# Gitea contract
+
+Use `shd_list_gitea_issues` and `shd_list_gitea_labels` for discovery. Writes
+are `shd_create_gitea_issue`, `shd_comment_gitea_issue`,
+`shd_update_gitea_issue_labels` and `shd_upload_gitea_issue_attachment`.
+
+Resolve the repository and issue from returned server data, preserve the
+current issue state before a label update, and use an idempotency key when the
+tool schema offers one. A comment or attachment is an external side effect;
+require exact user intent and report readback. Do not assume Gitea permissions
+from SHD project permissions alone.