# Refactor: delete write-only counters in RegionRequestQueue

**Task**: AZ-363_refactor_delete_writeonly_counters
**Name**: Remove non-atomic write-only counters
**Description**: Delete `_totalEnqueued` and `_totalDequeued` fields plus the two `++` lines in `RegionRequestQueue`.
**Complexity**: 1 point
**Dependencies**: None
**Component**: Services.RegionProcessing
**Tracker**: AZ-363
**Epic**: AZ-350

## Problem

`SatelliteProvider.Services.RegionProcessing/RegionRequestQueue.cs:12-13, 28, 38` uses `_totalEnqueued++` and `_totalDequeued++` on `int` fields. The increments are not atomic under concurrent producers/consumers, and the fields are never read anywhere in the codebase. Telemetry-via-`++` is both a thread-safety bug and dead code.

## Outcome

- The two fields and the two `++` lines are removed.
- 37 unit + 5 smoke tests stay green.

## Scope

### Included
- Delete the field declarations.
- Delete the `++` lines from `Enqueue` / `Dequeue`.

### Excluded
- Adding proper `Meter`/`Counter<long>` telemetry (deferred to a future observability ticket).

## Acceptance Criteria

**AC-1: Fields and increments removed**
Given the post-refactor `RegionRequestQueue.cs`
When grepped for `_totalEnqueued` or `_totalDequeued`
Then zero matches.

**AC-2: Tests stay green**
Given the post-refactor build
When `scripts/run-tests.sh --smoke` runs
Then all 37 unit + 5 smoke scenarios pass.

## Constraints

- No public API change (fields are private).

## Risks & Mitigation

**Risk 1: future telemetry need**
- *Risk*: someone may want enqueue/dequeue counts later.
- *Mitigation*: that's a separate, properly-implemented (atomic, read-out) ticket.

Full change entry: `_docs/04_refactoring/03-code-quality-refactoring/list-of-changes.md` (C10).
