Migrate Shell libraries from local source to NuGet packages

- Replaced local ProjectReference to Ums.Shell.* with NuGet PackageReference
- Namespace transformation: Ums.Shell.* → BeyondNetCode.Shell.*
- Updated 4 csproj files (Domain, Application, Infrastructure, Presentation)
- Updated all C# files with new namespaces (97 references)
- Removed local Shell source directories (libs/shell/aop, bootstrapper, ddd, factory)
- Updated solution file to remove Shell project entries
- Updated all documentation (40+ files) to reflect NuGet package model

Packages consumed from github.com/beyondnetcode/Shell.*:
- BeyondNetCode.Shell.Ddd + Shell.Ddd.ValueObjects
- BeyondNetCode.Shell.Factory + Shell.DI
- BeyondNetCode.Shell.Aop + Shell.DispatchProxy + Shell.Aspects + Shell.Logger.Serilog
- BeyondNetCode.Shell.Bootstrapper + Shell.DI + Shell.Observability

Build: 0 errors | Tests: 1,191 passed

Author: beyondnetPeru

docs/architecture/adrs/0054-shell-library-isolation.es.md

@@ -2,7 +2,7 @@
 
 **Estado:** Aceptado
 **Fecha:** 2026-05-15
-**Enmendado:** 2026-05-24 — grafo de dependencias corregido; alcance extendido para incluir `Ums.Shell.Aop` y `Ums.Shell.Bootstrapper`
+**Enmendado:** 2026-05-24 — grafo de dependencias corregido; alcance extendido para incluir `BeyondNetCode.Shell.Aop` y `BeyondNetCode.Shell.Bootstrapper`
 **Responsable de Decisión:** Arquitectura
 **Relacionados:**
 - [ADR-0060: Estrategia de Concerns Cross-Cutting AOP](./0060-aop-cross-cutting-concern-strategy.md)
@@ -14,24 +14,24 @@
 
 UMS incluye librerías de infraestructura reutilizables bajo `src/libs/shell`. Estas librerías se originaron de fuentes externas o de referencia, pero UMS no debe exponer namespaces upstream ni convenciones de repositorio en código de aplicación.
 
-El ADR-0029 anterior describía "Primitivas DDD nativas de C# (sin librería externa)". Esa redacción ya no es precisa: la posición correcta es que UMS **posee su superficie de dependencia de dominio** a través de las shell libraries `Ums.Shell.*`. Las capas de aplicación consumen la abstracción shell de UMS, no la identidad fuente upstream.
+El ADR-0029 anterior describía "Primitivas DDD nativas de C# (sin librería externa)". Esa redacción ya no es precisa: la posición correcta es que UMS **posee su superficie de dependencia de dominio** a través de las shell libraries `BeyondNetCode.Shell.*`. Las capas de aplicación consumen la abstracción shell de UMS, no la identidad fuente upstream.
 
 A partir de 2026-05-24, la capa shell incluye cuatro grupos de librerías:
 
 | Grupo | Proyectos | Capas consumidoras |
 |---|---|---|
-| `Ums.Shell.Ddd` | `Ums.Shell.Ddd` · `Ums.Shell.Ddd.ValueObjects` | Domain (directo) |
-| `Ums.Shell.Factory` | `Ums.Shell.Factory` · `Ums.Shell.Factory.Installer` | Domain (transitivo vía Ddd) · Infrastructure (directo) |
-| `Ums.Shell.Aop` | `Ums.Shell.Aop` · `Ums.Shell.Aop.DispatchProxy` · `Ums.Shell.Aop.Aspects` · `Ums.Shell.Aop.Aspects.Logger.Serilog` · `Ums.Shell.Aop.Microsoft.Extensions.DependencyInjection.Aspects.Installer` | Application (contrato de atributos) · Infrastructure (wiring DI + adapters) |
-| `Ums.Shell.Bootstrapper` | `Ums.Shell.Bootstrapper` · `Ums.Shell.Bootstrapper.DependencyInjection` · `Ums.Shell.Bootstrapper.AutoMapper` · `Ums.Shell.Bootstrapper.Observability` | Infrastructure · Presentation (startup) |
+| `BeyondNetCode.Shell.Ddd` | `BeyondNetCode.Shell.Ddd` · `BeyondNetCode.Shell.Ddd.ValueObjects` | Domain (directo) |
+| `BeyondNetCode.Shell.Factory` | `BeyondNetCode.Shell.Factory` · `BeyondNetCode.Shell.DI` | Domain (transitivo vía Ddd) · Infrastructure (directo) |
+| `BeyondNetCode.Shell.Aop` | `BeyondNetCode.Shell.Aop` · `BeyondNetCode.Shell.DispatchProxy` · `BeyondNetCode.Shell.Aspects` · `BeyondNetCode.Shell.Logger.Serilog` · `BeyondNetCode.Shell.DI` | Application (contrato de atributos) · Infrastructure (wiring DI + adapters) |
+| `BeyondNetCode.Shell.Bootstrapper` | `BeyondNetCode.Shell.Bootstrapper` · `BeyondNetCode.Shell.DI` · `BeyondNetCode.Shell.AutoMapper` · `BeyondNetCode.Shell.Observability` | Infrastructure · Presentation (startup) |
 
 ---
 
 ## Decisión
 
 UMS adopta una estrategia de **Aislamiento de Shell Libraries** para todos los patrones compartidos de infraestructura:
 
