Proto reorganization wire compatibility
An AI agent 'tidied up' a gRPC service's `.proto` files and the generated Go server, claiming it only 'reorganized fields and improved comments.' Your service has many downstream consumers on older clients. How do you verify the agent didn't make a wire-incompatible change, and what specific edits would be the silent killers here?
Implement
detect_proto_breaks(old_fields: list[str], new_fields: list[str]) → list[str]Examples
in
[["1|user_id|int64","2|email|string","3|created_at|int64"],["1|user_id|int64","2|email_address|string","3|created_at|int64"]]out[]in
[["1|user_id|int64","2|email|string","3|score|int32"],["1|user_id|int64","2|score|int32","3|email|string"]]out["type_changed:2","type_changed:3","renumbered:email","renumbered:score"]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 20 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.