docs: archive legacy guides and streamline copilot instructions governance
This commit is contained in:
@@ -31,7 +31,7 @@ Example payload:
|
||||
|
||||
```json
|
||||
{
|
||||
"schema_version": "tv-power-intent.v1",
|
||||
"schema_version": "1.0",
|
||||
"intent_id": "9cf26d9b-87a3-42f1-8446-e90bb6f6ce63",
|
||||
"group_id": 12,
|
||||
"desired_state": "on",
|
||||
@@ -39,7 +39,9 @@ Example payload:
|
||||
"issued_at": "2026-03-31T10:15:30Z",
|
||||
"expires_at": "2026-03-31T10:17:00Z",
|
||||
"poll_interval_sec": 30,
|
||||
"source": "scheduler"
|
||||
"active_event_ids": [148],
|
||||
"event_window_start": "2026-03-31T10:15:00Z",
|
||||
"event_window_end": "2026-03-31T11:00:00Z"
|
||||
}
|
||||
```
|
||||
|
||||
@@ -150,7 +152,7 @@ Every event includes these common fields:
|
||||
}
|
||||
```
|
||||
|
||||
**Note**: WebUntis events use the same payload structure as website events. The URL is fetched from system settings (`webuntis_url`) rather than being specified per-event. Clients treat `webuntis` and `website` event types identically—both display a website.
|
||||
**Note**: WebUntis events use the same payload structure as website events. The URL is fetched from system settings (`supplement_table_url`) rather than being specified per-event. Clients treat `webuntis` and `website` event types identically—both display a website.
|
||||
|
||||
#### Video Events
|
||||
|
||||
|
||||
Reference in New Issue
Block a user