will.anderson
6838e5cbff
Same defect as the release runtime: \uXXXX was skipped and a literal '?' emitted, destroying every non-ASCII character in JSON entering the runtime. Two copies of one parser bug is how this class of fault survives a fix, so it lands in both. NOTE: this file also carries pre-existing uncommitted work from 2026-07-15/16 that this commit preserves rather than authors - loopback bind hardening (EL_HTTP_BIND_HOST) and per-install API-key auth (EL_HTTP_AUTH_KEY) for the shipped desktop build, plus goal-bias and node-json changes. It had been sitting in the working tree for three weeks. Committing it because uncommitted work is work that does not survive, which is the same durability lesson as yesterday's Hebbian write-back finding. It needs review on its own terms - see the backlog item for reconciling the two runtime copies.