Run initial test for Climate Resilience Verification Suite

Add first part of Alert Quality Analytics

docs/simulator-guide.md

@@ -17,6 +17,7 @@ Think of it as a flight simulator, but for clinical decision support.
 7. [Reading the Output](#7-reading-the-output)
 8. [Creating Your Own Scenarios](#8-creating-your-own-scenarios)
 9. [Troubleshooting](#9-troubleshooting)
+10. [Ward Outage Scenario (Climate Resilience)](#10-ward-outage-scenario-climate-resilience)
 
 ---
 
@@ -76,6 +77,12 @@ dotnet run --project VigilCare.Simulator -- replay <scenario-file> [options]
 | `--base-url <url>` | `http://localhost:5270` | API address (change if your API runs elsewhere) |
 | `--poll` | off | Show alerts and scores after each set of vitals |
 | `--poll-interval <seconds>` | 5 | How often to check for alerts when polling |
+| `--username <name>` | `physician.demo` | API login username |
+| `--password <secret>` | (demo default) | API login password |
+| `--gateway` | off | Target the ward gateway API at `http://localhost:5081` |
+| `--encounter-id <guid>` | — | Use an existing encounter (required with `--gateway`; also used with `--skip-setup`) |
+| `--skip-setup` | off | Skip patient/encounter registration — requires `--encounter-id` |
+| `--gateway-token <jwt>` | `$GATEWAY_JWT` | Bearer token for gateway replay (required with `--gateway`; use `./scripts/mint-gateway-jwt.sh`) |
 
 **Example -- run the stable baseline scenario in real-time with polling:**
 
@@ -200,6 +207,9 @@ The key concept is **offsetMinutes** -- each event happens at a certain number o
 | `medication` | A drug being administered | Ceftriaxone 1g IV |
 | `order` | A clinical order being placed | "Blood cultures", "Chest X-ray" |
 | `order_result` | Result of a prior order | "Positive for E. coli" |
+| `alert_ack` | Acknowledgement of an open alert | RN acknowledges critical potassium alert |
+
+`alert_ack` events require `alertType` and `clinicianId` in `data`; optional `note`. On **gateway** replay (`--gateway`), the simulator sends `clinicianId` in the acknowledge request so the ward records the bedside nurse label (e.g. `RN-Wu`) and syncs it to central. On **central** replay, attribution comes from the logged-in API user.
 
 ### Vital Sign Codes
 
@@ -236,6 +246,7 @@ The simulator ships with 8 scenarios covering different clinical situations:
 | **dka-electrolyte-01** | Diabetic ketoacidosis with potassium and glucose derangement. | Varies |
 | **hypothermia-elderly-01** | Elderly patient with severe hypothermia. Slow HR, dropping temperature. | Varies |
 | **medication-false-alarm-01** | Beta-blocker causing bradycardia. Tests whether the system correctly handles medication-induced vital changes. | 3 hours |
+| **ward-outage-reconnect-01** | ICU patient with critical hyperkalemia during simulated central outage. Validates gateway-local alerting and alert acknowledgement sync. | 90 minutes |
 
 All scenario files are in: `VigilCare.Simulator/Scenarios/List/`
 
@@ -398,3 +409,83 @@ Use `--base-url`:
 dotnet run --project VigilCare.Simulator -- replay scenario.json \
   --base-url http://192.168.1.50:5270
 ```
+
+---
+
+## 10. Ward Outage Scenario (Climate Resilience)
+
+The `ward-outage-reconnect-01` scenario validates Tier 1 safety during a central API outage. Observations and alerts continue on the ward gateway; acknowledgements are recorded locally and synced when the uplink returns.
+
+### Automated verification (recommended)
+
+From the repo root, with Docker running:
+
+```bash
+./scripts/run-phase24-verification.sh
+```
+
+This script runs all three phases automatically: central baseline replay, gateway replay during simulated central outage, and post-reconnect sync checks. Logs go to `/tmp/vigilcare-phase24-*`.
+
+Useful flags:
+
+| Env var | Effect |
+|---------|--------|
+| `SKIP_DOCKER=1` | Assume `docker compose` stack is already up |
+| `SKIP_PHASE_A=1` | Skip central replay; use an existing ICU encounter on the gateway |
+
+Helper for manual gateway API calls (ward gateway has no login endpoint):
+
+```bash
+export GATEWAY_JWT=$(./scripts/mint-gateway-jwt.sh nurse.demo NURSE)
+```
+
+### Manual procedure
+
+1. Full stack running with the ward gateway profile:
+
+```bash
+docker compose --profile ward-gateway up -d
+```
+
+2. Central API running and the gateway encounter replica synced
+3. Note an active ICU encounter id from the gateway:
+
+```bash
+curl "http://localhost:5081/api/v1/encounters?status=ACTIVE&department=ICU" \
+  -H "Authorization: Bearer $JWT"
+```
+
+### Procedure
+
+**Phase A — Baseline on central (optional):**
+
+```bash
+dotnet run --project VigilCare.Simulator -- replay \
+  VigilCare.Simulator/Scenarios/List/ward-outage-reconnect-01.json \
+  --speed 0 --base-url http://localhost:5270
+```
+
+**Phase B — Stop central, replay against gateway:**
+
+```bash
+# Stop central API process/container
+dotnet run --project VigilCare.Simulator -- replay \
+  VigilCare.Simulator/Scenarios/List/ward-outage-reconnect-01.json \
+  --gateway --encounter-id <ENCOUNTER-GUID> --speed 60 --poll
+```
+
+The `--gateway` flag targets `http://localhost:5081` automatically. `--encounter-id` must reference an encounter already replicated on the gateway. The `alert_ack` event at T+50 min sends `clinicianId: "RN-Wu"` from the scenario; the gateway honors this in `acknowledged_by` and in the sync buffer (login user is only used when `clinicianId` is omitted).
+
+**Phase A note:** Central replay attributes acks to the JWT user (`physician.demo` by default). Use `--username nurse.demo` if you want a nurse role on central; gateway Phase B is the authoritative climate-resilience path for scenario attribution.
+
+**Phase C — Restart central, verify sync:**
+
+- Wait for `SyncUploaderService` to drain the buffer
+- Poll `GET /api/v1/operations/gateways` — buffer depth should reach 0
+- Confirm observations on central with preserved `recorded_at` timestamps
+
+### Success criteria
+
+- Critical potassium alert created on gateway at T+45 min while central is down
+- Ack recorded locally at T+50 min with `acknowledged_by` = `RN-Wu`
+- After reconnect: central has observations, alert, and ack; no duplicate paging logs