chore[skiplog|notask]: backmerge release-openclaw-plugin-0.2.1 — version bump, manifest, cli dep floor, changelog

[simon-iribarren]

🎯 What problem does this PR solve?

• Lands the release metadata for @qvac/openclaw-plugin@0.2.1 on main, per gitflow.md "Keep main aligned", so future development and the next changelog base see the shipped version.
• Without it, main keeps the plugin at 0.2.0 with a @qvac/cli floor of ^0.11.0 that no longer matches the host its launcher starts.

📝 How does it solve it?

Cherry-picks (-x) the single release commit from release-openclaw-plugin-0.2.1. No functional changes; tagged [skiplog] so it does not appear in future changelogs.

• plugins/openclaw/package.json — version 0.2.0 → 0.2.1, @qvac/cli ^0.11.0 → ^0.12.0
• plugins/openclaw/openclaw.plugin.json — manifest version 0.2.0 → 0.2.1
• plugins/openclaw/changelog/0.2.1/ — CHANGELOG.md, CHANGELOG_LLM.md
• plugins/openclaw/CHANGELOG.md — aggregate rebuilt

Companion release PR: #3996

🧪 How was it tested?

• A straight cherry-pick is correct here rather than a hand-crafted backmerge: release-openclaw-plugin-0.2.1 was cut from the current main tip in this same session, so there is no dependency divergence between the release branch and main to regress. @qvac/ai-sdk-provider is untouched at ^0.6.0, and the @qvac/cli floor moves forward to match the CLI 0.12 cut, so no dependency goes backwards.
• git diff --stat upstream/main..HEAD shows only the five release-metadata files above, with both version fields (package.json and openclaw.plugin.json) landing at 0.2.1.
• Cherry-pick applied with no conflicts.

[github-actions]

License compliance — findings detected (warn-only)

Critical: 0 · High: 1 · Medium: 0

Dependency	License	Scope	Severity	Outcome
@qvac/cli@^0.12.0	(none detected)	runtime	High	blocks

How to resolve a blocking finding:

• Remove or replace the disallowed dependency, or
• If the license is genuinely acceptable, run the compliance SKILL and record the decision in .github/license-allowlist.yml (CODEOWNERS-reviewed), or
• For a one-off, a maintainer can apply the license-override label (High findings only; Critical cannot be overridden).

Warn-only (shadow) mode — this check does not block merges yet.

Updated automatically by the canonical license compliance workflow.

NOTICE presence (advisory)

Missing NOTICE (advisory, does not block):

• ./.github/actions/release-merge-guard
• ./docs/website
• ./packages/ggml-coload-smoke
• ./packages/fabric/test/integration
• ./packages/inference-addon-cpp/mobile
• ./packages/sdk/e2e
• ./packages/llm-llamacpp/benchmarks/performance
• ./packages/llm-llamacpp/benchmarks/server
• ./packages/vla-ggml/sim/server
• ./packages/embed-llamacpp/benchmarks/performance
• ./packages/embed-llamacpp/benchmarks/server
• ./packages/asr-ggml/benchmarks/server