tracking: migrate C++ plugins from WasmEdge core (WasmEdge/WasmEdge#3840) #22

Implements the cpp-plugins side of WasmEdge/WasmEdge#3840 (decoupling the C++ plugins from the core repository; vote passed 2024-10-22).

Goal: all 15 C++ plugins build, test, and release from this repository against a stable WasmEdge release (0.17.0 at the time of writing), so plugin maintainers no longer track unreleased WasmEdge master.

Phases

Plugin migration issues

(Pilot: wasmedge_zlib is #25.)

Dependency graph

graph TD
    B["#1 repo bootstrap"]
    F1["#23 import sources"] --> F2["#24 standalone build"]
    F2 --> P0["#25 pilot: wasmedge_zlib"]
    P0 --> M["plugin migrations ×14"]
    P0 --> F4["#26 release pipeline"]
    F4 --> R1["#27 installer integration"]
    M --> R2["#28 remove from core"]
    P0 --> R2
    R1 --> R2

Out of scope for this repo

• The installer change itself lands in WasmEdge/WasmEdge (utils/install_v2.sh, utils/install.py) — coordinated by feat: installer integration: fetch plugin assets from cpp-plugins releases #27.
• Per-plugin removal PRs land in WasmEdge/WasmEdge — coordinated by tracking: remove migrated plugins from WasmEdge core #28.
• Rust-based plugins already live in their own repositories.

🤖 Generated by Claude Fable 5 with Claude Code