Flaky test: //score/mw/com/test/subscribe_handler/integration_test:subscribe_handler

## Flaky test: `//score/mw/com/test/subscribe_handler/integration_test:subscribe_handler`

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

### Per-config cumulative

| Config | Failed | Total |
|--------|-------:|------:|
| gcc15-integration | 2 | 200 |

```json
{
"configs": {
"gcc15-integration": {
"failed_runs": 2,
"total_runs": 200
}
},
"cumulative_failed_runs": 2,
"cumulative_total_runs": 200,
"first_seen": "2026-08-13",
"last_seen": "2026-08-28",
"nightly_count": 2,
"target": "//score/mw/com/test/subscribe_handler/integration_test:subscribe_handler"
}
```

Start by running the Bazel target //score/mw/com/test/subscribe_handler/integration_test:subscribe_handler under the gcc15-integration configuration and inspect its test output. Use the two reported nightly failures to reproduce the flakiness; done means the target passes reliably across repeated runs and the intermittent failure is resolved.

Written by the indexing model from the issue text.