andriyDev 4dc8fb4919 Change the ambiguity_detection test to be more strict. (#23846) ...

# Objective

- Fixes #23843 by preventing these systems from recurring inside Bevy.
- Note this does not fix this for users of Bevy. They would need to
setup their own "strict" checking.

## Solution

- Disable `auto_insert_apply_deferred` in the `ambiguity_detection`
example. Now these stages won't accidentally resolve these ambiguities,
so they will be detected!
- Stop running the app in `ambiguity_detection` and just manually
initialize the schedules.
- We have to do this otherwise the schedules just panic because they
depend on various resource initializations to be executed by commands
(which were previously being applied by the automatically inserted
`apply_deferred`).

### Caveats:

- The ambiguity_detection CI test now won't detect ambiguities in
runtime-added systems.
- This is not a pattern we use today, and I'd encourage us to **delete**
systems instead so that tooling can grab the systems before the app
runs.
- To clarify, this is **not** ambiguity detection in general - just
Bevy's CI test that is affected.

## Testing

- Ran the examples and all the ambiguities have been fixed in previous
PRs.

2026-04-22 16:19:28 +00:00

..

ambiguity_detection.rs

Change the ambiguity_detection test to be more strict. (#23846)

2026-04-22 16:19:28 +00:00