## Problem Follow-up to: #3586294+s Parent: #3586310+s _**This issue should be verified prior to working on it to make sure it is valid.**_ This one should be fixed in: #3586218+s `AiContextItemStorage` skips validation entirely for syncing entities (`!$entity->isSyncing()`). The bypass exists so update 10011 completes on sites already over the global cap, but it also disables the structural checks in `AiContextItemValidator::validateItem()` — self-parent, two-level nesting, missing `subcontext_type`. Migrations and `default_content` imports run with syncing TRUE, so invalid hierarchies can now persist with nothing to repair them later. ## Proposed resolution Always run validation, but for syncing saves filter out only the global-cap violation (the validator already has a distinct violation path for `context_scope.global`). Add a kernel test that a syncing save with a structural violation still throws. ## AI usage - [x] AI assisted issue