Component should be removed if any of its required components is removed

[beicause]

Bevy version and features

main

What you did

Insert Bloom, then in other system remove Hdr. For example change to this in bloom_3d example and press space:

            if keycode.just_pressed(KeyCode::Space) {
                commands.entity(entity).remove::<Hdr>();
            }

What went wrong

wgpu validation error:

2026-03-17T01:57:17.882899Z ERROR queue_submit{count=8}: bevy_render::error_handler: Caught rendering error: Validation Error

Caused by:
  In Queue::submit
    In a set_pipeline command
      Render pipeline targets are incompatible with render pass
        Incompatible color attachments at indices [0]: the RenderPass uses textures with formats [Some(Rgba8UnormSrgb)] but the RenderPipeline with 'bloom_upsampling_pipeline' label uses attachments with formats [Some(Rgba16Float)]

Additional information

transmission example has this behavior (#23142).

[alice-i-cecile]

We've discussed this a bit before: I feel that we should split apart required components between true "required" (this issue), and "included" (the current behavior). Different uses want different behavior here.

[beicause]

Well, it doesn't necessarily have to remove the component via a required component.

The key point of #23142 seems to be that once ExtractComponent::QueryFilter is removed, the extracted component cannot be automatically removed (in #23334). Not sure how it should be resolved. Removing QueryFilter and relying on required components might be one approach in my quick thought.

[Arrekin]

Would be nice to have both. requires()(maybe renamed to something like enforces()/must_have() to not break compatibility) and includes() having a temporary requires() alias with a deprecation notice.
Naming is not that important, but I have use cases for both behaviours

• includes() (current) for auto-spawning related components and ensuring that some value exists at the beginning but not worrying that removing something later creates cascades
• must_have() for when the leading component has a bunch of helpers, so when removing the main component, I don't have to write observers for cascade removals(right now I usually even move it to a separate entity so I can just despawn all of them together)