[Enhancement] Admin plane: Policy-disabled feature code retained: AdminDoorGameController + door-games admin routes (door_games is POLICY_DISABLED)

Area: Admin plane (audit p12) · Surface: GET/POST /admin/door-games* · Dimension: dead-code · Severity: enhancement

Per the audit rules, door_games is INTENTIONALLY off for every tenant (POLICY_DISABLED), so this is a removal candidate (policy-disabled), NOT an orphaned bug. The admin controller, its routes, and the member-facing DoorGameController are live code paths backing a feature that policy guarantees will never auto-enable. Same class applies to AdminOnelinerController (one_liners, FeatureCatalog.php:80) and AdminEditorialController (editorial_series, FeatureCatalog.php:74).

Evidence

door_games is in the intentional never-enable list: platform-admin/src/Domain/FeatureCatalog.php:67 `'door_games',` (POLICY_DISABLED) and also retro-games-group default=>false at line 158. The admin surface remains fully wired: routes.php:1994-1996 register GET /door-games → AdminDoorGameController@index, POST /door-games/{id}/toggle, POST /door-games/{id}/edit, plus the member-facing DoorGameController routes at 552 and 894. The controller file platform/src/Controllers/AdminDoorGameController.php exists.

Suggested fix. If the POLICY_DISABLED retro/door/oneliner/editorial features are never coming back, schedule removal of their admin controllers, routes, and templates to shrink the codebase. If they may be revived per-tenant in future, leave as-is — they are correctly gated by policy and are not bugs.

Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.