chore[notask]: release @qvac/opencode-plugin 0.3.0

[simon-iribarren]

🎯 What problem does this PR solve?

• QVAC-22567 feat[bc]: remove SDK dynamic tools mode (toolsMode) #3380 removed the SDK's dynamic tools mode and, as part of that, stopped the plugin pinning toolsMode: 'static' on the managed serve's model config. That change is unreleased.
• Because the SDK now rejects toolsMode rather than ignoring it, a 0.2.x plugin cannot drive a @qvac/cli 0.12 / @qvac/sdk 0.18 serve. The plugin needs a release whose manifest ties it to the new host.
• Third package in the agent-stack cascade (cli → ai-sdk-provider → opencode-plugin / openclaw-plugin).

📝 How does it solve it?

• plugins/opencode/package.json — version 0.2.0 → 0.3.0
• plugins/opencode/package.json — @qvac/cli ^0.11.0 → ^0.12.0
• plugins/opencode/README.md — Requirements now name CLI ^0.12.0 / SDK 0.18 runtime
• plugins/opencode/changelog/0.3.0/ — CHANGELOG.md, CHANGELOG_LLM.md, breaking.md
• plugins/opencode/CHANGELOG.md — aggregate rebuilt (5 versions)

@qvac/ai-sdk-provider stays at ^0.6.0 — the caret already covers the 0.6.1 peer-range release (#3992), so no floor move is needed.

Minor bump per the 0.x policy: the required @qvac/cli floor crosses a minor, and 0.x carets do not cross minors, so consumers pinned to CLI 0.11 are affected.

On the changelog wording: the generator rendered #3380 under Features using the SDK-side PR title, and produced a breaking.md copied from the SDK's migration example plus that PR's internal release-coordination notes and an Asana link. Both were rewritten to describe the plugin's change. #3380 states outright that the plugin-side edit is behaviour-neutral (static was already the default), so this release is titled chore[notask], not [bc] — the plugin's own surface does not break. breaking.md is kept, scoped to the one thing that genuinely breaks for installers: the plugin and host must now move together.

No third-party dependency changed, so NOTICE is unchanged and was not regenerated.

Release-order note: publish only after @qvac/cli@0.12.0 is live on npm (which itself waits on @qvac/sdk@0.18.0).

🧪 How was it tested?

• Release metadata and README only — the single source change (dropping the toolsMode pin) already merged and was tested in QVAC-22567 feat[bc]: remove SDK dynamic tools mode (toolsMode) #3380.
• prettier --check clean on changelog/0.3.0/**/*.md, CHANGELOG.md, and README.md.
• Verified the AI SDK majors still line up, so this plugin is not blocked: the plugin depends on ai@^7.0.0 and @ai-sdk/openai-compatible@^3.0.0, matching the provider's ai@^7.0 / ^3.0 peers.

[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