fix(brokerkit): consume canonical operator contract

[osolmaz]

Summary

The approvals popover treated valid BrokerKit requests as unavailable because MLClaw's private request schema was missing canonical presentation fields.
This change makes MLClaw consume BrokerKit's published Operator V1 validators directly.
It also makes package, plugin, binary, OpenClaw, and runtime-image version updates come from one checked release configuration.

What Changed

MLClaw now follows the same wire contract as BrokerKit instead of maintaining a second hand-written schema.

• Replaced the local Operator V1 request and error schemas with openclaw-brokerkit/operator-v1.
• Added regression fixtures for target, warnings, plan_hash, and canonical error correlation IDs.
• Updated the pinned plugin to openclaw-brokerkit@0.3.4 and the MLClaw release to 0.4.8.
• Added generated release constants plus checks for package-lock, Docker, dependency, and runtime-image drift.
• Enforced the release metadata check in CI and publishing.
• Rebuilt the committed runtime and CLI bundles.

Testing

The original unavailable popover state was reproduced locally in Chromium, then a harmless BrokerKit request was displayed, approved in the popover, and confirmed active in the real BrokerKit store.

• npm run check
• 318 tests passed; 2 environment-dependent broker binary tests skipped by the default suite.
• 97.5% statement coverage and 93.84% branch coverage.
• Shell launcher resolved and installed the published openclaw-brokerkit@0.3.4.
• Build, package inspection, secret scan, DRY, and Slophammer checks passed.

Risks

The protocol duplication is removed, so future BrokerKit schema changes now require an explicit MLClaw dependency update instead of silently drifting.
The live GoePT deployment and authenticated Hugging Face clone/sandbox acceptance checks remain release-stage validation after merge.