Summary
QwenPaw/CoPaw closed PR #5612 to isolate plugin market downloads by major version after the 2.0.0 beta exposed compatibility problems. The fix adds compatibility labels, versioned metadata indexes, and CDN release changes so v1.x and v2.x users do not receive incompatible plugin packages.
What changed
The plugin market now filters entries by qwenpaw_compat_labels, sends compatibility labels through the backend search API, publishes separate /metadata/plugins/v1/index.json and /metadata/plugins/v2/index.json indexes, and updates plugin manifests and package versions to avoid stale CDN artifacts.
Why it matters
Plugin markets become a supply-chain and reliability surface once an agent platform has multiple incompatible major versions. Routing downloads by compatibility label reduces broken installs and gives QwenPaw a cleaner path to support v2 without stranding v1 users.
Evidence excerpt
PR #5612 says v1.x and v2.x users could download incompatible plugins after QwenPaw 2.0.0b1; it adds compatibility labels, versioned metadata indexes, and CDN release pipeline updates.