Migrate from gpt-5.5 to claude-opus-4.8

[meerakurup]

Description

Adds a new Forgebook recipe for migrating a Chat Completions workload from gpt-5.5 to claude-opus-4-8 on Microsoft Foundry.

The notebook teaches a side-by-side migration pattern: keep the existing GPT-5.5 path live, add Claude behind the same adapter contract, compare both providers with eval gates, then promote only after schema/tool parity, structured output retry rate, quality, and latency checks pass.

New content and contributor registration:

• Added meerakurup as a new author in authors.yaml, including name, title, avatar, and GitHub profile.
• Registered the new notebook in registry.yaml with slug, path, title, description, date, author, and allowed tags.
• Added notebooks/migrate-gpt-5-5-to-claude-opus-4-8.ipynb.
• Included runnable examples for:
  • OpenAI Chat Completions baseline
  • Anthropic Messages call on Foundry
  • Provider-neutral adapter
  • Tool schema translation
  • Structured output validation and retry
  • Streaming normalization
  • Promotion gates and rollout guidance

Review focus

Please focus review on:

• Product accuracy for Claude on Microsoft Foundry, especially endpoint shape, auth audience, SDK usage, Marketplace billing, and model/deployment naming.
• Whether the migration guidance is correctly positioned as side-by-side validation before user-facing rollout.
• Adapter design and whether the Conversation / Response contract is a reasonable reusable pattern.
• Eval gate thresholds and whether schema/tool parity, structured output retry rate, quality, and latency are framed correctly.
• Notebook runnability, including prerequisites, .env configuration, quota assumptions, and common error recovery.
• Registry metadata, tags, author entry, and title/description quality for the Forgebook site.

---

Checklist

Notebook contributions

Skip if this PR only touches site code.

• Recipe author is an approved Microsoft Forgebook author, or this contribution has maintainer approval
• Recipe was drafted or validated through the internal authoring workflow
• Foundry PM, engineering, or DX reviewer has checked product accuracy and positioning
• Notebook added to notebooks/ directory
• Entry added to registry.yaml with all required fields (slug, path, title, authors)
• Approved author entry exists in authors.yaml (with at least name and title)
• Tags are from the allowed list in tags.yaml
• Registry validation passes: cd scripts && npx tsx validate-registry.ts
• Notebook runs cleanly end-to-end
• Cell outputs cleared before committing
• No site-specific metadata inside the notebook
• No secrets, tenant-specific values, or private endpoints are committed
• Images stored in notebooks/media/<slug>/ with descriptive alt text
• Data files stored in notebooks/data/<slug>/ when applicable

Site changes

Skip if this PR only adds a notebook.

• Site builds without errors: cd site && npm run build
• No TypeScript errors: cd site && npx astro check