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,22 @@
+---
+name: shd-status-page
+description: Use when the user asks to inspect SHD status-page monitors, history, groups or incidents, or to change public status monitoring.
+---
+
+# SHD status page
+
+See `references/status-page-safety.md` for monitor and incident boundaries.
+
+## Read
+
+- Resolve the status-page scope and monitor IDs before reporting health.
+- Read current monitors and history; distinguish current state from historical
+  observations and from an incident declaration.
+- Report unavailable, stale or unauthorized monitors explicitly.
+
+## Mutations
+
+Publishing an incident, creating/updating/deleting a group or monitor changes
+an externally visible monitoring surface. Require an explicit request, exact
+scope and current readback. Do not publish an incident to test the integration
+and do not infer an outage from one missing response.
@@ -0,0 +1,5 @@
+interface:
+  display_name: "SHD status page"
+  short_description: "Inspect monitors and publish incidents safely"
+policy:
+  allow_implicit_invocation: false
@@ -0,0 +1,14 @@
+# Status-page safety contract
+
+Read with `shd_get_status_page_monitors` and
+`shd_get_status_page_monitor_history`. Mutations are
+`shd_publish_status_page_incident`, `shd_create_status_page_group`,
+`shd_update_status_page_group`, `shd_delete_status_page_group`,
+`shd_create_status_page_monitor`, `shd_update_status_page_monitor` and
+`shd_delete_status_page_monitor`.
+
+Before a mutation, resolve the canonical monitor/group IDs, read the latest
+state and show the public scope, message, duration or target being changed.
+Report server validation and final status. Deletion and incident publication
+are consequential actions and must never be inferred from a question asking for
+diagnosis.