SMS SDK smoke test
An AI agent integrated a third-party SMS provider's SDK into your notification service, writing the send call and the response handling from the provider's docs it 'remembered.' The code compiles and looks idiomatic. Describe the lightweight smoke-check you'd run before trusting it in production, given that AI commonly hallucinates SDK method names and response shapes.
Implement
sdk_contract_gaps(assumed_surface: list[str], real_surface: list[str]) → list[str]Examples
in
[["method|client.messages.create|to,body,from","field|response.messageId|string","field|response.error.code|string"],["method|client.messages.create|to,body,from","field|response.sid|string","field|response.status|string"]]out["missing:field.response.error.code","missing:field.response.messageId"]in
[["method|client.messages.create|body,to"],["method|client.messages.create|to,body"]]out["shape_mismatch:method.client.messages.create"]in
[["method|client.messages.create|to,body","field|response.sid|string"],["method|client.messages.create|to,body","field|response.sid|string","method|client.messages.list|limit"]]out[]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 14 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.