will.anderson
e60ca8123b
Investigated awareness.el ise_post's local-fallback engram_node_full call as a suspected instance of the score-mangling double-wrap fixed in server.el on 2026-08-01. It is not one. Removing the wrapper produces byte-identical codegen: the compiler treats el_from_float as the boxing intrinsic, so both `el_from_float(0.3)` and a bare `0.3` emit exactly one el_from_float(0.3). The server.el bug was different in kind - there the arguments came from json_get_float(), already boxed as el_val_t, and wrapping those a second time reinterprets the boxed bits as a raw double, fails engram_decode_score's range check, and silently clamps to defaults. Comment only, no behavior change. Recording the negative result at the call site so the sweep criterion is right: look for el_from_float applied to an already-boxed expression, never to a literal. Grepping the call name alone produces false positives, which is what happened here.