Build an interactive, self-serve learning console that teaches someone the Tines Tunnel and Command-over-HTTP — aimed at a person who has never deployed a container and needs to get one running, operate it, and diagnose it when it breaks. It should feel like an app you poke at, not a document you read. Source all of the factual content from Tines' own documentation on Tunnel and Command-over-HTTP (the setup, Docker/Compose, health check and metrics, and troubleshooting/common-errors pages), linking out to third-party docs only where Tines does — Cloudflare for the outbound port and IP ranges, Docker for restart policies. Don't invent environment variables, commands, URL paths, or behaviour. Trigger it with a single HTTP route serving a web page, reachable only by members of the space. No cron, no email, no upstream steps. Structure it as two steps: A UI step rendering the whole console: a left rail of panels with a Q&A desk docked alongside on wide screens and a slide-in drawer on narrow ones. Panels should cover, at minimum — an animated trace of where a request actually travels (Tines → Cloudflare → the container in the private network → the internal system); a deployment generator whose toggles (restart policy, health check, metrics port, secrets handling, high availability, the Command-over-HTTP container) rewrite a docker-compose.yml live, alongside a tickable setup checklist; a "is it running?" wizard that walks ordered self-checks on the user's own host and stops at the first failure with a verdict and fix; a direct answer to whether the container needs restarting daily (it doesn't — distinguish a restart policy from a restart schedule); a health-status explorer plus what to ask a firewall team; a builder that composes a Command-over-HTTP call and shows the resulting action config and payload; and a troubleshooter where pasting a real error message from an action's event log matches it against the documented errors and turns it into ordered checks with commands. Give every panel a button that hands a relevant question to the desk. Commit to a distinctive aesthetic and make it genuinely polished — copy buttons on every command, staged reveals, honest empty states. A Q&A endpoint the page calls from the browser, also space-only. It should answer questions using Claude — or whichever model provider you prefer — grounded strictly in a distilled copy of the Tines docs kept in its own file, keeping a few turns of conversation for follow-ups, rendering markdown answers, and saying plainly when something isn't covered rather than guessing. Route the model call through a connector so no key lives in code. Optionally, if a tenant-level admin API key is available, add a live status widget that reads tunnel health from the Tines admin API — but design the console to be fully useful without it, and don't leave a half-wired step behind if that credential doesn't exist. Keep the doc text in one place per step so it's cheap to refresh when Tines updates a page. Tools used: 3B, React, Tailwind, Anthropic, Cloudflare, Docker