Implement direct Gateway-dispatched OpenClaw tool activity

[CompleteDotTech]

Parent

Implements the durable direct-Gateway dispatch path required by #3847. It supersedes the reverted observer-only attempt in #3852.

Problem

The CLI does not expose the Gateway-accepted runId before tool events begin, so an observer cannot safely correlate session-scoped session.tool events to one Cave turn.

Scope

• Make a compatible authenticated Gateway the authoritative OpenClaw chat transport.
• Use the published @openclaw/gateway-client and @openclaw/gateway-protocol packages for protocol constants, validation, device authentication, and capabilities.
• Obtain the accepted dispatch runId, bind chat and tool events to it, and keep the existing CLI route as a fail-closed fallback for unsupported, unpaired, unavailable, or schema-incompatible runtimes.
• Add release-versioned protocol fixtures and a route-level WebSocket-to-SSE/persistence integration test.

Acceptance criteria

• No tool card is emitted unless its authenticated, validated frame matches the exact dispatched run ID.
• Operator scopes and paired-device authentication are negotiated before dispatch; Gateway credentials are never inherited by the CLI fallback child.
• Unknown protocol/schema/capability, malformed frames, replay/gap, disconnect, cancellation, or dispatch failure close the Gateway path and retain safe plain-chat behavior.
• Supported protocol versions are generated from/pinned to official package schemas, with an upgrade matrix and conformance fixtures.
• Route-level tests prove that one dispatched run emits start/update/result cards and that a concurrent run cannot leak cards into it.

[CompleteDotTech]

Implementation is being developed in draft PR #3866. Parent compatibility work: #3847. Reverted predecessor: #3852.

[CompleteDotTech]

This issue is the successor to the safe stop point in #3852. Its implementation lives in draft PR #3866; it must not re-enable live activity until direct Gateway dispatch supplies the accepted run ID.

[CompleteDotTech]

Planning contract was clarified and pushed in cd5b308 / draft PR #3866. This issue remains open until the dispatcher, conformance fixtures, and route-level lifecycle tests are implemented; #3866 no longer claims to close it.

[CompleteDotTech]

Implementation commit 41a7a45 is now on draft PR #3866: it adds official v4 Gateway dispatch, challenge-bound auth, accepted-run correlation, idempotent no-duplicate fallback, cancellation fencing, SSE/persistence projection, and focused coverage. The current official protocol package lacks a published session.tool payload schema, so tool cards remain fail-closed until that versioned contract is available.