Flaky test: //score/mw/com/test/move_semantics/skeleton_event/integration_test:move_construct_not_offered_skeleton_same_process_test

## Flaky test: `//score/mw/com/test/move_semantics/skeleton_event/integration_test:move_construct_not_offered_skeleton_same_process_test`

**Cumulative failed runs observed:** 2 (over 200 total runs, 2 nightlies)
**First seen:** 2026-08-10 · **Last seen:** 2026-08-17

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 1 | 100 |
| qnx-integration | 1 | 100 |

```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 1,
"total_runs": 100
},
"qnx-integration": {
"failed_runs": 1,
"total_runs": 100
}
},
"cumulative_failed_runs": 2,
"cumulative_total_runs": 200,
"first_seen": "2026-08-10",
"last_seen": "2026-08-17",
"nightly_count": 2,
"target": "//score/mw/com/test/move_semantics/skeleton_event/integration_test:move_construct_not_offered_skeleton_same_process_test"
}
```

Start with the named //score/mw/com/test/move_semantics/skeleton_event/integration_test:move_construct_not_offered_skeleton_same_process_test target and reproduce it in the gcc15-integration and qnx-integration configurations. Inspect the test and failure output to identify the intermittent behavior; done means the test passes reliably across those configurations.

Written by the indexing model from the issue text.