### Problem/Motivation Refactor the analyze-job and testset run into two sequential halves (analyze-job-1 and analyze-job-2) to fit CI resource limits and job timeout constraints, sequencing via a dedicated stage instead of needs: to avoid the needs:-cap-of-50. ### References - Related issue(s): [#3577028](https://www.drupal.org/i/3577028) ### Work items - Commit(s): [47132251c0](https://git.drupalcode.org/project/project_analysis/-/commit/47132251c0a6), [40d78a71dd](https://git.drupalcode.org/project/project_analysis/-/commit/40d78a71ddf5), [5afa3faf52](https://git.drupalcode.org/project/project_analysis/-/commit/5afa3faf52af), [a7bf93ac54](https://git.drupalcode.org/project/project_analysis/-/commit/a7bf93ac5478), [e1dec2f298](https://git.drupalcode.org/project/project_analysis/-/commit/e1dec2f2986c) ### Credit - Implemented by: @bbrala --- *Filed retroactively as part of the Drupal 12 rector coverage effort. Closed as fixed; credit to be applied to the contributors listed above.* *AI was used extensively to build this work and to file this issue. See [Dries Buytaert: AI-generated Rector rules for Drupal](https://dri.es/ai-generated-rector-rules-for-drupal) and [Björn Brala: Drupal Rector rules are config, not code. Mostly.](https://www.linkedin.com/pulse/drupal-rector-rules-config-code-mostly-bj%C3%B6rn-brala-vfpwe/).*