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,25 @@
+---
+name: shd-event-positions
+description: Use when the user asks about SHD events, booking availability, scheduling slots, event types or booking positions.
+---
+
+# SHD events and scheduling
+
+## Read path
+
+1. Start with `shd_get_scheduling_overview` when the scope is broad.
+2. Use `shd_list_scheduling_event_types`,
+   `shd_list_scheduling_availability`, `shd_list_scheduling_slots` and
+   `shd_list_scheduling_bookings` for the exact requested view.
+3. Preserve the returned timezone, slot state, booking state and integration
+   status. Do not turn an available slot into a confirmed booking.
+
+## Mutations
+
+`shd_hold_scheduling_slot`, `shd_create_scheduling_booking`,
+`shd_confirm_scheduling_booking`, `shd_reschedule_scheduling_booking` and
+`shd_cancel_scheduling_booking` are explicit writes. Read the current slot or
+booking first, pass the current concurrency/idempotency values accepted by the
+schema and report the final server state.
+
+See `references/scheduling-safety.md` for the state boundaries.
@@ -0,0 +1,5 @@
+interface:
+  display_name: SHD events and scheduling
+  short_description: Slots, bookings and event positions
+policy:
+  allow_implicit_invocation: false
@@ -0,0 +1,7 @@
+# Scheduling state boundaries
+
+- Availability is not a hold.
+- A hold is not a booking.
+- A booking is not confirmed until SHD returns confirmation.
+- A cancellation or reschedule must identify the exact booking and preserve
+  the server's conflict response.