chore: keep widget sources only

2026-09-17 23:29:09 +03:00
commit e0404617d2
125 changed files with 8935 additions and 0 deletions
@@ -0,0 +1,29 @@
+---
+name: shd-documents
+description: Use when the user asks to inspect, generate, send, publish, revise or audit SHD documents, templates, comments or public links.
+---
+
+# SHD documents
+
+See `references/document-safety.md` before handling publication, PDF or
+contract-related document actions.
+
+## Read and prepare
+
+- Resolve the project and document identifiers before reading content.
+- Read the document, relevant template/configuration, revisions and comments
+  needed for the requested result; do not treat a filename as authorization.
+- Keep document status, approval state, external links and public links
+  separate in the report.
+- Use the document's returned revision or version when a write accepts one.
+- In a UI-capable MCP host, pass normalized list records to
+  `shd_render_documents_widget`; keep the structured document list as the
+  fallback and use `shd_get_contract` only for an explicitly selected record.
+
+## Mutations and publication
+
+Generating a PDF, sending a document, saving a contract, publishing a public
+link or changing document state requires an explicit request. Explain the
+target and audience before publication, preserve the server's ACL and expiry
+rules, and perform readback when the tool provides it. Never expose private
+links, bearer values or document content outside the authorized result.
@@ -0,0 +1,5 @@
+interface:
+  display_name: "SHD documents"
+  short_description: "Inspect and safely manage documents"
+policy:
+  allow_implicit_invocation: false
@@ -0,0 +1,14 @@
+# Document safety contract
+
+Useful read tools include `shd_list_contracts`, `shd_get_contract`,
+`shd_list_document_revisions`, `shd_list_document_templates`,
+`shd_list_document_comments`, `shd_list_document_external_links` and
+`shd_list_document_public_links`. PDF inspection uses
+`shd_download_document_pdf`; generation uses `shd_generate_document_pdf`.
+
+Treat these as separate side effects: `shd_send_document`,
+`shd_publish_document_public_link`, `shd_save_document_contract` and
+`shd_document_contract_workflow`. Before any of them, resolve the document,
+read the current state and require the exact requested action. Report recipient,
+visibility, expiry, revision and server validation when returned. A public link
+is never a harmless preview and must not be created just to test access.