Update to LiveReacting

{
  "description": "Schedule one pre-recorded video to go live on YouTube, Facebook, Twitch or a custom RTMP destination at a set date and time with LiveReacting, like a premiere or a webinar replay. Use when the user wants a recorded video to air live later, at a specific time.",
  "included_files": [],
  "name": "schedule-recorded-broadcast",
  "skill_md_contents": "---\nname: schedule-recorded-broadcast\ndescription: Schedule one pre-recorded video to go live on YouTube, Facebook, Twitch or a custom RTMP destination at a set date and time with LiveReacting, like a premiere or a webinar replay. Use when the user wants a recorded video to air live later, at a specific time.\n---\n\n# Schedule a recorded broadcast\n\nAir one recorded video as a live stream at a time the user chooses. The stream starts and ends\nby itself. Confirm the time with the user before scheduling anything.\n\n## 1. Confirm the time\n\n1. Get the date, the time and the user's time zone. If the time zone is unclear, ask.\n2. Convert it to an ISO 8601 time in UTC.\n3. The start must be at least 3 minutes and at most 28 days in the future. If it is not, ask\n   for another time.\n4. Repeat the time back to the user in their time zone and in UTC.\n\n## 2. Get the video ready\n\n1. Call `livereacting_list_media` with `type: \"video\"` to find the video. Follow\n   `nextOffset` before treating it as missing.\n2. If it is not in the library:\n   - Google Drive, Dropbox, or one video from the user's own YouTube channel:\n     `livereacting_import_media`.\n   - A direct link to a video file: `livereacting_import_from_url`.\n3. Poll `livereacting_get_import_status` no more than every 10 seconds. Read `usable`, not only\n   `done`. Stop and report an import error when `status` is `error`. Otherwise, when\n   `usable` is false, follow `nextStep`.\n4. Read the file with `livereacting_get_media_file`, including a file already in the\n   library. If it needs encoding, call `livereacting_encode_media` once. If it is\n   already queued or encoding, wait for that job instead.\n5. Poll `livereacting_get_encode_status` no more than every 15 seconds. After each check,\n   read the selected file again with `livereacting_get_media_file`. While `issues.errors`\n   includes `encoding_in_progress`, keep waiting. A file missing from one queue page is\n   not proof that encoding finished or succeeded.\n6. Once encoding is no longer active, require `issues.errors` to be empty. If errors\n   remain, stop and report them. Do not automatically encode the same file again.\n7. Call `livereacting_get_media_file` with `includeMetadata: true` and note `durationSec`.\n   Require a positive duration; if it is missing, stop rather than inventing a length.\n\n## 3. Build the broadcast\n\n1. Call `livereacting_list_destinations` and confirm the destination with the user. If it is\n   missing, the user must connect it once in the LiveReacting Studio.\n2. Call `livereacting_create_project` with the destination ids and a fixed duration:\n   `duration: { manual: false, planned: <durationSec rounded up, at least 30> }`. The stream then\n   ends when the video ends. Do not add extra time: the stream keeps running for the whole planned\n   duration, after the video has finished.\n3. Call `livereacting_create_scene_with_playlist` with the one file id and `loop: false`, so the\n   video plays once.\n\n## 4. Schedule it\n\n1. Call `livereacting_get_project` with `includeScheduledLives: true`. If the project already has\n   a schedule, ask whether the user wants to replace it. Do not cancel it yet.\n2. Recheck the requested start against the current UTC time. It must still be at least\n   3 minutes and at most 28 days ahead. Preparation may have taken several minutes. If it is\n   outside that range, stop and ask for another time. Never move it silently.\n3. If an existing schedule needs replacement and the user authorized it, call\n   `livereacting_cancel_schedules`. Recheck the time range again after cancellation.\n   If the time is now outside the range, stop and ask for another time before scheduling.\n4. Immediately after the time check, call `livereacting_schedule_stream` with the created\n   `projectId` and `dates: [<the UTC time>]`. If it rejects the date as too soon, ask for another\n   time instead of retrying the same date or choosing a new time yourself.\n5. After a successful response, report the confirmed start time in the user's time zone and\n   in UTC, the length, and the destination. Say that LiveReacting starts and stops it by itself,\n   so the user's computer can be off.\n\n## Good to know\n\n- Do not call `livereacting_start_stream` on a scheduled project: it returns the existing\n  schedule and starts nothing.\n- To change the time, cancel the schedule with `livereacting_cancel_schedules`, then schedule\n  again.\n- Title and description changes made later with `livereacting_update_project` also update the\n  scheduled broadcast on the platform.\n"
}