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

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

**Cumulative failed runs observed:** 6 (over 500 total runs, 5 nightlies)
**First seen:** 2026-08-28 · **Last seen:** 2026-09-07

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 6 | 500 |

```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 6,
"total_runs": 500
}
},
"cumulative_failed_runs": 6,
"cumulative_total_runs": 500,
"first_seen": "2026-08-28",
"last_seen": "2026-09-07",
"nightly_count": 5,
"target": "//score/mw/com/test/move_semantics/skeleton_method/integration_test:move_assign_after_offered_skeleton_different_process_test"
}
```

Start with the Bazel target //score/mw/com/test/move_semantics/skeleton_method/integration_test:move_assign_after_offered_skeleton_different_process_test and reproduce it in the gcc15-integration configuration. Review the test and its move-semantics skeleton-method setup to identify why it fails intermittently across processes. Done means the test no longer exhibits the reported flakiness across repeated runs and the relevant test coverage remains passing.

Written by the indexing model from the issue text.