Gaming locks normalization¶
85-gaming-locks.php is a compatibility facade. The active gaming lock implementation lives under includes/pipeline/norm/products/gaming/locks/.
Module ownership¶
10-core-routing.phpowns the ordered generic gaming classification pass: educational toys, video games, simulation, consoles, controllers, and console accessories.20-residual-polish.phpowns cross-product false-positive corrections historically executed immediately after core gaming routing.30-final-polish.phpowns late console/accessory coherence, peripheral correction, and Switch 2 residual fixes.90-compose.phpowns the publicccx_norm_apply_gaming_global_ux_lock_v1()entrypoint and preserves the historical order of those three stages.
Compatibility contract¶
The public function name and runtime call position are unchanged. This refactor is structural only: regexes, SQL targets, category/vertical assignments, feed/run scoping, and execution order remain unchanged.
The cross-product corrections in 20-residual-polish.php and 30-final-polish.php remain there deliberately. Moving them to other product domains would be a behavioral/timing refactor and must be reviewed separately.
Change policy¶
Future changes to gaming classification keywords, console/accessory precedence, cross-product correction targets, or stage ordering must be treated as behavioral changes and covered by dedicated runtime tests.