Friday Slack digest: new and leaving on streaming

Build me an agent workflow that posts a weekly "weekend watch list" digest to Slack every Friday at 8am in my local time zone. Trigger is a cron schedule.

Configurable inputs (expose these so I can change them without editing the workflow):

- country: ISO country code, default "us".

- services: list of streaming service IDs the household actually pays for, default [netflix, prime, disney, max, apple, hulu].

- channel: the Slack channel ID (or name) to post in, default #watercooler.

- highlight_count: integer 5 to 7, default 6.

What the agent should do on each run:

1. Use the Streaming Availability "Get Changes" operation twice against the configured country and services: once with change_type set to new (titles added in the past 7 days) and once with change_type set to expiring or leaving within the next 30 days. Page through results if there are more than one page.

2. Reason over the combined results and pick highlight_count titles total, split roughly evenly between "new this week" and "last chance before they leave." Mix genres so the list does not feel one-note, prefer higher-rated titles (the API returns ratings on a 0 to 100 scale), and give extra weight to titles that are about to expire in the next few days.

3. For each pick, capture the title, the streaming service it lives on, a 1 to 2 sentence blurb (use the API's overview field, trim or rewrite for brevity), the rating, and the deep link to watch on that service.

4. Send one Slack message using the Slack Bot "Send a Message" operation to the configured channel. Format it with Slack mrkdwn (bold with single asterisks, links as <url|text>). Use two clear sections:

*:popcorn: New this week*

- *Title* on Service. Blurb. Rating: 87/100. <link|Watch>

*:hourglass_flowing_sand: Last chance before they leave*

- *Title* on Service (leaves Jun 30). Blurb. Rating: 82/100. <link|Watch>

Open the message with a friendly one-liner like "Weekend watch list for the week of <date>." Keep the whole thing under ~3000 characters so Slack renders it cleanly.

5. If a run yields no usable results (rare, but possible if the API returns empty for the configured services), skip the post entirely rather than sending an empty message.

Notes for the build: Streaming Availability is read-only via RapidAPI and only Apple TV, Disney+, Max, Netflix, Prime Video, and Mubi return populated upcoming-change buckets, so if Hulu or other services are in the list they should still be queried for new arrivals but treated as empty for the leaving section. Use the Slack Bot integration (xoxb token), not the user-token Slack integration.