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

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

**Cumulative failed runs observed:** 1 (over 100 total runs, 1 nightlies)
**First seen:** 2026-09-05 · **Last seen:** 2026-09-05

### Per-config cumulative

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

```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 1,
"total_runs": 100
}
},
"cumulative_failed_runs": 1,
"cumulative_total_runs": 100,
"first_seen": "2026-09-05",
"last_seen": "2026-09-05",
"nightly_count": 1,
"target": "//score/mw/com/test/move_semantics/skeleton_event/integration_test:move_assign_offered_skeleton_same_process_test"
}
```

Start with the target //score/mw/com/test/move_semantics/skeleton_event/integration_test:move_assign_offered_skeleton_same_process_test and run it under the gcc15-integration configuration. Inspect the move-semantics skeleton-event integration test and its failure output to identify the intermittent behavior. Done means the cause is understood and the target runs reliably without recurring failures.

Written by the indexing model from the issue text.