### Problem/Motivation Running the kernel suite on Drupal 10.6.18 ([#3583074](https://git.drupalcode.org/project/tool/-/work_items/3583074)) leaves four tests red after the PHPUnit 9 mechanics are fixed, and they share one cause: - `TypedInputsValidationTest::testDeclaredMapConstraintsSkipEntityValidation`: validating a map whose `account` property holds `User::create()` runs the user entity's own field constraints (`UserMailUnique` queries the `users` table), which the test exists to rule out. - `TypedInputsValidationTest::testValidatesMapDefinitionConstraints` ("property too short") and `::testValidatesStructureReadingMapConstraints` (two data sets): every property violation is reported twice, once as `(property code) …` with an empty path from the tool's walker and once as `code: …` from core. - `EntityInputTypeCheckTest::testDeclaredConstraintsAreChecked`: a node that satisfies the declared `Bundle` constraint reports one violation from its own fields. `TypedInputsTrait::validateDeclaredConstraints()` validates the declared constraints of a map with `RecursiveContextualValidator::validate($data, $constraint, NULL, FALSE)`: a non-root call with explicit constraints. Core 11's `validateNode()` only recurses into list items and map properties when the call is the root call or no constraints were given: ```php if ( ($is_root_call === TRUE || $constraints_given === FALSE) && ($data instanceof ListInterface || $data instanceof ComplexDataInterface) && !$data->isEmpty() && !($data instanceof EntityAdapter && $constraints_given)) { ``` Core 10.6 has no such gate: it recurses into every non-empty list or complex value, and the recursion validates each property with no constraints given, so an entity property is traversed into its fields. The tool's property-by-property walk in `validateInputValue()` was written against the 11 behavior ("this avoids core's recursive typed-data traversal, which validates entity…"), so on 10 the walker and core both report. ### Proposed resolution Decide one of: 1. Parity on 10: validate declared constraints through a tool-owned contextual validator that applies core 11's gate (`RecursiveValidator` is constructed by `TypedDataManager::getValidator()`, so the tool would build its own with the same `ExecutionContextFactory` and `ConstraintValidatorFactory` and a `RecursiveContextualValidator` subclass whose `validateNode()` carries the gate). Keeps one behavior on both majors; copies about forty lines of core. 2. Stop relying on recursion at all: validate each declared constraint against the typed data without entering `validateNode()` for children, for example by resolving the constraint validator through the factory and running it in a context the tool starts, which is what `validateNode()` does before it recurses. 3. Document the difference and keep the skips. Until then the four tests skip below core 11 with a pointer here, so the Drupal 10 job stays green and the gap stays visible. ### Remaining tasks * [ ] Pick the approach. * [ ] Remove the four `markTestSkipped()` calls added in #3583074. ### AI usage (if applicable) * [x] AI Assisted Issue: This issue was generated with AI assistance, but was reviewed and refined by the creator. * [ ] AI Assisted Code: This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision. * [ ] AI Generated Code: This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human. * [ ] Vibe Coded: This code was generated by an AI and has only been functionally tested.