-1. Todos los ensamblados shell usan el namespace y convención de naming `Ums.Shell.*`.
+1. Todos los ensamblados shell usan el namespace y convención de naming `BeyondNetCode.Shell.*`.
 2. Las capas de aplicación no deben referenciar namespaces upstream como `BeyondNet.*` o nombres de repositorio fuente como `csdevlib.*`.
 3. Las shell libraries deben compilar cross-platform y apuntar al baseline .NET estable actual usado por la API (`net10.0`).
 4. La dirección de dependencias es estrictamente enforce como se describe abajo.
@@ -46,31 +46,31 @@ Ums.Presentation
 Ums.Infrastructure
   ├── Ums.Application
   ├── Ums.Domain
-  ├── Ums.Shell.Aop.Microsoft.Extensions.DependencyInjection.Aspects.Installer
-  │     └── Ums.Shell.Aop.Aspects (transitivo)
-  │           └── Ums.Shell.Aop (transitivo)
-  │                 └── Ums.Shell.Aop.DispatchProxy (transitivo)
-  └── Ums.Shell.Aop.Aspects.Logger.Serilog (transitivo vía installer)
+  ├── BeyondNetCode.Shell.DI
+  │     └── BeyondNetCode.Shell.Aspects (transitivo)
+  │           └── BeyondNetCode.Shell.Aop (transitivo)
+  │                 └── BeyondNetCode.Shell.DispatchProxy (transitivo)
+  └── BeyondNetCode.Shell.Logger.Serilog (transitivo vía installer)
 
 Ums.Application
   ├── Ums.Domain
-  └── Ums.Shell.Aop.Aspects    ← contrato de atributos solo (sin DI, sin proxy runtime)
+  └── BeyondNetCode.Shell.Aspects    ← contrato de atributos solo (sin DI, sin proxy runtime)
 
 Ums.Domain
