Description
## Head / Body
| Field | Value |
|-------|-------|
| Head | ipad-head-4 (node-d0112bf1) |
| Body | fluffy-dumpling-87 (node-11da9ea3) |
| District | bxl1-test-2 |
| Experience | mercator-talks (portrait) |
| App version | v0.2.150 |
## Known issues at event start
- **WireGuard instability on WiFi**: iPad-4 had 2 orphaned sessions this morning (08:40, 08:56) due to WireGuard tunnel dropping. Body cannot route back to 10.10.200.4 when WireGuard is down.
- **Fix**: ask hospitality to toggle WireGuard off/on in iPad Settings → VPN.
- **Confirm**: ping 10.10.200.4 from node-11da9ae3 exec. If replies come back, tunnel is up.
- Body self-heals the orphan in 1–3 min once confirmed stuck.
## Agent instructions
When hospitality flags a problem with this iPad:
1. Check `GET /api/v1/heads/node-d0112bf1` and `GET /api/v1/nodes/node-11da9ae3`.
2. **WireGuard first**: exec `ping 10.10.200.4 -n 2` on node-11da9ea3. If unreachable → WireGuard down on iPad → hospitality toggle VPN.
3. If `stream_status=streaming` with no active head: body self-heals (grace ~1m, GPU-mismatch ~3m). Force-stop only if stuck beyond 5 min.
4. Append findings under a new `### HH:MM — [summary]` heading.
5. At every full hour and end of day: append an hourly/EOD summary of status, any incidents, and resolution.
## Event log
### 10:25 — Event start
Recovered from 2 WireGuard-drop orphan sessions (08:40, 08:56). WireGuard stable since 08:57. ipad-head-4 streaming mercator-talks on fluffy-dumpling-87.