Lab: Finish, check and hand over the assistant

Module 11 · Lab · About 75 minutes · Needs: the labs of Modules 1 to 10 (this lab rebuilds what is missing); a free Groq or Gemini key only for the last command of Step 8

What you are building

Friday 9 October 2026. Nare, Priya and Tomas review the assistant: six questions (one the notes cannot answer), the planted visitor-policy note with its made-up freezer alarm code, both transports with tokens, and a record of what broke. This lab turns each check into code that passes or fails, then hands the repository over with a README a stranger can follow.

A real team made the same decisions in public. In June 2025 Sentry's Cody De Arkland wrote up their MCP server: hosted over Streamable HTTP because "It's lower friction" than a local install, OAuth because "Making people create API tokens and pass them around is… not great", 16 tool calls including prompts, and instrumentation from their own SDK. He closed with the honest part: "MCP certainly has its share of sharp edges and challenges associated with it", naming which tools get called, chained calls and authentication (Sentry, 10 June 2025). (Module 9 Lesson 3 opened with Sentry's later monitoring post.) Your WHAT_BROKE.md is the same honesty, with numbers.