Add a development-runner banner at startup

[kompfner]

Prints a bordered startup banner (on every run mode) marking pipecat.runner.run as a development tool — not a production server — and linking to the deployment docs for running bots locally and in production.

🤖 Generated with Claude Code

[codecov]

Codecov Report

❌ Patch coverage is 53.84615% with 6 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/pipecat/runner/run.py	53.84%	6 Missing ⚠️

Files with missing lines	Coverage Δ
src/pipecat/runner/run.py	38.06% <53.84%> (-2.28%)	⬇️

... and 22 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[markbackman]

My main concern is that the callout box dominates the visual space, making it harder to find the bot ready / open information. Could we try a different approach:

1. Running locally, just include a simple text description: Pipecat development runner: not for production use. or Pipecat development runner: for development purposes only?

Pipecat development runner: not for production use.

🚀 Bot ready!
   → Open: http://localhost:7860
   → Enabled transports: daily, webrtc, telephony, websocket
   → Allowed origins: all (no restriction)

2. When not running on localhost or 0.0.0.0, etc then show a warning; something like:

⚠️  This runner is reachable beyond localhost and its endpoints are
    unauthenticated. For more information, see:
    https://docs.pipecat.ai/pipecat/deployment/self-hosting

🚀 Bot ready!
   → Open: http://0.0.0.0:7860
   ...

This might balance out the two options. Importantly, this helps the dominate use case remain usable.

WDYT?

[filipi87]

+1 for Mark's suggestions above.

But I think it could still be worth keeping the warning symbol, even in this case.

⚠️ Pipecat development runner: not for production use.

🚀 Bot ready!
   → Open: http://localhost:7860
   → Enabled transports: daily, webrtc, telephony, websocket
   → Allowed origins: all (no restriction)

[kompfner]

If we're concerned that folks are inadvertently running in prod, I think it'd helpful to provide some link to learn more. I also find it helpful to make it clear what's actually running when you run your bot.py command.

But I see your point about not visually "taking over" the subsequent connection status messages.

Counter-proposal: I'm going to try to make the banner dimmer but still prominent. I feel like I've seen that precedent elsewhere, though I'm not sure exactly where. Screenshot incoming.

[kompfner]

Messed around with some different colors; I'm now choosing between the plain dim gray or the dim cyan.

[kompfner]

Cyan looks best to me. Strikes a balance between subtle and noticeable; clearly describes the running process and supplies the necessary warning without distracting from the following log lines.

[filipi87]

• 1 on using Cyan @kompfner.

This looks great. 🚀