feat: add SHD widget suite

plugins/shd-mcp-plugin/README.md

@@ -33,16 +33,23 @@ modules. Skills do not grant permissions or bypass server-side ACLs.
 - linked Gitea issues, labels, comments and attachments;
 - safe bulk-change planning and validation rules.
 
-When the connected MCP host supports MCP Apps UI, the active-projects workflow
-also has an inline widget: it sorts by the nearest completion date, filters by
-name/code, shows status pills and loads one project’s read-only details. The
-same tools still return normal structured data for hosts that do not render
+When the connected MCP host supports MCP Apps UI, the 36 SHD render tools have
+inline read-only widgets: active projects, module registers and specialized
+Kanban, workload, timeline, funnel, dashboard, calendar, matrix, tree and
+Project DB views. Each widget sorts or filters normalized records, shows
+status/value fields and can load one selected record’s details where supported.
+The same tools still return normal structured data for hosts that do not render
 widgets.
 
 The active-projects widget is versioned in `widgets/active-projects/v1/` with a
 manifest, SHA256 checksum and source/provenance note. The SHD MCP backend reads
 that artifact for the `ui://shd/active-projects/v1.html` resource.
 
+The other versioned resources are stored under `widgets/` with a manifest,
+SHA256 checksum and source/provenance note for each resource. Their render
+tools are deliberately separate from the list tools so the server can keep
+data access and UI rendering auditable.
+
 ## MCP connection
 
 The package points to `https://shd.xyz.su/mcp` and requests OAuth for that MCP