iamtoruk b99744bf93 fix(parser): gate parse workers on available memory, not free memory ... os.freemem() reports free pages on macOS, not available memory: on an idle 128 GB machine it reads a few hundred MB, so the 2 GB gate switched the worker pool on and off between runs on the platform the desktop app ships to. The gate and the budget now use process.availableMemory() (cgroup/rlimit-aware in a container), falling back to os.totalmem(): serial under 4 GB available, budget min(0.25 * available, 2 GB). An 8 GB box earns 8 threads, a 4 GB box none. The verbose line now carries every decision input — cores, available GB, pending files and bytes — on both the gate and the go path, so one support log explains itself.		2026-08-17 01:23:42 -07:00
..
design	Scope the root test script to tests/ so npm test runs from a clean install	2026-08-09 10:19:58 -05:00
providers	fix(parser): flatten already-sliced previews and memoize canonical path walks	2026-08-16 01:49:10 -07:00
sync	fix(sync): close credential-leak paths; session retraction; span/key/CLI hardening	2026-08-02 12:56:59 +00:00
architecture.md	fix(parser): gate parse workers on available memory, not free memory	2026-08-17 01:23:42 -07:00