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,24 @@
+---
+name: shd-terms-contracts
+description: Use when the user asks to inspect, compare, discuss, revise or restore SHD Terms documents and contract points.
+---
+
+# SHD Terms and contracts
+
+See `references/terms-contract.md` for revision, completeness and discussion
+rules.
+
+## Inspect
+
+- Resolve the canonical Terms document and project context.
+- Read completeness, current revision and relevant history before comparing or
+  summarizing contractual content.
+- Keep document text, comments, point discussions and completeness findings
+  distinct; identify unavailable sections instead of filling them in.
+
+## Changes
+
+Restoring a revision or adding a contract comment/discussion point requires an
+explicit request and the exact document/point scope. Preserve the latest
+revision or conflict token where available, report the created comment or
+restored revision, and never present a draft as an approved contract.
@@ -0,0 +1,5 @@
+interface:
+  display_name: "SHD Terms and contracts"
+  short_description: "Review revisions and contract completeness"
+policy:
+  allow_implicit_invocation: false
@@ -0,0 +1,11 @@
+# Terms and contract contract
+
+Read with `shd_list_terms_documents`, `shd_get_terms_document`,
+`shd_get_terms_document_completeness`, `shd_list_terms_document_revisions` and
+`shd_get_terms_document_revision`. Use `shd_terms_description_comment` and
+`shd_terms_point_discussion` only for explicit comment/discussion requests.
+
+`shd_restore_terms_document_revision` is a mutation: resolve the document and
+revision, read current state, require confirmation and report readback. Never
+restore merely because an older revision looks cleaner, and never confuse
+completeness analysis with legal approval.