Design a channel page

Design a channel page in our brand:

Redesign one Juno channel's page, look and feel only: layout, hero, covers, type, colour. Do not add, remove, or re-file any content, and publish nothing until I approve.

═══ ONE ROUND OF QUESTIONS ═══
Ask me in ONE message, then wait:
1. Which channel; offer the ones that exist (list_channels) so we pick from real names.
2. The feeling the page should give: calm library, launch hub, busy newsroom. If my answer is vague, offer two or three concrete directions.
3. How strong a change: a fresh accent and hero only, or a fully designed page.

═══ READ THE BRAND AND THE PAGE ═══
Read our brand from the account (get_company_context): colours, fonts, tone. Show me exactly what you found and say plainly what is missing rather than inventing it; if the logo is not returned, ask me to paste it. Read the channel's current page and its topics (get_channel_structure) before proposing anything, and read the platform's page guide before you design (get_authoring_guide, topic page-kit); follow it over memory.

═══ DESIGN, THEN STOP ═══
Propose the page: the sections in order, the hero, where each existing topic rail sits, and a cover treatment for the topics from ONE shared palette (generate_channel_topic_cover), consistent, not three unrelated looks. Styling rules for anything custom:
- Scope every CSS rule to your own wrapper classes, and give every block you author its own class. Never style bare tags (p, span, h1-h6, div) and avoid broad descendant selectors; both reach inside Juno's own cards and widgets and break them.
- Keep the channel's existing widgets and rails; design around them, never over them. Restyle Juno's cards only through their documented CSS variables, and where a band changes background, redeclare the full card variable set so no card text or pill goes invisible on the new ground.
- Use the platform's own fonts. Never load or invent a typeface.
- The brand colour is ink, rules, and small accents, not full washes. Check text contrast on the surface it actually sits on; small or muted text gets MORE contrast, not less.
- Real assets only: never fabricate screenshots or product imagery.
Wait for my approval before writing anything.

═══ DRAFT, PREVIEW, THEN LIVE ON MY YES ═══
Save the approved design as a draft version (update_channel_layout), show me the preview (preview_channel_page), and report which parts survived and which the platform dropped. The preview strips the platform's fonts and live widgets, so judge structure in the preview and look on the published page. Nothing changes for members until the draft is set live (set_live_channel_version); the previous design stays as a restorable version, so tell me how to roll back. Set it live only on my explicit yes.

Rules throughout: look and feel only, never the channel's content or its filing; read-only until I approve, no write-shaped calls, not even ones you expect to be rejected; read the brand and the page before proposing; show what was found and what was missing; design around what a tool result surfaces instead of sending me to dig up ids; work with whatever this account has and never stall on a missing thing; talk to me in product terms, never tool names or call order; scoped styles, never bare tags; preview before live; nothing goes live without my yes.