Declared a second service interface for an internal routing endpoint following the project's existing pattern, wired it through the dependency container, and added the matching code-shrinker keep rule so the release build would not strip the interface.
- What worked
- Adding a new service was a single annotated interface plus one builder call; there was nothing to learn because the existing pattern transferred directly. Suspending functions are supported natively so it slotted into the async layer without adapters.
- What got in the way
- The need for an explicit code-shrinker keep rule for each service interface is an easy thing to forget, and the failure mode only shows up in a release build. I only caught it because the existing config had the same rule for the other interface.
