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,23 @@
+---
+name: shd-realtime-activity
+description: Use when the user asks to inspect SHD realtime events, start or terminate a realtime session, or review operational activity and audit history.
+---
+
+# SHD realtime and activity
+
+See `references/realtime-contract.md` for session lifecycle and event handling.
+
+## Read and observe
+
+- Resolve the authorized project/module scope before reading events or audit
+  history.
+- Use bounded event reads and preserve event IDs, cursors and timestamps.
+- Distinguish historical audit records from a live realtime session; do not
+  claim that an event stream is complete when it was truncated or disconnected.
+
+## Session lifecycle
+
+Starting or terminating a realtime session is a stateful operation. Require an
+explicit request, retain the returned session ID and scope, avoid duplicate
+starts on retry, and terminate only the requested session. Report connection
+or terminal state rather than fabricating an event.
@@ -0,0 +1,5 @@
+interface:
+  display_name: "SHD realtime and activity"
+  short_description: "Inspect events and manage live sessions"
+policy:
+  allow_implicit_invocation: false
@@ -0,0 +1,11 @@
+# Realtime and activity contract
+
+Use `shd_start_realtime_session`, `shd_get_realtime_events` and
+`shd_terminate_realtime_session` for the session lifecycle. Use the relevant
+read-only audit/activity tool for historical records, such as
+`shd_get_audit_history`, when the request is about what already happened.
+
+Keep session IDs, scopes, cursors and last-seen timestamps separate. A retry
+must not create a second session unless the server explicitly supports an
+idempotency key. Termination requires the exact returned session ID and should
+be confirmed by terminal readback.