will.anderson
bc5e14a3e1
Today's review found the JSON parser had been replacing every \uXXXX escape with a literal '?' for at least two months: 3,119 of 4,081 non-telemetry nodes damaged, including the self traversal root and all 13 values nodes. The parser is fixed in el_runtime.c. This is the part that keeps it fixed. Every gauge on this heartbeat answers whether the machinery is running - WM occupancy, Hebbian potentiation, embedding coverage, sync age, breaker state. None answered whether the text the machinery carries is intact, which is why two months of silent corruption read as a perfectly healthy system. Adds txt_damaged: nodes created this process whose content carries the character-loss signature. Flat 0 is healthy; any climb means a write path is mangling text again. The full store census lives at GET /api/text-health, which is too expensive for a 60s beat. A gauge that exists but is not plumbed into the beat is not observability - act_stats fields have to be extracted by name here or they are invisible.