nx_jsscope.nx

nx_jsscope.nx -- STATIC SCOPE RESOLUTION over nx_js_parse's AST: does every identifier a script REFERENCES have a declaration in a scope that ENCLOSES the reference? WHY THIS EXISTS. 2026-08-25 every /world page with a cast went black on the WebGL tier and reverted to the CPU renderer, and the reason -- once the reload was made to carry it -- was `ReferenceError: nxHairTick is not defined`: a function DECLARED inside loadNPC, CALLED from drawNPCs at script scope. The page LEXED (nx_jsbalance passed it), the wasm PAINTED, every gate was green. Nothing in the estate asks the one question a browser asks first: can this name be seen from here? This organ asks it, statically, over the incumbent parser -- one AST, no second front-end. THE RULE, STATED ONCE. A reference resolves if its name is declared in the SAME function scope or any ENCLOSING one (function declarations and `var` hoist to their function; params, class names, catch params and for-targets bind where they appear). A name declared ONLY in a function that does NOT enclose the reference is the exact defect above and is reported as OUT-OF-SCOPE, with the declaring scope named -- because "undefined" sends a reader to grep for a typo, while "declared in loadNPC" sends them to the real fix. A name declared nowhere is UNRESOLVED and is checked against a globals CONF (knowledge/js_globals.conf, one name per line): browser and language globals are DATA the page may lean on, never a list compiled into this organ. ⚠ DECLARED IMPRECISION, because a checker whose blind spots are unstated gets trusted as exact. 1. `let`/`const` are BLOCK-scoped in JS; this pass binds them to their FUNCTION. A let in one block referenced from a sibling block would be a real ReferenceError this organ does NOT see. That is the conservative direction -- it misses an error class, it never invents one. 2. Template-literal interiors (`${expr}`) are not parsed by nx_js_parse (the token is opaque), so references inside them are invisible here. 3. `with` statements and `eval` are not modelled; a page that used them could not be judged. 4. Property names (a.b), object keys, labels and destructuring keys are NOT references and are never counted, by construction of the walk. license_tier: ORIGINAL No hw writes (Rule 26).