weather_service agent binds Uvicorn on :8001 despite PORT=8000 / containerPort 8000

Summary

The a2a/weather_service agent, when deployed via the Rossoctl UI (Sandbox workload), logs:

INFO:     Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit)

...even though the Sandbox pod spec sets PORT=8000 (env) and containerPort: 8000, and the service maps to target port 8000.

Impact

Low — it works in practice (readiness/health probes pass through the AuthBridge sidecar, and the app is reachable). But it's a mismatch: the app appears to ignore the PORT env var (or offset it by one), which is confusing when debugging and could bite a setup that relies on the app honoring PORT.

Expected

The agent should bind the port given by the PORT env var (8000), matching containerPort and the service target port.

Environment

• Kind on macOS, deployed via Rossoctl UI, image weather-service:v0.0.1 built from a2a/weather_service @ main.
• Observed while running the AuthBridge weather-agent demo.

Assisted-By: Claude (Anthropic AI) noreply@anthropic.com

Start in the a2a/weather_service entry point and trace how the agent chooses its Uvicorn bind port. Run it with PORT=8000 and inspect the startup log. Done means Uvicorn reports port 8000, matching the Sandbox containerPort and service target port.