chore(deps): update mcr.microsoft.com/playwright docker digest to 02810c9

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
mcr.microsoft.com/playwright	container	digest	9bd26ad → 02810c9

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[roborev-ci]

roborev: Combined Review (db01dbf)

No issues found.

---

Panel: ci_default_security | Synthesis: codex | Members: codex_default (codex/default, done, 25s), codex_security (codex/security, done, 16s) | Total: 41s

[roborev-ci]

roborev: Combined Review (cdb4f74)

Medium issue found: the pinned Playwright container digest appears to point at the wrong image version.

Medium

• .github/workflows/ci.yml:270 and .github/workflows/ci.yml:399
  The updated digest does not match the declared v1.60.0-noble Playwright image. The review reports that mcr.microsoft.com/playwright:v1.60.0-noble resolves to sha256:9bd26ad900bb5e0f4dee75839e957a89ae89c2b7ab1e76050e559790e946b948, while the new sha256:02810c... digest resolves to v1.46.1-jammy.

  Because these jobs run inside the container before checkout/setup/test steps, the container is part of the CI trust boundary. A mismatched digest can downgrade or swap the runtime while the comment still claims v1.60.0-noble, leaving the existing version check satisfied.

  Suggested remediation: restore the digest for mcr.microsoft.com/playwright:v1.60.0-noble, or intentionally update the package pins, image version comment, and digest together. Prefer a tag@sha256 reference and make the guard verify that the digest resolves to the declared tag.

---

Panel: ci_default_security | Synthesis: codex, 16s | Members: codex_default (codex/default, done, 35s), codex_security (codex/security, done, 3m59s) | Total: 4m50s