[AZ-315] Sync architecture docs after coupling refactor

Phase C of architecture coupling refactor (epic AZ-309). Closes the
last baseline finding (F5 — DataAccess incorrectly documented as
importing Common) and synchronizes the rest of _docs/02_document/
with the post-split project layout from AZ-312/313/314:

- module-layout.md: per-component sections for the three new csprojs
  with explicit ProjectReferences and the no-cross-sibling-reference
  invariant the split enforces.
- architecture.md: components and internal-communication tables
  updated to show calls flow through Common interfaces.
- architecture_compliance_baseline.md: F1..F5 marked Resolved with
  task IDs and commit refs; baseline summary now 0 findings.
- diagrams/components.md, components/03_tile_downloader/description.md,
  modules/{common_interfaces,services_tile_service,
  services_google_maps_downloader,tests_unit}.md updated for the
  split, RateLimitException relocation, and new ITileService methods.

Documentation-only batch — no code, no tests, no build changes.
Epic AZ-309 complete (6 tasks across 3 batches).

Co-authored-by: Cursor <cursoragent@cursor.com>

_docs/03_implementation/reviews/batch_06_review.md

@@ -0,0 +1,89 @@
+# Code Review Report
+
+**Batch**: 6 (AZ-315 — documentation sync, Phase C of coupling refactor)
+**Date**: 2026-05-10
+**Verdict**: PASS
+
+## Scope
+
+Documentation-only batch. No source code, build configuration, or test changes. Closes epic AZ-309 (architecture coupling refactor) by syncing the architecture / module-layout / compliance baseline / per-component module docs to the post-split reality.
+
+## Changed files
+
+- `_docs/02_document/architecture.md` — components list updated with csproj names; internal-communication table updated to reflect calls flowing through Common interfaces (no direct concrete dependencies).
+- `_docs/02_document/module-layout.md` — three Layer-3 components now have their own per-component sections with csproj path, public API list, ProjectReferences, and explicit "no cross-sibling reference" note. Allowed-Dependencies table simplified to one Layer-3 row stating siblings communicate only through Common interfaces. Verification section corrects DataAccess → Common assumption (F5).
+- `_docs/02_document/architecture_compliance_baseline.md` — F1, F2, F3, F4, F5 marked Resolved with task IDs and commit references; baseline summary now shows 0 findings post AZ-309.
+- `_docs/02_document/diagrams/components.md` — component summary table updated with new csproj names; added clarifying note that Layer-3-to-Layer-3 arrows are logical-only via Common interfaces; removed incorrect `DA --> Common` edge.
+- `_docs/02_document/components/03_tile_downloader/description.md` — csproj path added; `ITileService` extended interface enumerated; downloader/service consumers note clarified.
+- `_docs/02_document/modules/common_interfaces.md` — implementations now mapped to per-component csprojs; new ITileService methods documented.
+- `_docs/02_document/modules/services_tile_service.md` — csproj path added; `GetOrDownloadTileAsync` and `DownloadAndStoreSingleTileAsync` documented; `IMemoryCache` dependency declared.
+- `_docs/02_document/modules/services_google_maps_downloader.md` — csproj path added; RateLimitException relocation noted.
+- `_docs/02_document/modules/tests_unit.md` — ProjectReferences updated to the three new service projects.
+- `_docs/02_tasks/_dependencies_table.md` — refactor tasks marked Done / In Progress.
+
+## Findings
+
+| # | Severity | Category | File:Line | Title |
+|---|----------|----------|-----------|-------|
+
+No findings.
+
+## Phase results
+
+### Phase 2 — Spec compliance (AC verification)
+
+- **AC-1: Architecture doc reflects the split** ✓
+  `architecture.md` Architecture Vision and Internal Communication sections name all three csprojs and explicitly state cross-sibling calls use Common interfaces.
+- **AC-2: Module layout is accurate** ✓
+  `module-layout.md` § Per-Component Mapping has one section per new csproj with `csproj`, `Public API`, `ProjectReferences`, `Imports from`, and `Consumed by` keyed to the actual on-disk layout.
+- **AC-3: Compliance baseline closed for F3/F4** ✓
+  `architecture_compliance_baseline.md` table has a Status column; F3/F4/F5 each cite the resolving task IDs (AZ-310/311 for F3, AZ-312/313/314 for F4, AZ-315 for F5) and commit hash where applicable.
+- **AC-4: No stale references to current state** ✓
+  `grep "SatelliteProvider\.Services[^.]"` against `_docs/02_document/` returns matches only in:
+  - `00_discovery.md` (historical baseline snapshot — pre-refactor by design)
+  - `architecture_compliance_baseline.md` (describing the resolved-state of historical findings)
+  - `module-layout.md` § Layout Rule #1 (one historical-context mention naming the project that was split)
+  - `components/03_tile_downloader/description.md` (one historical-context mention explaining the relocation)
+  No current-state description still claims a single Services project.
+
+### Phase 3 — Code quality
+
+N/A — no code changes.
+
+### Phase 4 — Security quick-scan
+
+N/A — no code changes.
+
+### Phase 5 — Performance scan
+
+N/A — no code changes.
+
+### Phase 6 — Cross-task consistency
+
+- All updated docs use consistent naming for the three new csprojs.
+- Cross-doc references (architecture → module-layout → diagrams → per-component descriptions) form a coherent narrative without contradictions.
+- F5 resolution in module-layout.md (Verification section) and architecture_compliance_baseline.md agree.
+
+### Phase 7 — Architecture compliance
+
+N/A on the code side — no code changes. On the doc side, the docs now accurately describe the architecture rather than the pre-refactor state.
+
+## Baseline Delta
+
+Final state of `architecture_compliance_baseline.md` after this batch:
+
+| Finding | Severity | Status |
+|---------|----------|--------|
+| F1 — Concrete dependency on GoogleMapsDownloaderV2 | High | Resolved (pre-AZ-309) |
+| F2 — ISatelliteDownloader is dead code | High | Resolved (pre-AZ-309) |
+| F3 — API endpoint bypasses service layer | Medium | Resolved (AZ-310 + AZ-311) |
+| F4 — No physical boundary in Services project | Medium | Resolved (AZ-312 + AZ-313 + AZ-314) |
+| F5 — DataAccess documented as importing Common (incorrect) | Low | Resolved (AZ-315) |
+
+**Newly introduced**: none.
+**Carried over**: none.
+**Resolved this batch**: F5.
+
+## Verdict
+
+**PASS** — all 4 ACs satisfied. Documentation now matches the actual project layout. Architecture compliance baseline is fully closed.