Author SHA1 Message Date
sneak d513d1c060 RULES.md: DEBUG mode also enables debug logging and the screen name (closes #761)
check / check (push) Successful in 7m14s
e2e / e2e-chrome (push) Successful in 14m45s
e2e / e2e-firefox (push) Successful in 2m24s
The DEBUG Mode line now lists what a debug build does: the red banner
naming the current screen, debug-level logging, and the hardcoded test
recovery phrase. Wording as approved on the issue.

Model: opus-5-5
2026-11-13 18:43:49 +00:00
clawbot 3a8b309d7e test: replace jest workers past 200 MB so they exit in time (closes #766)
check / check (push) Successful in 6m7s
e2e / e2e-chrome (push) Successful in 14m38s
e2e / e2e-firefox (push) Failing after 14m19s
On a starved CPU, jest force-stopped worker processes that could not exit
within the 500 ms it allows, and script/lib/jest.js failed the run although
every test passed. No test leaks a handle; exit time grows with what a
worker holds, 380 to 970 MB at the end of the run.

workerIdleMemoryLimit in package.json replaces a worker whose heap is over
200 MB after a test file with a fresh one.

tests/jestRunner.test.js runs script/lib/jest.js on a fixture that leaves
an interval running and expects the force-stop to fail the run.

Model: opus-5-5
2026-11-11 09:37:12 +01:00
+2 -1
View File
@@ -75,7 +75,8 @@ contradicts either, the originals govern.
## DEBUG Mode ## DEBUG Mode
- [ ] DEBUG mode only enables: red banner + hardcoded test mnemonic - [ ] DEBUG mode only enables: red banner naming the current screen, debug-level
logging, and the hardcoded test recovery phrase
- [ ] No `if (DEBUG)` branches that skip functionality or bypass security - [ ] No `if (DEBUG)` branches that skip functionality or bypass security
- [ ] New DEBUG conditionals require explicit project owner approval - [ ] New DEBUG conditionals require explicit project owner approval