connect_rpc_rails 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 582638c47c9c929929643e53251f54ec5734f3e0cec8aa2f4fe5041db2d09e83
+  data.tar.gz: a32657f0c08c0e8f3bfd92658d3a7fbb8121a2485e3854260b0f91ea84ae7df0
+SHA512:
+  metadata.gz: 5cbd7087dc4f05689ce9957fa7aad85d4291a6f0c9e69c6af410fab38f80d364062b34e9b835b433fbf1a65fcab72fe0db4a49bd2ab2f89bd240f20f0d0151d5
+  data.tar.gz: 9840150ff947a838ca21db9bb2935899bd27a69f445fc6a8e64bc7e0ceca155d2b7c7b5fa93deb776f5e8c2f2c1b7bdb4594db6b433c0929983af0e98ef25b28

data/CHANGELOG.md

@@ -0,0 +1,7 @@
+# Changelog
+
+## 0.1.0 (2026-09-25)
+
+- Initial release: Connect unary RPCs served as ordinary `ActionController::API` actions,
+  with the routes DSL, the Connect error shape (including for exceptions that escape to
+  `config.exceptions_app`), and RBS signatures.

data/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 IVRy Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/README.md

@@ -0,0 +1,290 @@
+# connect_rpc_rails
+
+A minimal [Connect](https://connectrpc.com/docs/protocol/) **unary** RPC server for
+Rails, built on `ActionController::API`. It gives you a Connect-for-Ruby layer that is
+small enough to own outright: a service is an ordinary Rails controller, so it reuses
+`google-protobuf` and the observability you already have rather than shipping a parallel
+stack.
+
+## How it works
+
+A Connect service is an `ActionController::API` controller: each RPC in the descriptor
+is **one Rails action on that controller**, so every call flows through the normal
+controller lifecycle. Because `process_action.action_controller` fires, the entire
+Rails observability ecosystem (Datadog resource naming, Sentry transactions, lograge,
+the `Completed 200 in Xms` request log) works with no extra wiring. The RPC method
+holds the domain logic; the library wraps it with the transport.
+
+```
+caller ──HTTP──▶ Rails router ──▶ GreetController#say_hello
+                                  (ConnectRpcRails::Controller: decode ▸ callbacks ▸ encode)
+```
+
+```ruby
+# app/controllers/greet_controller.rb
+class GreetController < ActionController::API
+  include ConnectRpcRails::Controller
+  include BearerAuthentication          # a concern with a before_action
+
+  connect_service "greet.v1.GreetService"   # the name the .proto gives it
+
+  # An ordinary action — no arguments, like any other Rails action. The library decodes
+  # the request message (`connect_request`, read the way you read `params`) and encodes
+  # whatever message you return. `principal` was set by the before_action; authZ lives
+  # here.
+  def say_hello
+    Greet::V1::SayHelloResponse.new(greeting: "Hello, #{connect_request.name}!")
+  end
+end
+```
+
+```ruby
+# config/routes.rb — 1 RPC = 1 route.
+Rails.application.routes.draw do
+  connect_service "greet.v1.GreetService" => :greet
+end
+```
+
+**The RPC runs on a per-request instance.** That is the reason there is no handler
+object to register: an object held on the controller class would be shared by every
+request in the process, so anything one call left in an instance variable would be
+readable by the next caller — the mismatch that bites when gRPC-style handlers (one
+long-lived instance) are mixed into Rails (one instance per request). Here the RPC
+method *is* an action, so Rails' per-request instance is the only lifecycle in play.
+Domain logic that shouldn't live in a controller belongs in an ordinary object the
+action calls, constructed inside the action like anywhere else in Rails.
+
+**A service can be one controller or a controller per RPC.** A whole service behind one
+class is the default. When its methods have little in common — different authorization,
+different validation — give each its own controller with a block, and each RPC's callbacks
+are its own rather than the service's with `only:`:
+
+```ruby
+# config/routes.rb
+connect_service "greet.v1.GreetService" do
+  rpc "SayHello" => :greet_say_hello
+  rpc "SayGoodbye" => :greet_say_goodbye
+end
+```
+
+Every mapped name has to be one the descriptor declares, so a typo or a rename fails at boot
+instead of drawing a route nothing reaches. The mapping does not have to cover the service:
+an RPC left out is still routed — to the first mapped controller, which serves the service
+but not that method, so it is answered `unimplemented` exactly as a declared RPC nobody
+implements always is. The controllers declare the service once on a shared base class —
+`connect_service` is inherited — and the service-prefix catch-all is drawn at the first of
+them, since answering it is a 404 and nothing else.
+
+**Routes come from the descriptor, per service.** The routes file names the service the
+way the `.proto` does and points it at a controller as a string, exactly like any other
+Rails route — so drawing the routes doesn't load the controller class, and both ends of the
+mapping grep straight to the protobuf definition. Every method the descriptor declares
+becomes one route to the action implementing it; the method list lives in the `.proto` and
+nowhere else. What the controller actually serves is then its own business: a declared RPC
+with no action is answered Connect `unimplemented` (HTTP 501, not a 404, as the protocol
+wants) through Rails' own `action_missing`, and the single catch-all the DSL draws over the
+service prefix makes a method the descriptor never declared a plain 404.
+
+Under eager loading — production, and CI — the DSL also resolves each routed controller as
+the routes are drawn and checks that it serves the service it was wired to, so a
+mis-wired route raises at boot instead of 404-ing in production. Rails eager loads before it
+draws the routes, so that costs no autoloading; with lazy loading (development) the class is
+left untouched.
+
+**Why `ActionController::API`, not a bare Rack transport?** A bespoke Rack transport
+would mean going off the controller path and losing everything that hangs off
+`process_action.action_controller` (Datadog/Sentry/lograge/the request log), then
+rebuilding each integration by hand. `ActionController::API` ships exactly the useful
+modules (`Instrumentation`, `Logging`, `Rescue`, `AbstractController::Callbacks`,
+`StrongParameters`) and omits the browser concerns an RPC endpoint never uses (CSRF,
+cookies, flash, view rendering). It also brings the per-request instance lifecycle,
+which is what keeps request state from outliving the request.
+
+## Reading the call, and cross-cutting logic
+
+A Connect call *is* an HTTP request, so there is no per-call context object to learn:
+
+| what you want | where it is |
+|---|---|
+| the decoded request message | `connect_request` — read it the way you read `params` |
+| request metadata | `connect_metadata` (the request's headers, downcased and dasherized), or `request.headers` |
+| leading response metadata | `response.headers` |
+| trailing response metadata | `connect_trailers["x-audit"] = ["1"]` — the helper writes Connect's unary `trailer-` form |
+| the deadline | `connect_deadline` / `connect_timeout_ms`, for budgeting your own downstream calls |
+| anything you computed for this call | an instance variable, as in any controller |
+
+**Cross-cutting logic is Rails callbacks, and only that.** There is no interceptor layer:
+`before_action` for auth, `around_action` to wrap a call, `rescue_from` for exception
+mapping. The body is decoded *before* the callbacks run, so a `before_action` can already
+read `connect_request` — which is what makes callbacks a complete replacement rather than a
+partial one. Reuse across services is an `ActiveSupport::Concern` (see
+[`BearerAuthentication`](examples/greet/app/controllers/concerns/bearer_authentication.rb))
+or a shared base controller, and on top of that you get `only:` / `except:`, inheritance
+and `skip_before_action`, none of which an interceptor chain offers.
+
+Callbacks halt the Rails way: `render` a response, or raise a `ConnectRpcRails::Error` and
+let the library's `rescue_from` render the wire error.
+
+The library's own transport checks (POST-only, media type, undecodable body) run in a
+`prepend_before_action`, so a wrong-verb or unreadable request is answered as the protocol
+requires before any application callback — auth never sees a request that should be a 405.
+
+## Error handling
+
+`ConnectRpcRails::Error` maps to its Connect code + HTTP status. The controller declares
+`rescue_from ConnectRpcRails::Error` once, so it becomes the wire error body `{code,message,details}`
+in exactly one place. An exception that isn't a `ConnectRpcRails::Error` propagates to the
+host's error middleware, per the "let exceptions propagate" policy.
+
+**Exceptions Rails already classifies need no mapping.** Rails keeps that classification in
+`config.action_dispatch.rescue_responses` — the registry every railtie and gem writes into,
+where `ActiveRecord::RecordNotFound` is `:not_found` and `ActiveRecord::RecordInvalid` is
+`:unprocessable_content` — so including the module installs a Connect code for each of its
+entries, read off the nearest classified ancestor. A `RecordNotFound` out of an RPC is a
+Connect `not_found` without the app restating it.
+
+Mapping the *rest* — your own domain exceptions — is `map_connect_errors`, which applies to
+every RPC on the controller and overrides the code an entry above would have got:
+
+```ruby
+map_connect_errors MyDomain::Invalid => :invalid_argument,
+  MyDomain::QuotaReached => :resource_exhausted
+```
+
+That is `rescue_from` with the conversion filled in: each class gets its own handler, so
+nothing is blanket-rescued and anything unmapped still propagates. It exists as a macro
+because a hand-written `rescue_from` can't simply `raise` a `ConnectRpcRails::Error` —
+Rails calls one handler per exception, so the raise would escape instead of reaching the
+handler that renders the wire error.
+
+**Everything that escapes is the exceptions app's job.** An exception raised before
+dispatch — a routing error, an unreadable body, a middleware failing — never reaches a
+controller, and the host's `config.exceptions_app` would answer it in a shape a Connect
+client reads as a malformed response. `ConnectRpcRails::ExceptionsApp` wraps that app and
+answers the Connect protocol's error shape for a request carrying
+`connect-protocol-version`, passing everything else through untouched:
+
+```ruby
+config.exceptions_app = ConnectRpcRails::ExceptionsApp.new(MyExceptions.new(Rails.public_path))
+```
+
+The code comes from the status `rescue_responses` assigned the exception, so the app
+configures its classification in one place; the message is the status's own text, never
+the exception's. Override `#connect_error_for` in a subclass to stamp every error with a
+detail of your own (a `google.rpc.RequestInfo` holding the request id, say).
+
+Because escaping is now answered correctly, an app needs no blanket
+`rescue_from StandardError` to keep the protocol: let the exception propagate and Rails'
+request-error logging — and the error reporters subscribed to it — see it the way they see
+any other.
+
+## Conformance
+
+The official [connectrpc/conformance](https://github.com/connectrpc/conformance) suite
+lives in [`conformance/`](conformance/) and passes **84/84** (Connect + unary) against
+the `ActionController::API` transport, with the server-under-test mounted through an
+`ActionDispatch` `RouteSet` — including error details, response headers/trailers (on
+success *and* error), `connect-timeout-ms` enforcement, and the HTTP-status mapping for
+malformed requests (404 unknown method, 405 wrong verb, 415 unsupported media type,
+`unimplemented` for an unimplemented method and for unsupported compression). Streaming, gRPC/gRPC-Web, compression, and
+TLS remain out of scope. This is the real interop check that hand-written specs can't give.
+
+## Design highlights
+
+- **Reflection-based dispatch, no codegen.** A `protoc`/`buf`-generated service lands in the descriptor pool as a `ServiceDescriptor` whose `MethodDescriptor`s expose input/output message classes. `connect_service` takes the service's full name, looks it up in the pool, and derives the action names and message types purely off that — no per-service generated stubs. (`examples/greet/lib/greet_pb.rb` builds the descriptor in pure Ruby so the example runs with no protoc toolchain.)
+- **Rails instrumentation for free.** `process_action.action_controller` fires for every RPC (including errors), carrying `controller`/`action`/`status` plus a `connect_method` payload key (`pkg.Service/Method`) for clean trace/log resource naming.
+- **No object outlives the request.** The RPC is a controller action, so there is no handler singleton on the class to accumulate state between callers — the failure mode of putting gRPC-style handlers behind Rails.
+- **Nothing to learn beyond Rails.** An RPC is an action, cross-cutting logic is a callback, exception mapping is `rescue_from`, metadata is headers. The only Connect-specific thing in a controller is `connect_request`.
+- **authN vs authZ split.** `BearerAuthentication` (a concern standing in for a real bearer-token verifier) authenticates the `Bearer` token in a `before_action` and exposes `principal`; the RPC method authorizes against it.
+- **Connect wire compliance for unary:** `POST /pkg.Service/Method`, `application/json` + `application/proto`, error body `{code,message,details}` with the spec's code→HTTP-status table.
+
+## Layout
+
+```
+lib/connect_rpc_rails/
+  controller.rb           # the ActionController::API transport (mix-in)
+  routing.rb              # routes DSL: a route per declared RPC + the unknown-method catch-all
+  railtie.rb              # installs the routes DSL / Connect's content-type at Rails boot
+  service_registration.rb # descriptor -> RPC table (reflection)
+  codec.rb                # JSON / proto, via google-protobuf
+  errors.rb               # Connect codes -> HTTP status, wire error body
+  exceptions_app.rb       # config.exceptions_app wrapper: Connect error shape for what escapes
+examples/greet/           # the example as a real, bootable Rails app (own Gemfile + config.ru)
+  app/controllers/greet_controller.rb    # connect_service + the RPC action
+  app/controllers/concerns/bearer_authentication.rb  # authN as a before_action + stub verifier
+  config/routes.rb                       # connect_service "greet.v1.GreetService" => :greet
+  config/application.rb                  # api_only Rails app boot (Action Controller + Active Record)
+  proto/greet/v1/greet.proto             # the service contract
+  lib/greet_pb.rb                        # hand-built stand-in for `buf generate` output
+spec/                     # RSpec: controller, routing, auth, error mapping, instance lifecycle
+```
+
+## Run
+
+Ruby is pinned in `.mise.toml`, so [mise](https://mise.jdx.dev) users get the right
+interpreter automatically; otherwise use Ruby 3.4.
+
+```sh
+rspec             # specs (controller, routing, auth, error mapping, deadline)
+hk check --all    # rubocop, steep, actionlint, zizmor (tools pinned in .mise.toml)
+rake rbs          # regenerate + validate sig/generated from inline annotations
+rake steep        # regenerate, then type check lib with Steep
+rake conformance  # the Connect conformance suite (needs Go and buf on PATH)
+```
+
+`hk install` wires the same checks into a pre-commit hook. CI runs exactly these.
+
+### The example service
+
+`examples/greet` is a bootable Rails app with its own bundle (the gem itself depends only
+on actionpack, so full Rails lives in the example's `Gemfile`, not the gem's):
+
+```sh
+cd examples/greet
+bundle install
+bundle exec puma -b tcp://127.0.0.1:9711 config.ru
+
+curl -X POST -H 'Content-Type: application/json' \
+  -H 'Authorization: Bearer valid-token' \
+  -d '{"name":"Ada","preferredLanguage":"ja"}' \
+  http://127.0.0.1:9711/greet.v1.GreetService/SayHello
+# => {"greeting":"こんにちは, Ada!"}
+```
+
+Drop the token for `401 unauthenticated`, send `{}` for `400 invalid_argument`, use `GET`
+for `405`, and ask for a method the service doesn't declare for a `404`.
+
+## Types
+
+The library carries [rbs-inline](https://github.com/soutaro/rbs-inline) annotations
+(`# rbs_inline: enabled`, `#:` method signatures). `rake rbs` transpiles them into
+`sig/generated/**/*.rbs` and runs `rbs validate`. Protobuf messages are typed
+`untyped` — in a typical project their `.rbs` comes from buf's `rbs` plugin.
+
+`rake steep` goes further and checks `lib` against those signatures. Dependency
+signatures come from [gem_rbs_collection](https://github.com/ruby/gem_rbs_collection);
+run `rbs collection install` once to populate `.gem_rbs_collection` from
+`rbs_collection.lock.yaml`. Note the collection's `actionpack` and `google-protobuf`
+signatures lag the versions this gem builds against, and much of that surface is
+`untyped` there, so Steep checks this library's own logic rather than its use of Rails.
+
+`ConnectRpcRails::Controller` is a mix-in, so `sig/manual/controller_self.rbs` declares
+what it is mixed into (`ActionController::API`) plus the class-level accessors
+`extend ClassMethods` installs — a shape RBS cannot infer from the module body.
+
+## Releasing
+
+Tags drive the release. `.github/workflows/release.yml` fires on `v*`, reruns the full
+test workflow as a gate, then creates a draft GitHub release and publishes the gem to
+RubyGems through OIDC trusted publishing — there is no API key stored anywhere.
+
+1. Bump `ConnectRpcRails::VERSION` and retitle the `## Unreleased` heading in
+   `CHANGELOG.md` to `## <version> (<YYYY-MM-DD>)`. Merge that as its own PR.
+2. `git tag v<version> && git push origin v<version>`.
+3. Once the workflow finishes, review the draft release and publish it.
+
+## Deliberately out of scope
+
+Streaming (enveloped framing), gRPC / gRPC-Web compatibility, request compression,
+and the idempotent-GET variant. Unary over the Connect protocol is the whole surface
+here; add the rest only when a real consumer needs it.

data/lib/connect_rpc_rails/codec.rb

@@ -0,0 +1,60 @@
+# frozen_string_literal: true
+# rbs_inline: enabled
+
+# Copyright 2026 IVRy Inc.
+# SPDX-License-Identifier: Apache-2.0
+
+module ConnectRpcRails
+  # Encodes/decodes bare unary message bodies. Both codecs delegate to
+  # google-protobuf, so serialization is not something this library implements.
+  module Codec
+    # @rbs!
+    #   interface _Codec
+    #     def decode: (untyped message_class, String bytes) -> untyped
+    #     def encode: (untyped message) -> String
+    #     def content_type: () -> String
+    #   end
+
+    #: (String?) -> _Codec?
+    def self.for_content_type(content_type)
+      case content_type&.split(';')&.first&.strip
+      when Json::CONTENT_TYPE then Json
+      when Proto::CONTENT_TYPE, 'application/protobuf' then Proto
+      end
+    end
+
+    module Json
+      CONTENT_TYPE = 'application/json' #: String
+
+      #: (untyped, String) -> untyped
+      def self.decode(message_class, bytes)
+        message_class.decode_json(bytes, {ignore_unknown_fields: true})
+      end
+
+      #: (untyped) -> String
+      def self.encode(message)
+        message.class.encode_json(message)
+      end
+
+      #: () -> String
+      def self.content_type = CONTENT_TYPE
+    end
+
+    module Proto
+      CONTENT_TYPE = 'application/proto' #: String
+
+      #: (untyped, String) -> untyped
+      def self.decode(message_class, bytes)
+        message_class.decode(bytes)
+      end
+
+      #: (untyped) -> String
+      def self.encode(message)
+        message.class.encode(message)
+      end
+
+      #: () -> String
+      def self.content_type = CONTENT_TYPE
+    end
+  end
+end