docs: add agentic patterns overview to cookbook

[nuthalapativarun]

Issue Link (REQUIRED)

Fixes #328

Summary

Changes

Adds docs/src/content/docs/cookbook/patterns/agentic-patterns.mdx — a new cookbook page covering the four core agentic patterns for Agent Squad. Updates astro.config.mjs to surface the page in the sidebar under a new Agentic Patterns heading.

The four patterns documented:

1. Multi-Agent Routing — classifier picks the right specialist agent
2. Supervisor Pattern — lead agent coordinates a parallel team
3. Sequential Chain Pattern — ChainAgent pipelines output through stages
4. RAG Pattern — agent grounded in a retriever/knowledge base

Each pattern includes side-by-side TypeScript and Python examples and a brief "when to use" note. The page closes with a note on combining patterns.

User experience

Before: no single place explaining the architectural patterns available in Agent Squad.

After: users land on Agentic Patterns Overview from the sidebar and can immediately see code examples for their chosen pattern in their preferred language.

Checklist

• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• I have linked this PR to an existing issue (required)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[cornelcroi]

Hey @nuthalapativarun, the structure and descriptions are good but several code examples are broken and will fail if someone copies them.

The TypeScript RAG example calls AmazonKnowledgeBasesRetriever with just an options object but the actual constructor requires a BedrockAgentRuntimeClient as the first argument, also the field name is retrievalConfiguration not retrievalConfig. The Python routing example does response, _ = await orchestrator.route_request(...) but route_request returns a single AgentResponse not a tuple, so that will throw a ValueError. The Python RAG example imports AmazonKnowledgeBasesRetrieverConfig which does not exist, the correct class is AmazonKnowledgeBasesRetrieverOptions, and the options kwarg is wrong too — it should be retrievalConfiguration not retrieval_config.

Also worth fixing in the Supervisor examples for both languages — name and description passed to SupervisorAgentOptions are silently overwritten by the lead agent values, so either remove those fields from the example or add a comment explaining it.

[nuthalapativarun]

Thanks for the detailed review, @cornelcroi — all fixed in 6a63510:

• TypeScript RAG example: AmazonKnowledgeBasesRetriever now takes a BedrockAgentRuntimeClient as its first constructor argument (with the options object as the second), matching the real signature. Also renamed retrievalConfig → retrievalConfiguration.
• Python RAG example: swapped the nonexistent AmazonKnowledgeBasesRetrieverConfig import for the actual AmazonKnowledgeBasesRetrieverOptions, and renamed retrieval_config → retrievalConfiguration to match the real field name.
• Python routing example: removed the incorrect tuple unpacking — route_request returns a single AgentResponse, so it's now response = await orchestrator.route_request(...) instead of response, _ = ....
• Supervisor examples (TS + Python): added a comment above the SupervisorAgent/SupervisorAgentOptions construction in both languages noting that name/description are required by the options type but are silently overwritten by the lead agent's name/description at runtime — so readers aren't confused when the "Travel Supervisor" name never shows up.

Re-checked every changed example against the current constructor signatures and field names in python/src/agent_squad/retrievers/amazon_kb_retriever.py, typescript/src/retrievers/AmazonKBRetriever.ts, python/src/agent_squad/orchestrator.py, typescript/src/orchestrator.ts, and the Supervisor agent implementations in both languages. Ready for re-review.