newos4/modules/test/test-loop-policy.js, branch mainnewOS4 - the browser terminal that runs WebX11 user spaceshttps://newos.webx11.duckdns.org/newos4/atom?h=main2026-10-27T15:07:35+00:00fix(newos4): the loop guard reads the config it documents2026-10-27T15:07:35+00:00Agandoroduccomm@gmail.com2026-10-27T15:07:35+00:00urn:sha1:2e9401a5587b0a45daaf0af116bb7da573b0988d
MAINT-004. The guard read warnAt/blockAt/hardStopAt while one config path wrote `threshold`, and
`enabled` was never consulted anywhere — writing {"enabled": false} into webx11_ai_config changed
nothing at all. One resolver, _loopPolicy(), now normalises both spellings, guarantees
warnAt <= blockAt < hardStopAt, and both the block and the warning are gated on enabled.
Live on v4.6.110 (_loopPolicy called in the page): defaults {warn 3, block 6, hardstop 9};
{threshold: 4} -> {warn 2, block 4, hardstop 7}; {enabled: false, threshold: 3} -> enabled false.
test-loop-policy.js: 17 asserts, RED on HEAD ("_loopPolicy is not a function"), suite 16/16.