Repository navigation
v1.9 — The residue test is one command
scripts/residueruns the residue test (docs/testing.md, Resource hygiene): it measures processes
and available memory, runs./scripts/checktwice (--fastfor the fast profile), and names
every survivor with its command line; memory over the tolerance (ANEW_RESIDUE_MB, 512 MB) is
residue too. A process only counts if it is still alive at a second look. Unix-likes viaps,
Windows (Git Bash) via PowerShell/CIM. A red check aborts it: the test needs a green check.docs/testing.md,prompts/bootstrap.mdandworkflows/bootstrap.mdname the command, for both
profiles;docs/testing.mdadds: rerun it wheneverscripts/check.confchanges.scripts/selftestcovers it (usage, red check,--fast, a leaked process named, a waited-for
child not reported). Its assertions look for the scenario's own marker, so a busy machine cannot
make them flaky.
Upgrading
Copy scripts/residue (keep it executable) and scripts/selftest, then run ./scripts/residue and
./scripts/residue --fast against your scripts/check.conf.