gRPC C++ 1.83

Apply the C++23 prompt first. These rules cover gRPC Core/C++ 1.83. gRPC requires at least C++17; use a supported C++23 toolchain consistently across the application and its dependencies.

Build and dependency compatibility

• Keep the gRPC line within its rolling support window: only the current release and its predecessor receive bug and security fixes. Migrate when the deployed line leaves that window; wire interoperability is not a promise of continued security maintenance.
• Leave the message_size_refactoring, ph2_perf_01, and header_data_frame experiments enabled and remove any GRPC_EXPERIMENTS override that turns them off: they gate Core's bound on decompressed message size, its on-demand allocation of GOAWAY debug data, and its coalescing of small receive buffers. Carry those fixes with Core when packaging or backporting it; message-size configuration alone does not repair a transport that lacks them.
• Resolve and review the dependencies actually selected by Bazel or CMake; MODULE.bazel specifies Protobuf 35.1, but CMake package providers and dependency overrides can select other builds. Match Protobuf C++ generated code and runtime exactly using that runtime's protoc, generate gRPC stubs with the grpc_cpp_plugin from the gRPC release you link, and rebuild dependent code when changing them; wire compatibility does not imply C++ ABI compatibility.

Transport credentials and peer identity

• Use grpc::SslCredentials and grpc::SslServerCredentials, or a reviewed authenticated transport, for network RPCs. Verify the intended server name against