perf: guard the complete core benchmark suite

[tiye]

Summary

• add RFC 0109 requiring qbench coverage for every core benchmark workload
• expand release qbench from six to the complete 34-workload core suite
• assert every stable workload name and timing field in the CLI integration test

Validation

• cargo run --locked --quiet --release --bin qbench -- --json --iterations 1 --repeat 3
• make check
• git diff --check

This PR is stacked on PR #50 and should remain unmerged with the existing chain.

[Copilot]

Pull request overview

Expands qbench’s release/CI semantic guard from a small subset to the full core benchmark workload suite, and codifies the requirement via a new RFC so future core benchmarks can’t drift from qbench --json coverage.

Changes:

• Add RFC 0109 requiring 1:1 coverage between cargo bench --bench core workloads and qbench --json built-ins.
• Expand qbench’s built-in WORKLOADS set to the complete 34-workload core suite.
• Strengthen the CLI integration test to assert every stable workload name appears exactly once and that timing/schema fields are present.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
tests/cli_tools.rs	Expands the qbench --json integration assertions to cover all 34 workload names and required fields.
src/bin/qbench.rs	Adds the missing core workloads to qbench so CI/release gating exercises the full suite.
RFCs/0109-qbench-core-suite.md	Defines the coverage and output-contract guardrails for the full core suite in qbench.
RFCs/0000-project-scope.md	Updates the repository’s implemented RFC range and list to include RFC 0109.
README.md	Updates the documented RFC range link to point through RFC 0109.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.