Claude 233fc73430 Let the console keep its recovery hostnames without breaking route caching ... Registering the console once per accepted hostname reused one set of route names, and Laravel refuses to serialise two routes under the same name — so `artisan optimize` failed on the live server the moment the separation was switched on, mid-deploy. Only the canonical registration carries the `admin.` names now; the alternates answer under `admin.viaN.*`. They exist to be MATCHED — they are the addresses someone locked out reaches for — never to have URLs generated for them, so route() keeps producing the canonical hostname. That renaming then broke every exact route-name check, which is how the console navigation decides what is active: reached through a recovery address, nothing in the sidebar was marked, exactly when something is already going wrong. The check goes through AdminArea now and matches either form. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-07-27 06:20:44 +02:00
..
Feature	Let the console keep its recovery hostnames without breaking route caching	2026-07-27 06:20:44 +02:00
Support/Steps	feat(engine-b): CustomerStep base + shared resource trait + config	2026-07-25 11:39:56 +02:00
Unit	feat(engine): orchestrator core (state machine + tick + lock)	2026-07-25 09:54:52 +02:00
Pest.php	fix(security): match ADMIN_HOSTS case-insensitively; share test helpers	2026-07-25 20:56:26 +02:00
TestCase.php	test: do not reach for Redis from the provisioning queue	2026-07-26 02:20:46 +02:00