nx_input_abstract_part.nx

nx_input_abstract_part.nx -- RENAMED FROM nx_input_abstract.nx 2026-07-31 (lib-reconcile). PERMANENT FIX for a two-libraries-one-name collision. runtime/nx_input_abstract.nx is a DIFFERENT program: the F1102 game-platform input CORE, whose API is ia_init(p) / ia_bind(p, code, act). THIS file is the gamebench capability-43 composable PART, whose API is ia_init(s, nact) and ia_bind(s, dev, act, raw) -- same names, INCOMPATIBLE arities. nx_cc binds an import to the IMPORTER'S OWN DIRECTORY FIRST, so which API a caller got depended on WHICH DIRECTORY IT SAT IN, and moving a file between directories silently swapped its input API. The rename removes the ambiguity by construction: one name now denotes one program corpus-wide. WHY THIS PART EXISTS (measured, not guessed): nx_gamebench 2026-07-25 ranked platform reach and found platform-desktop-native blocking 21 of 22 reference titles, vr-runtime a GAP for 4, and mobile only PARTIAL -- while EVERY game in the ecosystem wired its own controls. One loop per platform is how a codebase forks into four. This part is the single place a raw device code becomes a SEMANTIC ACTION, so the game loop above it never learns which device the player used. THE CONTRACT (each clause is a gate tooth): - DEVICE-INDEPENDENCE BY CONSTRUCTION: the same semantic action sequence delivered from keyboard, gamepad, touch or a VR controller drives IDENTICAL downstream state. The game cannot tell them apart because it never sees a device -- it sees actions. This is the flagship property. - NO DEAD ACTION: an action reachable on one device but not another is a platform that cannot play. ia_coverage MEASURES this per device; the gate requires 1000 permil on every bound device. - UNAMBIGUOUS BINDINGS: binding a second action to a (device, raw-code) already in use is REFUSED (IA_E_DUP) with state bit-identical. Ambiguous input is a bug you cannot debug later. - AN UNBOUND CODE PRODUCES NOTHING: a stray device code can never fabricate an action. - DETERMINISTIC REPLAY: the action trace replays to the same actions and the same checksum, and the serializable span rides nx_gamesave like every other certified part (rpgstats T8 / entity T9). Bindings are DATA, not code: a game declares its own action set and its own per-device codes, so a new platform is a binding table, never a fork of the loop. LIB, no main (ecosystem convention, cf. nx_swgpu.nx / nx_gamehud.nx). license_tier: ORIGINAL