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

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

**Cumulative failed runs observed:** 3 (over 300 total runs, 3 nightlies)
**First seen:** 2026-09-02 · **Last seen:** 2026-09-10

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 3 | 300 |

```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 3,
"total_runs": 300
}
},
"cumulative_failed_runs": 3,
"cumulative_total_runs": 300,
"first_seen": "2026-09-02",
"last_seen": "2026-09-10",
"nightly_count": 3,
"target": "//score/mw/com/test/move_semantics/skeleton_method/integration_test:move_construct_after_offered_skeleton_different_process_test"
}
```

Start by locating and running the Bazel target //score/mw/com/test/move_semantics/skeleton_method/integration_test:move_construct_after_offered_skeleton_different_process_test under the gcc15-integration configuration. Inspect its failure output and the three recorded nightly failures to identify the cross-process flakiness. Done means the cause is addressed and repeated runs no longer fail intermittently.

Written by the indexing model from the issue text.