[aaronphifer]

Summary

• supports VariaQ 0.6.x while retaining schema version 1
• adds non-executing campaign planning and bounded campaign execution
• preserves the VariaQ max-run guard and only passes override when explicitly requested
• adds campaign list/show, analyze-runs, analyze-campaign, and report generation
• preserves report and analysis provenance, source run IDs, null metrics, and mixed status summaries
• constrains report output to a stable configured/project-local root with traversal and symlink protection
• leaves existing version/status/problem/solve/benchmark/compare/runs/reproduce behavior intact
• keeps all campaign orchestration, analysis mathematics, statistics, plotting, and provenance logic in VariaQ
• adds no UI and no physical-QPU path

Local verification

• npm ci — passed
• npm run typecheck — passed
• npm run test:unit — 84 passed, 1 skipped
• npm run test:integration against released VariaQ 0.6.0 — 22 passed, 2 optional CUDA-Q suites skipped
• npm test with the real VariaQ environment — 106 passed, 3 skipped
• npm run sdk:check — passed (Plugin SDK 0.4.104)
• npm run build — passed
• npm pack --dry-run — bb-plugin-variaq-0.5.0.tgz, 12 intended public files
• npm audit --omit=dev — 0 vulnerabilities
• git diff --check — clean

Hosted VariaQ integration is pinned to v0.6.0 and includes bounded campaign plan/run, analyze-campaign, and JSON/CSV/Markdown report smoke coverage. It requires no CUDA-Q, GPU, matplotlib, remote provider, or physical QPU.