Flaky test: //score/mw/com/test/fields/set_and_get_and_notifier/integration_test:test_get_and_notifier_same_process

## Flaky test: `//score/mw/com/test/fields/set_and_get_and_notifier/integration_test:test_get_and_notifier_same_process`

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

### 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-08-28",
"last_seen": "2026-08-28",
"nightly_count": 1,
"target": "//score/mw/com/test/fields/set_and_get_and_notifier/integration_test:test_get_and_notifier_same_process"
}
```

Start with the Bazel target //score/mw/com/test/fields/set_and_get_and_notifier/integration_test:test_get_and_notifier_same_process and inspect its gcc15-integration runs. Reproduce the reported flake and determine why the test fails intermittently in the same-process configuration; done means the target passes reliably across repeated runs.

Written by the indexing model from the issue text.