-  ├── Ums.Shell.Ddd
-  │     └── Ums.Shell.Factory (transitivo vía Ddd)
-  └── Ums.Shell.Ddd.ValueObjects
-        └── Ums.Shell.Ddd (transitivo)
+  ├── BeyondNetCode.Shell.Ddd
+  │     └── BeyondNetCode.Shell.Factory (transitivo vía Ddd)
+  └── BeyondNetCode.Shell.Ddd.ValueObjects
+        └── BeyondNetCode.Shell.Ddd (transitivo)
 ```
 
-> **Corrección del ADR original (2026-05-15):** `Ums.Domain.csproj` previamente listaba una `<ProjectReference>` directa a `Ums.Shell.Factory`. Esto era una referencia redundante — `Ums.Shell.Ddd` ya depende de `Ums.Shell.Factory`, haciéndola disponible transitivamente. La referencia directa fue removida el 2026-05-24. El código de Domain debe acceder a abstracciones de factory solo a través de la capa shell DDD, no importando directamente el namespace de Factory.
+> **Corrección del ADR original (2026-05-15):** `Ums.Domain.csproj` previamente listaba una `<ProjectReference>` directa a `BeyondNetCode.Shell.Factory`. Esto era una referencia redundante — `BeyondNetCode.Shell.Ddd` ya depende de `BeyondNetCode.Shell.Factory`, haciéndola disponible transitivamente. La referencia directa fue removida el 2026-05-24. El código de Domain debe acceder a abstracciones de factory solo a través de la capa shell DDD, no importando directamente el namespace de Factory.
 
 ### Reglas por capa
 
 | Capa | Puede referenciar | NO puede referenciar |
 |---|---|---|
-| `Ums.Domain` | `Ums.Shell.Ddd`, `Ums.Shell.Ddd.ValueObjects` | Cualquier `Ums.Shell.Aop.*`, `Ums.Shell.Factory` (directo), `Ums.Shell.Bootstrapper.*` |
-| `Ums.Application` | `Ums.Domain`, `Ums.Shell.Aop.Aspects` (contrato de atributos) | `Ums.Shell.Aop.DispatchProxy`, `Ums.Shell.Aop.*.Installer`, `Ums.Shell.Factory`, `Ums.Shell.Bootstrapper.*` |
+| `Ums.Domain` | `BeyondNetCode.Shell.Ddd`, `BeyondNetCode.Shell.Ddd.ValueObjects` | Cualquier `BeyondNetCode.Shell.Aop.*`, `BeyondNetCode.Shell.Factory` (directo), `BeyondNetCode.Shell.Bootstrapper.*` |
+| `Ums.Application` | `Ums.Domain`, `BeyondNetCode.Shell.Aspects` (contrato de atributos) | `BeyondNetCode.Shell.DispatchProxy`, `BeyondNetCode.Shell.Aop.*.Installer`, `BeyondNetCode.Shell.Factory`, `BeyondNetCode.Shell.Bootstrapper.*` |
 | `Ums.Infrastructure` | Todo lo anterior + AOP installer + Bootstrapper | — |
 | `Ums.Presentation` | Todas las capas + Bootstrapper para startup | — |
 
@@ -82,15 +82,15 @@ Ums.Domain
 
 - UMS tiene una superficie de dependencia interna estable para patrones tácticos de DDD, Factory, AOP, y Bootstrapper.
 - El código de Domain es puro de todas las preocupaciones de infraestructura — sin imports de AOP, DI, o logging.
-- `Ums.Application` referencia solo el **contrato de atributo** de AOP (`Ums.Shell.Aop.Aspects`) — los handlers declaran intención cross-cutting vía atributos sin acoplamiento a la infraestructura de proxy.
+- `Ums.Application` referencia solo el **contrato de atributo** de AOP (`BeyondNetCode.Shell.Aspects`) — los handlers declaran intención cross-cutting vía atributos sin acoplamiento a la infraestructura de proxy.
 - Cambios de fuente upstream pueden ser absorbidos dentro de `src/libs/shell` sin tocar las capas de aplicación.
 - El patrón `IMelLogger` (interfaz marker en Application, adapter concreto en Infrastructure) demuestra cómo aplicar el mismo principio de aislamiento a adapters cross-cutting.
 
 ### Trade-offs
 
 - La capa shell es una dependencia arquitectónica real y debe ser versionada y revisada correspondientemente.
 - Alertas de seguridad y warnings de paquetes de dependencias shell (ej., CVE de `OpenTelemetry.Api` en Bootstrapper) afectan la salud del build de UMS.
-- `Ums.Shell.Ddd` depende de `Ums.Shell.Factory` — este acoplamiento es intencional (la construcción DDD puede usar abstracciones de factory internamente) pero significa que agregar una dependencia de Factory a Domain es suficiente para arrastrar Factory a todas partes donde Domain es referenciado.
+- `BeyondNetCode.Shell.Ddd` depende de `BeyondNetCode.Shell.Factory` — este acoplamiento es intencional (la construcción DDD puede usar abstracciones de factory internamente) pero significa que agregar una dependencia de Factory a Domain es suficiente para arrastrar Factory a todas partes donde Domain es referenciado.
 
 ---
 
@@ -103,15 +103,15 @@ Las siguientes verificaciones son obligatorias después de cualquier cambio en l
 dotnet build src/apps/ums.api/Ums.sln
 
 # 2. Ejecutar todos los test suites de shell libraries
-dotnet test src/libs/shell/aop/src/Ums.Shell.Aop.Tests/Ums.Shell.Aop.Tests.csproj --verbosity minimal
-dotnet test src/libs/shell/factory/src/Ums.Shell.Factory.Test/Ums.Shell.Factory.Test.csproj --verbosity minimal
+dotnet test src/libs/shell/aop/src/BeyondNetCode.Shell.Aop.Tests/BeyondNetCode.Shell.Aop.Tests.csproj --verbosity minimal
+dotnet test src/libs/shell/factory/src/BeyondNetCode.Shell.Factory.Test/BeyondNetCode.Shell.Factory.Test.csproj --verbosity minimal
 
 # 3. Verificar pureza del Domain (sin refs AOP en Domain)
-grep -r "Ums.Shell.Aop" src/apps/ums.api/Ums.Domain/ --include="*.csproj"
+grep -r "BeyondNetCode.Shell.Aop" src/apps/ums.api/Ums.Domain/ --include="*.csproj"
 # Esperado: sin output
 
 # 4. Verificar que no hay ref directa a Factory en Domain (debe ser solo transitiva)
-grep "Ums.Shell.Factory" src/apps/ums.api/Ums.Domain/Ums.Domain.csproj
+grep "BeyondNetCode.Shell.Factory" src/apps/ums.api/Ums.Domain/Ums.Domain.csproj
 # Esperado: sin output
 ```
 

