docs(components): verification pass — fix cross-link targets, tag code fences, correct type names

- Fix 15 link-text/target mismatches (ConfigurationDatabase ×8 to Commons,
  NotificationOutbox ×4, ClusterInfrastructure case, HealthMonitoring,
  SiteCallAudit) caught by a link-text-vs-target consistency check.
- Tag 14 untagged code-fence openers (ASCII diagrams/trees, JSON, HTTP).
- Correct 4 type names to match source (ValidationService, HealthReportSender,
  CentralCommunicationActor, DebugSnapshotCommand set).
- Soften Traefik version prose per the style guide.

docs/components/SiteCallAudit.md

@@ -20,7 +20,7 @@ The Notification Outbox (#21) ingests notifications and dispatches them centrall
 
 The `SiteCalls` table holds one row per `TrackedOperationId`. `ISiteCallAuditRepository.UpsertAsync` implements insert-if-not-exists followed by a conditional update that only applies when the incoming status has a strictly higher rank than the stored status:
 
-```
+```text
 Submitted=0, Forwarded=1, Attempted=2, Skipped=2,
 Delivered=3, Failed=3, Parked=3, Discarded=3
 ```
@@ -119,7 +119,7 @@ Unlike the `AuditLog` table, `SiteCalls` is a standard non-partitioned table on
 
 ### Status lifecycle
 
-```
+```text
 Submitted → Forwarded → Attempted ──→ Delivered   (terminal, success)
                                   └──→ Parked      (non-terminal, awaiting operator action)
                                   └──→ Failed      (terminal, permanent failure)
@@ -221,7 +221,7 @@ Registration is via `ServiceCollectionExtensions.AddSiteCallAudit`, which binds
 - [Central–Site Communication (#5)](./Communication.md) — the `CentralCommunicationActor` is the transport the relay handlers use. It is registered via `RegisterCentralCommunication` by the Host after both actors are running. `CommunicationService` also provides the async wrappers (`RetrySiteCallAsync`, `DiscardSiteCallAsync`) that the Central UI calls; those methods Ask the `SiteCallAuditActor` with the outer `CommunicationOptions.QueryTimeout`.
 - [Store-and-Forward Engine (#6)](./StoreAndForward.md) — site-side executor of `RetryParkedOperation` and `DiscardParkedOperation`. The site's S&F buffer is the source of truth for parked cached calls; it emits updated telemetry after applying an operator action.
 - [Health Monitoring (#11)](./HealthMonitoring.md) — consumes `SiteCallKpiResponse` / `PerSiteSiteCallKpiResponse` to surface buffered count, parked count, stuck count, and throughput KPI tiles on the health dashboard alongside the Notification Outbox tiles.
-- [Central UI (#9)](./Host.md) — the Site Calls page queries this actor for the paginated list, detail modal, and KPIs; it issues Retry/Discard actions that flow through `CommunicationService` to the relay handlers here.
+- [Central UI (#9)](./CentralUI.md) — the Site Calls page queries this actor for the paginated list, detail modal, and KPIs; it issues Retry/Discard actions that flow through `CommunicationService` to the relay handlers here.
 - [Cluster Infrastructure (#13)](./ClusterInfrastructure.md) — hosts the `SiteCallAuditActor` singleton with active/standby failover via `ClusterSingletonManager`.
 
 ## Troubleshooting