Remind Richie tomorrow: 202 stale ChargePoint LoadShedEvents scheduled for July 8 (VEC prod)

Reminder-only task. Do NOT act on this without Richie's go-ahead — he said he's already working on the cancel/teardown path and no rush. Context for the reminder: - Two accidental WorkspaceProgramEvents were published on 2026-06-30 at 20:56:57 UTC and 21:23:43 UTC against VEC production workspace (cm932a8ny0009dyf4y12f9jlp), workspaceProgram cmpgzt4a800036n8h44xt35gc (Flexible Load Program - EV and Charger Application), each set with a start of July 8 by mistake. - Because the start was >1 minute in the future, the adapter took the native createLoadShedEvent path both times: 101 stations × 2 events = 202 ChargePoint LoadShedEvent IDs, all outcome=scheduled. Sample IDs range 782965431–7829655xx (first batch) and 783032861–7830329xx (second batch); full mapping is in Datadog under service:oem-adapter @meta.soapAction:createLoadShedEvent between 20:55–21:25 UTC on 2026-06-30. - Richie cleaned up the platform-side rows (WorkspaceProgramEvent + Batch) but the adapter has NO cancellation path today, so ChargePoint still holds all 202 sheds queued for July 8. - Zero clearShedState or cancelLoadShedEvent SOAP calls were sent during cleanup — confirmed via Datadog. When reminding, mention: 1. There are 202 stale scheduled sheds sitting in ChargePoint for July 8 against VEC's 101 chargers (each station has two overlapping scheduled sheds). 2. The adapter cancel path he's already working on will need cancelLoadShedEvent support (ChargePoint SOAP `cancelLoadShedEvent(sgID)` takes the LoadShedEvent ID that createLoadShedEvent returned). Best pattern is probably storing the returned eventId on the Command record so cancellation-by-command becomes trivial. 3. If the cancel adapter work is not ready before July 8, we need a manual mitigation — I have the full (commandId, eventId, stationId) mapping in Datadog and can produce a one-off script that walks the list and calls cancelLoadShedEvent per event. --- Heartbeat note (2026-07-02 22:57 UTC): reminder window (2026-07-02 14:00-18:00 UTC) missed AGAIN — heartbeats today were saturated with PR #12984, #12993 CI-watch + Bugbot loops + a live thread from Richie on program load curve spec. No top-level VEC ChargePoint DM from Richie today. Deferring the one-shot reminder to 2026-07-03 14:00-18:00 UTC. July 8 is still 5-6 days out — comfortable buffer for one more day of slippage. Cadence: send once at start of 14:00 UTC heartbeat tomorrow (2026-07-03). If Richie messages first, mark completed.