docs/architecture/adrs/0054-shell-library-isolation.md

@@ -2,7 +2,7 @@
 
 **Status:** Accepted  
 **Date:** 2026-05-15  
-**Amended:** 2026-05-24 — dependency graph corrected; scope extended to include `Ums.Shell.Aop` and `Ums.Shell.Bootstrapper`  
+**Amended:** 2026-05-24 — dependency graph corrected; scope extended to include `BeyondNetCode.Shell.Aop` and `BeyondNetCode.Shell.Bootstrapper`  
 **Decision Owner:** Architecture  
 **Related:**
 - [ADR-0060: AOP Cross-Cutting Concern Strategy](./0060-aop-cross-cutting-concern-strategy.md)
@@ -14,24 +14,24 @@
 
 UMS includes reusable infrastructure libraries under `src/libs/shell`. These libraries originated from external or reference sources, but UMS must not expose upstream namespaces or repository conventions in application code.
 
-The previous ADR-0029 described "C# Native DDD Primitives (no external library)". That wording is no longer precise: the correct position is that UMS **owns its domain dependency surface** through `Ums.Shell.*` shell libraries. Application layers consume the UMS shell abstraction, not the upstream source identity.
+The previous ADR-0029 described "C# Native DDD Primitives (no external library)". That wording is no longer precise: the correct position is that UMS **owns its domain dependency surface** through `BeyondNetCode.Shell.*` shell libraries. Application layers consume the UMS shell abstraction, not the upstream source identity.
 
 As of 2026-05-24, the shell layer includes four library groups:
 
 | Group | Projects | Consumer layers |
 |---|---|---|
-| `Ums.Shell.Ddd` | `Ums.Shell.Ddd` · `Ums.Shell.Ddd.ValueObjects` | Domain (direct) |
-| `Ums.Shell.Factory` | `Ums.Shell.Factory` · `Ums.Shell.Factory.Installer` | Domain (transitive via Ddd) · Infrastructure (direct) |
-| `Ums.Shell.Aop` | `Ums.Shell.Aop` · `Ums.Shell.Aop.DispatchProxy` · `Ums.Shell.Aop.Aspects` · `Ums.Shell.Aop.Aspects.Logger.Serilog` · `Ums.Shell.Aop.Microsoft.Extensions.DependencyInjection.Aspects.Installer` | Application (attribute contract) · Infrastructure (DI wiring + adapters) |
-| `Ums.Shell.Bootstrapper` | `Ums.Shell.Bootstrapper` · `Ums.Shell.Bootstrapper.DependencyInjection` · `Ums.Shell.Bootstrapper.AutoMapper` · `Ums.Shell.Bootstrapper.Observability` | Infrastructure · Presentation (startup) |
+| `BeyondNetCode.Shell.Ddd` | `BeyondNetCode.Shell.Ddd` · `BeyondNetCode.Shell.Ddd.ValueObjects` | Domain (direct) |
+| `BeyondNetCode.Shell.Factory` | `BeyondNetCode.Shell.Factory` · `BeyondNetCode.Shell.DI` | Domain (transitive via Ddd) · Infrastructure (direct) |
+| `BeyondNetCode.Shell.Aop` | `BeyondNetCode.Shell.Aop` · `BeyondNetCode.Shell.DispatchProxy` · `BeyondNetCode.Shell.Aspects` · `BeyondNetCode.Shell.Logger.Serilog` · `BeyondNetCode.Shell.DI` | Application (attribute contract) · Infrastructure (DI wiring + adapters) |
+| `BeyondNetCode.Shell.Bootstrapper` | `BeyondNetCode.Shell.Bootstrapper` · `BeyondNetCode.Shell.DI` · `BeyondNetCode.Shell.AutoMapper` · `BeyondNetCode.Shell.Observability` | Infrastructure · Presentation (startup) |
 
 ---
 
 ## Decision
 
 UMS adopts a **Shell Library Isolation** strategy for all shared infrastructure patterns:
 
