TypeError: Cannot read properties of undefined (reading 'id') in ChangeRequestDetailPage editChangeRequest

**Sentry:** [FLAGSMITH-FRONTEND-58E](https://flagsmith.sentry.io/issues/7642253636/)

`TypeError: Cannot read properties of undefined (reading 'id')`

### Where
`web/components/pages/ChangeRequestDetailPage.tsx` → `editChangeRequest`.

### Impact
2 events, 1 user affected. 2026-07-30T12:10Z → 12:14Z. Sentry priority: **high**.
Release `1785412572601`, Chrome 150, production.
URL: https://app.flagsmith.com/project/15330/environment/bsqUVtRH8kcp2MJfd8BFua/change-requests/23602

### In-app frames
```
./web/components/pages/ChangeRequestDetailPage.tsx .children.editChangeRequest
/static/main.07099c7a9e35cb93.js b
new Promise
./web/components/pages/ChangeRequestDetailPage.tsx
```

### Likely cause
`editChangeRequest` dereferences `.id` on something undefined — plausibly the
change request or its committed-by/approval object not yet loaded, or absent
for this change request. Two events four minutes apart suggests a retry by the
same user rather than a one-off.

---
[Slack alert](https://flagsmith.slack.com/archives/C05GSDTULDB/p1785413476886019) · filed by the `sentry-triage` skill

Start in web/components/pages/ChangeRequestDetailPage.tsx at editChangeRequest and trace which change-request or committed-by/approval value is accessed before it is loaded or when it is absent. Reproduce the edit flow using the Sentry context if possible, then verify that editing this change request no longer throws a TypeError when the value is undefined.

Written by the indexing model from the issue text.