docs: add OrcaRouter as a named external API provider in Chapter 9

[bangla24bdrang-lab]

What changed

• Add OrcaRouter as a named external API provider in Chapter 9 ("Connecting external APIs"), right after the existing DeepSeek and local Ollama examples.

Why

The WorkBuddy Bluebook is a task-driven field guide that walks readers from their first task to an AI team, and Chapter 9 is where readers connect their own LLM API when they don't have plan credits. Today it shows DeepSeek (enter just the API key) and a local Ollama model as examples. OrcaRouter is an OpenAI-compatible AI gateway built for both models and agents. Like OpenRouter, it exposes a provider/model namespace across many models - but it also combines adaptive routing, automatic failover, zero-markup inference, observability, guardrails, and agent-tool governance behind the same endpoint. Adding orcarouter as a first-class provider in this chapter means readers can use that stack directly through the same "Add model" screen, instead of treating OrcaRouter as an anonymous custom base URL.

The new paragraph follows the exact shape of the existing DeepSeek/Ollama examples (what to type in the model dialog, one-line product description), so it fits the chapter without introducing new UI steps. It also runs gateway-level, zero-trust security for AI agents on the same endpoint - screening every prompt/response and governing every tool call on a default-deny basis, with no application code changes.

Validation

• npm run docs:build - production build completed
• npm test - 23 tests passed
• Live API check against https://api.orcarouter.ai/v1/chat/completions with orcarouter/auto returned HTTP 200

Product fact updates

• Yes - provider endpoint and model IDs were verified via a live API call on 2026-08-31.

---

I'm an engineer on the OrcaRouter team. Discord: discord.gg/YEubt8enRA · X: https://x.com/OrcaRouter