-1. All shell assemblies use the `Ums.Shell.*` namespace and project naming convention.
+1. All shell assemblies use the `BeyondNetCode.Shell.*` namespace and project naming convention.
 2. Application layers must not reference upstream namespaces such as `BeyondNet.*` or source repository names such as `csdevlib.*`.
 3. Shell libraries must compile cross-platform and target the current stable .NET baseline used by the API (`net10.0`).
 4. Dependency direction is strictly enforced as described below.
@@ -46,31 +46,31 @@ Ums.Presentation
 Ums.Infrastructure
   ├── Ums.Application
   ├── Ums.Domain
-  ├── Ums.Shell.Aop.Microsoft.Extensions.DependencyInjection.Aspects.Installer
-  │     └── Ums.Shell.Aop.Aspects (transitive)
-  │           └── Ums.Shell.Aop (transitive)
-  │                 └── Ums.Shell.Aop.DispatchProxy (transitive)
-  └── Ums.Shell.Aop.Aspects.Logger.Serilog (transitive via installer)
+  ├── BeyondNetCode.Shell.DI
+  │     └── BeyondNetCode.Shell.Aspects (transitive)
+  │           └── BeyondNetCode.Shell.Aop (transitive)
+  │                 └── BeyondNetCode.Shell.DispatchProxy (transitive)
+  └── BeyondNetCode.Shell.Logger.Serilog (transitive via installer)
 
 Ums.Application
   ├── Ums.Domain
-  └── Ums.Shell.Aop.Aspects    ← attribute contract only (no DI, no runtime proxy)
+  └── BeyondNetCode.Shell.Aspects    ← attribute contract only (no DI, no runtime proxy)
 
 Ums.Domain
