# Refactor: update consumers (Api, Tests, IntegrationTests) for split

**Task**: AZ-313_refactor_update_consumers
**Name**: Update consumer csprojs and using directives after Services split
**Description**: Re-wire `SatelliteProvider.Api`, `SatelliteProvider.Tests`, and `SatelliteProvider.IntegrationTests` to reference the three new per-component csprojs.
**Complexity**: 3 points
**Dependencies**: AZ-312
**Component**: API + Tests
**Tracker**: AZ-313
**Epic**: AZ-309

## Problem

After AZ-312 splits `SatelliteProvider.Services` into three csprojs, every consumer of the old project breaks (compile errors). This task fixes the consumers without changing any test logic or DI behavior.

## Outcome

- `SatelliteProvider.Api.csproj` references all three new Services projects.
- `SatelliteProvider.Tests.csproj` references whichever Services projects its current tests depend on (typically all three; verify per file).
- `SatelliteProvider.IntegrationTests.csproj` references whichever Services projects its current tests depend on.
- All `using SatelliteProvider.Services;` directives across consumers replaced with the correct `using SatelliteProvider.Services.<Component>;` directive.
- `dotnet build SatelliteProvider.sln` succeeds.
- All previously-green unit tests remain green.

## Scope

### Included
- Edit `.csproj` files of Api, Tests, IntegrationTests: add new `ProjectReference` entries, remove the old `SatelliteProvider.Services` reference.
- Update all `using` directives in `.cs` files under those three projects.
- Run `dotnet build` to confirm zero errors.
- Run unit test suite (`SatelliteProvider.Tests`) to confirm zero regressions vs. Step 6 baseline.

### Excluded
- DI container registration changes — those happen in AZ-314.
- Re-running integration suite — that happens in AZ-315.
- Changing any test assertion or test data.

## Acceptance Criteria

**AC-1: Solution builds clean**
Given the post-refactor consumer csprojs
When `dotnet build SatelliteProvider.sln` is run
Then build succeeds with zero errors and zero new warnings vs. the pre-refactor baseline.

**AC-2: Unit tests green**
Given the post-refactor consumer csprojs
When `dotnet test SatelliteProvider.Tests` is run
Then all 35 (or current baseline count) unit tests pass.

**AC-3: No stale `using SatelliteProvider.Services;`**
Given the post-refactor source tree
When grepping for `using SatelliteProvider.Services;` (without a `.<Component>` suffix)
Then zero matches outside intentional comments.

## Constraints

- No DI registration changes in this task.
- No test logic, fixture, or assertion changes.

## Risks & Mitigation

**Risk 1: Shadowed types if a single file references types from two of the new components**
- *Risk*: A test that exercises both `RegionService` and `RouteService` needs both `using` statements.
- *Mitigation*: Add both. Compiler will tell us which.
