Less variable lazy-loading limits across nested scopes

Less employs a lazy-loading evaluation strategy that permits variables to be referenced before their formal definition in certain contexts. This behavior is typically reliable for global variables defined later in the same compilation pass.

Complexity arises when combining lazy-loading with hierarchical scoping. When a variable is used within a nested selector block before it is defined globally, the compiler must determine if the variable should be resolved as a lazy global or if it should trigger a scope-related error due to the local context.

Given these scoping rules, what are the specific limits of lazy-loading when a variable is referenced inside a nested rule but defined at the root level after that rule? Does the compiler prioritize the local scope check over the lazy-loading lookup?