### Problem/Motivation Block content access classes (AccessGroupAnd, DependentAccessInterface, RefinableDependentAccessInterface, RefinableDependentAccessTrait) moved from Drupal\block_content\Access to Drupal\Core\Access namespace (drupal:11.3). ### Proposed resolution Handled automatically by drupal-rector by configuring the existing upstream rule in the Drupal 12 rule set (no dedicated rule class). ### How this rule was built This rule was produced with an AI-assisted workflow in which every step was verified manually by @bbrala. Its logic started from the matching drupal-digests entry, which was adapted to drupal-rector's conventions — a dedicated rule or an existing upstream rule configured into the Drupal 12 set — and covered with before/after test fixtures. Backward-compatibility was assessed and version-gated: safe rewrites are applied directly, while unsafe ones are wrapped via `DeprecationHelper` or moved to an opt-in breaking set. The rule was then live-tested against a set of contributed modules; where no contrib call site could be found, a static code sample was written in a test module to exercise it. A final automated QA pass covered type-guard, fixture coverage, BC-decision, registration and idempotency checks. ### References - Related issue(s): [#3571874](https://www.drupal.org/i/3571874) ### Work items - Commit(s): [67e20dfe9c](https://github.com/palantirnet/drupal-rector/commit/67e20dfe9cb2) ### 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 rule 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/).*