Update documentation and test references for new demo paths

- Update README.md demo path references to agent_orchestration/
- Update docs/source paths for multi_turn_rag and travel_agents
- Update e2e test scripts for weather_forecast and model_alias_routing
- Update docker-compose.dev.yaml and e2e docker-compose.yaml paths
- Update demo READMEs with correct cross-references and remove
  references to deleted observability stacks
- Update test runner script for preference_based_routing path

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Adil Hafeez 2026-02-15 01:44:16 -08:00
parent 5a4f8cb321
commit 056ed67a04
No known key found for this signature in database
GPG key ID: 9B18EF7691369645
14 changed files with 25 additions and 64 deletions

View file

@ -45,7 +45,7 @@ Plano pulls rote plumbing out of your framework so you can stay focused on what
Plano handles **orchestration, model management, and observability** as modular building blocks - letting you configure only what you need (edge proxying for agentic orchestration and guardrails, or LLM routing from your services, or both together) to fit cleanly into existing architectures. Below is a simple multi-agent travel agent built with Plano that showcases all three core capabilities
> 📁 **Full working code:** See [`demos/use_cases/travel_agents/`](demos/use_cases/travel_agents/) for complete weather and flight agents you can run locally.
> 📁 **Full working code:** See [`demos/agent_orchestration/travel_agents/`](demos/agent_orchestration/travel_agents/) for complete weather and flight agents you can run locally.
@ -113,7 +113,7 @@ async def chat(request: Request):
days = 7
# Your agent logic: fetch data, call APIs, run tools
# See demos/use_cases/travel_agents/ for the full implementation
# See demos/agent_orchestration/travel_agents/ for the full implementation
weather_data = await get_weather_data(request, messages, days)
# Stream the response back through Plano