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

[cursor]

Summary

The hourly repo health automation cycle failed because tests/test_quantum_integration.py used a non-whitelisted autorun job name (another). run_autorun_job rejects unknown names before status lookup, so the parametrized list/dict shape tests never reached _find_job_status. This PR restores the whitelisted smoke job name and refreshes data_out status timestamps from the successful follow-up cycle.

Changes

• Update quantum integration test fixtures to use the whitelisted smoke job name instead of another
• Refresh tracked data_out/**/status.json artifacts from the 2026-06-20 22:04 UTC health run

Testing

• .venv/bin/python -m pytest tests/test_quantum_integration.py -q — 2 passed
• 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

Restore the quantum integration autorun test to use a whitelisted smoke job and refresh recorded repo health status artifacts.

Bug Fixes:

• Fix quantum integration test to call the whitelisted smoke autorun job so status lookup is exercised correctly.

Tests:

• Update quantum integration test fixtures and expectations to align with the smoke autorun job name.

Chores:

• Refresh data_out status artifacts from the latest successful repo health automation run.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the quantum integration test to use the whitelisted smoke autorun job so that status lookup paths are exercised, and refreshes repo-health data_out status artifacts from the latest successful automation run.

File-Level Changes

Change	Details	Files
Align quantum integration test job name with whitelisted autorun job and ensure status lookup paths are exercised for list/dict payloads.	Change parametrized job payloads from job name another to smoke in both list- and dict-shaped fixtures Update expectations in test_run_autorun_job_reads_status_for_list_and_dict_shapes to assert the smoke job name in the returned result Keep stubbed subprocess behavior but ensure run_autorun_job now passes the whitelist check and reaches status lookup logic	tests/test_quantum_integration.py
Refresh repo health automation status artifacts to reflect the latest successful run.	Overwrite data_out/**/status.json and related status artifacts with outputs from the 2026-06-20 22:04 UTC health run Ensure refreshed artifacts are consistent across autonomous agent, autotrain, evaluation, integration smoke, quantum autorun, and orchestrator components	data_out/autonomous_agent/status.json data_out/autotrain/status.json data_out/ci_orchestrator/ci_results.json data_out/evaluation_autorun/status.json data_out/integration_smoke/status.json data_out/master_orchestrator/status.json data_out/quantum_autorun/status.json data_out/repo_health_automation/status.json

---

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.

[bryan-roe-bot]

Semgrep identified an issue in your code:
Possibly found usage of AI: OpenAI

To resolve this comment:

🔧 No guidance has been designated for this issue. Fix according to your organization's approved methods.

💬 Ignore this finding

Reply with Semgrep commands to ignore this finding.

• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons

Alternatively, triage in Semgrep AppSec Platform to ignore the finding created by detect-generic-ai-oai.

_{You can view more details about this finding in the Semgrep AppSec Platform.}

[github-actions]

🟡 Coverage — 84d22e1

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

Updated on every push · 2026-06-20