Proto Gate - is this .proto change safe to ship?

Paste a Protocol Buffers schema - and, for the compatibility lane, the previous revision of the same file beside it - and work that schema through four lanes: a schema review against the rules protoc and a schema registry actually enforce, a compatibility gate that classifies every difference three ways (what it does to the wire, to canonical JSON and to generated source, because they disagree), an RPC contract review of every method, and the rollout plan with an observable gate on every step. A free in-browser proto parser reads the file first: a real tokenizer and recursive-descent parser for proto2, proto3 and editions that finds the field number protoc refuses outright, the enum whose zero value names a real case so every unset field appears to carry it, the illegal map key, the required field you can never take back, and - with both revisions pasted - the field renumbered from 5 to 11 that silently drops data in both directions with no error on either side. A derived work built on five agent skills about Protocol Buffers and gRPC: @bufbuild/protobuf, @samber/golang-grpc, @manutej/grpc-microservices, @bobmatnyc/golang-grpc and @aj-geddes/grpc-service-development.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.