fleet-probe: default branch `develop` is red

[rafeekpro]

develop is red — and a red default branch is nobody's pull request.

After a merge there is no PR left to carry the failure, so nothing in the review loop
picks this up on its own. That is why this issue exists (pr-review-gate#266). It is
maintained by the fleet probe: the body is rewritten with current evidence every pass, and
the issue closes itself when the branch goes green.

Branch	develop
Failing checks	Playwright full
Head commit	73921020d051
Red since	2026-08-09 05:37 UTC — 18 h 0 min
Last observed red	2026-08-09 23:37 UTC
Checks on the head	12 total, 1 failing, 0 still running

Failing run: https://github.com/lagowski/dap/actions/runs/31294921576/job/93198342791

Open pull requests targeting develop — one of these may already carry the fix:

• #863 chore: sync AI review gate (pr-review-gate) — mergeable_state: blocked

---

What to do

1. Open the failing run above and read the first failing step.
2. If a pull request above is clean, it may already carry the fix — merging it is the
   fastest route, and this issue closes itself within the hour afterwards.
3. Otherwise push a fix to develop through a PR, as the gate requires.

Nothing above is a judgement: every line is a GitHub API read plus a comparison, made by
app/fleet_probe.py with no model involved. If this issue is wrong, the check that
produced it is wrong — please say so on veracrew#402 rather than only closing this.

[rafeekpro]

Green again — closing.

• red from: 2026-08-09 05:37 UTC
• last observed red: 2026-08-09 23:37 UTC
• observed green: 2026-08-10 00:37 UTC
• red for: 18 h 0 min of observed time

The branch recovered somewhere between the last two timestamps — the probe samples hourly, so it cannot say more precisely than that, and does not pretend to. If it goes red again a NEW issue is opened rather than this one reopened, so each incident keeps its own history.