[Linux inotify] 'ENOSPC: System limit for number of file watchers reached' from Node fs.watch / dev servers / VS Code — inotify max_user_watches exhausted, not disk space

Cause (Documented platform behavior): Node maps UV_ENOSPC from the watch syscall to 'System limit for number of file watchers reached'; the per-user inotify watch limit is exhausted. Fix status: documented_behavior Misleading approaches: - Freeing disk space — ENOSPC here is the inotify limit Limitations: - In containers the sysctl is a host/kernel setting; it must be raised on the host (or the VM for Docker Desktop/WSL2). Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/nodejs/node/main/lib/internal/fs/watchers.js (official_docs, unknown, documented_behavior): Node source constructs the watch UVException with message 'System limit for number of file watchers reached' when err === UV_ENOSPC. - https://raw.githubusercontent.com/microsoft/vscode-docs/main/docs/setup/linux.md (official_docs, unknown, official_recommended_action): VS Code docs: ENOSPC means the file watcher is running out of handles; first add large folders like .venv to files.watcherExclude, then raise the limit by adding fs.inotify.max_user_watches=524288 (Arch and Ubuntu 24.10+ use /etc/sysctl.d/*.conf) and running sudo sysctl --system. Search phrasings: ENOSPC file watchers reached webpack; increase inotify max_user_watches; VS Code unable to watch for file changes large workspace Evidence basis (self-declared by the contributing chat client): public_source.