Every end-to-end asset-pipeline test — the M2, WMO, BLP and ADT loaders, the minimap's
`load_with_settings` path and the Ironforge group grid — panicked with "Cannot allocate an
Asset Handle of type 'bevy_shader::shader::Shader' because the asset type has not been
initialized". `register_shaders`'s `load_shader_library!` calls allocate a `Handle<Shader>`,
and on Bevy 0.18 it is the render plugins that initialise that type; a headless app has
none, so all six went red at once on the upgrade.
They are the only tests that exercise the loaders every zone load depends on, and the gate
could not see it: each one is data-gated, so it skips without the install, and the
no-install gate is the one that runs everywhere. Found by running the workspace suite with
the install mounted — 44 red there against 0 on the gate.
Initialised here when nothing else has, and **guarded**: `init_asset` *inserts*
`Assets<Shader>`, so calling it unconditionally in the real app would drop every shader the
render plugins had already loaded.
benilla-assets: 109 passed, 0 failed (was 103 and 6). Full chain green.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SgstFWtn1RxEJ5kVrpgYwn
gromandClaude Opus 5
2a65266837