Flaky test: //score/mw/com/test/move_semantics/skeleton_method/integration_test:move_construct_after_offered_skeleton_same_process_test

## Flaky test: `//score/mw/com/test/move_semantics/skeleton_method/integration_test:move_construct_after_offered_skeleton_same_process_test`

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

### 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-14",
"last_seen": "2026-09-14",
"nightly_count": 1,
"target": "//score/mw/com/test/move_semantics/skeleton_method/integration_test:move_construct_after_offered_skeleton_same_process_test"
}
```

Start by running //score/mw/com/test/move_semantics/skeleton_method/integration_test:move_construct_after_offered_skeleton_same_process_test under the gcc15-integration configuration and inspect the related move-semantics test setup. Done means identifying the intermittent failure and making this test reliable while preserving its intended coverage, then rerunning it repeatedly.

Written by the indexing model from the issue text.