Create a channel per team or topic

Create a channel for one team, product, or topic:

Create a Juno channel organised around how a group actually works, not the org chart. Ask before building, ground every choice in our real content, and put nothing live until I approve.

═══ ONE ROUND OF QUESTIONS ═══
Ask me in ONE message, then wait:
1. Which group, product, or topic the channel is for.
2. How they actually work day to day: the real jobs, workflows, or moments they need content for. If my answer is vague, ask once more; do not fall back to org-chart categories.
3. Who should see it: private to members, or open.
Before proposing anything, check the channels that already exist (list_channels) so we do not duplicate one.

═══ TOPICS AND COVERS, THEN STOP ═══
Propose exactly three topics that match their real workflow, one line of rationale each, plus a cover for each topic from ONE shared palette (generate_channel_topic_cover) so they read as a set. Wait for my approval or edits. Create only what I approve.

═══ FILL THE TOPICS ═══
For each topic, in one combined plan:
- Reuse: search our library (search_lms_content) for content this group already has, open the candidates and confirm what is inside, and propose which existing units go in which topic.
- Create: where a topic has no good coverage, propose a new course for it and ask me for the material it should be built from. Each new course runs its own outline and publish gates; never invent content to fill a topic.
- External, only if I say yes: if our account can search outside catalogues (search_external_content), propose matches per topic and file only the items I approve one by one. They are links to other platforms and cannot be edited in Juno. If that option is not enabled on our account, say so and move on.
Wait for my approval, then file and build only what I approved.

═══ PREVIEW, GO LIVE, REPORT ═══
Show me a preview of the channel page (preview_channel_page). Say plainly that publishing (set_live_channel_version) takes it live for every member at once and that the previous version is kept as a restorable backup. Go live only on my yes. Then report the counts per topic: existing units filed, new courses built, external items added, and anything left unfiled for me to decide.

═══ KEEP IT FRESH (OPTIONAL) ═══
Ask whether I want a recurring refresh. If yes, on each pass: audit every topic against who and what the channel is for, report what is still relevant, what looks stale or off-topic, and a suggested fix for each. Propose only; remove or rewrite nothing without my approval each cycle. If this assistant can schedule tasks, offer to schedule the pass; if not, say so plainly and tell me to rerun this line.

Rules throughout: ask before you build; topics follow how the group works; reuse before you create; one palette for all covers; preview before live; nothing goes live, changes, or is removed without my yes; talk in product terms, not tool names.