fix(tests): use whitelisted smoke job in quantum integration test

[cursor]

Summary

Hourly repo health automation failed pre-commit validation because test_run_autorun_job_reads_status_for_list_and_dict_shapes called run_autorun_job("another"), which is rejected by the autorun job whitelist. Updated the test to use the allowed smoke job name so status lookup coverage matches production validation.

Changes

• Replace non-whitelisted job name another with smoke in quantum integration autorun status lookup parametrized test
• Update assertions for job_name and status name fields accordingly

Testing

• pytest tests/test_quantum_integration.py — 2 passed
• Full health cycle: PYTHON_BIN=.venv/bin/python .venv/bin/python scripts/repo_health_automation.py --once --repair-status --refresh-stale-status --run-agents --continue-on-fail — all steps passed (2725 unit tests, integration contract gate, repo agents)

  

Summary by Sourcery

Tests:

• Update quantum integration autorun status test fixtures and expectations to use the whitelisted smoke job instead of a non-allowed job name.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates a quantum integration test to use a whitelist-approved autorun job name (smoke) and aligns all test fixtures and assertions with the new job identifier so that repo health automation and production validation remain consistent.

File-Level Changes

Change	Details	Files
Align quantum integration autorun status test with whitelisted smoke job name	Update parametrized job payloads to use smoke as the job name key in both list and dict shapes Change the autorun invocation to call run_autorun_job("smoke", dry_run=True) instead of the non-whitelisted job Adjust assertions to expect job_name and status name fields to match smoke	tests/test_quantum_integration.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

🟡 Coverage — e65bc26

Metric	Value
Total coverage	65.2%
→ vs main	0.0%
Minimum threshold	60%

Updated on every push · 2026-06-20