Standalone dev server has no websocket endpoint, so task notifications never arrive locally

Running the project locally with webiny-standalone watch, the admin connects to wss://<host>/api and the connection fails:

[log] Websockets connecting to wss://wby9.localhost/api...
[info] Error in the Websocket connection. {isTrusted: true, type: "error", target: WebSocket, ...}

Against a deployed AWS environment the same client connects fine (wss://….execute-api.eu-central-1.amazonaws.com/dev, connected in ~830ms), so this is specific to the standalone server. packages/cli-standalone and packages/event-handler-standalone have no websocket handling.

Why it matters

Anything that reports progress or failure over WebsocketsSendToIdentityUseCase produces no user-visible feedback in local development. Current callers:

• ai-powerups — CMS entry generation, page generation, image enrichment
• api-record-locking — KickOutCurrentUser

The AI generation path is the clearest symptom. The task resolves the capability, calls the provider, fails, and calls sendErrorToUser correctly. On AWS that surfaces as a toast — verified: "Failed to generate content — AI generation failed: API key is invalid." On standalone the dialog just closes and nothing appears, so the feature looks silently broken to anyone developing locally.

Note

This is not an AI Power-Ups bug. The error reporting works where the transport works. Filed separately from #5720, which covers two places where ai-powerups genuinely does stay silent regardless of transport.