managedcode-communication

# ManagedCode.Communication ## Trigger On - integrating `ManagedCode.Communication` into services or APIs - replacing exception-driven result handling with explicit results - reviewing service boundaries that return success or failure payloads - documenting result-pattern usage across ASP.NET Core or application services - mapping application errors to RFC 7807 problem details, Minimal API results, SignalR filters, or Orleans call filters ## Install Use the package that matches the boundary. Current upstream release reviewed: `v10.2.2`. ```bash dotnet add package ManagedCode.Communication dotnet add package ManagedCode.Communication.AspNetCore dotnet add package ManagedCode.Communication.Extensions dotnet add package ManagedCode.Communication.Orleans ``` For pinned project files: ```xml <PackageReference Include="ManagedCode.Communication" Version="10.2.2" /> <PackageReference Include="ManagedCode.Communication.AspNetCore" Version="10.2.2" /> <PackageReference Include="ManagedCode.Communication.Extensions" Version="10.2.2" /> <PackageReference Include="ManagedCode.Communication.Orleans" Version="10.2.2" /> ``` ## Workflow 1. Confirm the boundary where the library belongs: - service result contracts - application manager boundaries - API endpoints that translate results into HTTP responses 2. Keep result creation and error mapping explicit instead of mixing exceptions, nulls, and ad-hoc tuples. 3. Pattern-match result objects at the boundary that converts the...