fix(gateway-protocol): regenerate validators for update notice fields (#203413)

## Problem

`build-artifacts` is red on `main`: the `pnpm validators:check` step fails with

```
Error: packages/gateway-protocol/src/compiled/protocol.generated/predicates.js is stale; run pnpm gateway:validators:gen
```

Scheduled run: https://github.com/openclaw/openclaw/actions/runs/44980759580 (job 137080867330), and earlier https://github.com/openclaw/openclaw/actions/runs/44976289659.

## Root cause

#203357 (`fix(ui): show app updates outside the conversation`, e76922592a73) added two optional fields to the update-run schema in `packages/gateway-protocol/src/schema/update-runs.ts`:

- `noticeSurface: Type.Optional(Type.Literal("app"))`
- `noticeInApp: Type.Optional(Type.Boolean())`

It did not regenerate the compiled gateway validators, so `predicates.js` no longer matches the schema.

## Fix

Regenerate with the owning script: `pnpm gateway:validators:gen`. No hand edits. The diff adds the two fields to the generated predicates; the rest is check-id renumbering from the generator.

## Evidence

- Base `origin/main` (6375a3690778): `pnpm gateway:validators:check` fails with the error above.
- Head: `pnpm validators:check` (gateway, ui, codex-app-server, static, lobster) exits 0. The other four sub-checks were already fresh on base.

## Merge danger

Two-way door. Generated validator output only; a revert restores the stale file. Blast radius: Gateway protocol validation of update-run payloads, which now accepts the two optional fields the schema already declares.

Co-authored-by: Ayaan Zaidi <hi@obviy.us>