fix(tests): align quantum integration test with whitelisted autorun jobs

[cursor]

Summary

Hourly repo health automation failed pre-commit because test_run_autorun_job_reads_status_for_list_and_dict_shapes used a non-whitelisted job name (another). The quantum integration bridge only accepts baseline, benchmark, nightly, and smoke.

Changes

• Update the list/dict status-shape test to use the whitelisted smoke job name while still exercising _find_job_status normalization for both payload shapes.

Verification

• 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
  • repair_data_out_status: PASS
  • pre_commit_check: PASS (2725 tests)
  • integration_contract_gate: PASS
  • run_repo_agents: PASS (status-freshness ok; docstring/marker warnings expected)

  

Summary by Sourcery

Bug Fixes:

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

---

Note

Low Risk
Generated status JSON only; no runtime, auth, or business-logic code changes in the diff.

Overview
This diff only updates checked-in data_out status and CI artifact JSON—no source or test files appear in the patch.

It bumps timestamps and run IDs across orchestration outputs (autonomous_agent, autotrain, ci_orchestrator, evaluation_autorun, master_orchestrator, quantum_autorun, repo_health_automation) to reflect a run around 2026-06-20T19:02.

data_out/integration_smoke/status.json also changes the recorded chat_cli_local_once smoke step: longer duration and updated assistant text for the local fallback provider message.

data_out/repo_health_automation/status.json captures a successful health cycle (repair status, pre-commit with 2725 tests passed, integration contract gate, repo agents) with matching step timing tweaks.

^{Reviewed by Cursor Bugbot for commit fbc7374. Bugbot is set up for automated code reviews on this repo. Configure here.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Align quantum integration autorun status-shape test with the whitelisted job names by switching from a generic job name to the allowed smoke job, and updating associated expectations and status fixtures.

File-Level Changes

Change	Details	Files
Update quantum integration autorun status-shape test to use the whitelisted smoke job name instead of another.	Change list-shaped jobs payload to use a single smoke job with preset heart and status completed. Change dict-shaped jobs payload to use a smoke key and job entry with preset heart and status completed. Invoke run_autorun_job with job name smoke and update assertions to expect smoke in job_name and status.name while still validating preset normalization.	tests/test_quantum_integration.py
Refresh repo health/status fixtures to reflect the passing health automation run after aligning the test with whitelisted autorun jobs.	Update autonomous_agent status JSON to reflect current status produced by the health automation. Update autotrain, ci_orchestrator, evaluation_autorun, integration_smoke, master_orchestrator, quantum_autorun, and repo_health_automation status JSON fixtures to the latest outputs.	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.

[github-actions]

🟡 Coverage — 8c6113c

Metric	Value
Total coverage	65.6%
▲ vs main	+0.3%
Minimum threshold	60%

Updated on every push · 2026-06-21

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_36ee82fc-c823-4b72-8ed1-af25f9931d20)