When modules register using a legacy identifier as their `parent` or
`position` reference (e.g. `'parent' => 'web'` instead of the current
`'parent' => 'content'`), the backend module cache warmer silently
stores those unadapted references.
The normal (non-warmed) load path in `ServiceProvider::getModuleRegistry`
calls `ModuleFactory::adaptAliasMappingFromModuleConfiguration()` before
writing to cache, which rewrites any legacy alias references to their
real module identifiers. The `getBackendModulesWarmer` closure that runs
during `cache:warmup --group system` was missing this call, so the alias
adaptation was never applied to the cached data.
On subsequent requests the cache is hit immediately, the adaptation step
is skipped entirely (the early-return guard `if ($modulesFromPackages ===
false)` is never entered), and `ModuleRegistry::applyHierarchy()` matches
submodules by comparing `getParentIdentifier()` against real identifiers.
A module whose parent is still the alias string (e.g. `'web'`) is never
attached to the resolved parent module (`'content'`), so it disappears
from the backend module menu after every cache warmup.
The issue exists since the alias feature was introduced in 2022
(commit 12568884a5b) but only became visible in practice once extensions
that ship TYPO3 14-compatible releases still use legacy identifiers while
recommending `cache:warmup` as part of deployment.
The fix mirrors what `getModuleRegistry` already does: call
`adaptAliasMappingFromModuleConfiguration()` inside the warmer closure
before persisting the result, ensuring both code paths produce identical
cache content.