-  ├── Ums.Shell.Ddd
-  │     └── Ums.Shell.Factory (transitive via Ddd)
-  └── Ums.Shell.Ddd.ValueObjects
-        └── Ums.Shell.Ddd (transitive)
+  ├── BeyondNetCode.Shell.Ddd
+  │     └── BeyondNetCode.Shell.Factory (transitive via Ddd)
+  └── BeyondNetCode.Shell.Ddd.ValueObjects
+        └── BeyondNetCode.Shell.Ddd (transitive)
 ```
 
-> **Correction from original ADR (2026-05-15):** `Ums.Domain.csproj` previously listed a direct `<ProjectReference>` to `Ums.Shell.Factory`. This was a redundant reference — `Ums.Shell.Ddd` already depends on `Ums.Shell.Factory`, making it available transitively. The direct reference was removed on 2026-05-24. Domain code must access factory abstractions only through the DDD shell layer, not by directly importing the Factory namespace.
+> **Correction from original ADR (2026-05-15):** `Ums.Domain.csproj` previously listed a direct `<ProjectReference>` to `BeyondNetCode.Shell.Factory`. This was a redundant reference — `BeyondNetCode.Shell.Ddd` already depends on `BeyondNetCode.Shell.Factory`, making it available transitively. The direct reference was removed on 2026-05-24. Domain code must access factory abstractions only through the DDD shell layer, not by directly importing the Factory namespace.
 
 ### Rules per layer
 
 | Layer | May reference | May NOT reference |
 |---|---|---|
-| `Ums.Domain` | `Ums.Shell.Ddd`, `Ums.Shell.Ddd.ValueObjects` | Any `Ums.Shell.Aop.*`, `Ums.Shell.Factory` (direct), `Ums.Shell.Bootstrapper.*` |
-| `Ums.Application` | `Ums.Domain`, `Ums.Shell.Aop.Aspects` (attr contract) | `Ums.Shell.Aop.DispatchProxy`, `Ums.Shell.Aop.*.Installer`, `Ums.Shell.Factory`, `Ums.Shell.Bootstrapper.*` |
+| `Ums.Domain` | `BeyondNetCode.Shell.Ddd`, `BeyondNetCode.Shell.Ddd.ValueObjects` | Any `BeyondNetCode.Shell.Aop.*`, `BeyondNetCode.Shell.Factory` (direct), `BeyondNetCode.Shell.Bootstrapper.*` |
+| `Ums.Application` | `Ums.Domain`, `BeyondNetCode.Shell.Aspects` (attr contract) | `BeyondNetCode.Shell.DispatchProxy`, `BeyondNetCode.Shell.Aop.*.Installer`, `BeyondNetCode.Shell.Factory`, `BeyondNetCode.Shell.Bootstrapper.*` |
 | `Ums.Infrastructure` | All of the above + AOP installer + Bootstrapper | — |
 | `Ums.Presentation` | All layers + Bootstrapper for startup | — |
 
@@ -82,15 +82,15 @@ Ums.Domain
 
 - UMS has a stable internal dependency surface for tactical DDD, Factory, AOP, and Bootstrapper patterns.
 - Domain code is pure of all infrastructure concerns — no AOP, no DI, no logging imports.
-- `Ums.Application` references only the AOP **attribute contract** (`Ums.Shell.Aop.Aspects`) — handlers declare cross-cutting intent via attributes without coupling to the proxy infrastructure.
+- `Ums.Application` references only the AOP **attribute contract** (`BeyondNetCode.Shell.Aspects`) — handlers declare cross-cutting intent via attributes without coupling to the proxy infrastructure.
 - Upstream source changes can be absorbed inside `src/libs/shell` without touching application layers.
 - The `IMelLogger` pattern (marker interface in Application, concrete adapter in Infrastructure) demonstrates how to apply the same isolation principle to cross-cutting adapters.
 
 ### Trade-offs
 
 - The shell layer is a real architectural dependency and must be versioned and reviewed accordingly.
 - Security and package warnings from shell dependencies (e.g., `OpenTelemetry.Api` CVE in Bootstrapper) affect the UMS build health.
-- `Ums.Shell.Ddd` depends on `Ums.Shell.Factory` — this coupling is intentional (DDD construction can use factory abstractions internally) but means that adding a Factory dependency to Domain is sufficient to pull in Factory everywhere Domain is referenced.
+- `BeyondNetCode.Shell.Ddd` depends on `BeyondNetCode.Shell.Factory` — this coupling is intentional (DDD construction can use factory abstractions internally) but means that adding a Factory dependency to Domain is sufficient to pull in Factory everywhere Domain is referenced.
 
 ---
 
@@ -103,15 +103,15 @@ The following checks are mandatory after any change to the shell library referen
 dotnet build src/apps/ums.api/Ums.sln
 
 # 2. Run all shell library test suites
-dotnet test src/libs/shell/aop/src/Ums.Shell.Aop.Tests/Ums.Shell.Aop.Tests.csproj --verbosity minimal
-dotnet test src/libs/shell/factory/src/Ums.Shell.Factory.Test/Ums.Shell.Factory.Test.csproj --verbosity minimal
+dotnet test src/libs/shell/aop/src/BeyondNetCode.Shell.Aop.Tests/BeyondNetCode.Shell.Aop.Tests.csproj --verbosity minimal
+dotnet test src/libs/shell/factory/src/BeyondNetCode.Shell.Factory.Test/BeyondNetCode.Shell.Factory.Test.csproj --verbosity minimal
 
 # 3. Verify Domain purity (no AOP refs in Domain)
-grep -r "Ums.Shell.Aop" src/apps/ums.api/Ums.Domain/ --include="*.csproj"
+grep -r "BeyondNetCode.Shell.Aop" src/apps/ums.api/Ums.Domain/ --include="*.csproj"
 # Expected: no output
 
 # 4. Verify no direct Factory ref in Domain (must be transitive only)
-grep "Ums.Shell.Factory" src/apps/ums.api/Ums.Domain/Ums.Domain.csproj
+grep "BeyondNetCode.Shell.Factory" src/apps/ums.api/Ums.Domain/Ums.Domain.csproj
 # Expected: no output
 ```