# npm treats this folder as a project of its own and would resolve it from the registry,
# past pnpm-workspace.yaml's overrides and release-age gate. engines.npm in package.json is
# no valid range, and engine-strict turns that into a refusal for every command that builds
# a dependency tree here (install, ci, update, dedupe, uninstall, link, --package-lock-only,
# --ignore-scripts, --force). npx, npm exec and npm run do not check it. pnpm ignores both.
# This root file also covers every checkout folder without a package.json (agent/, tools/,
# Docker's /opt/hermes): there npx refuses, not warns, when the package or any non-optional
# dependency it installs declares engines this Node or npm does not satisfy.
engine-strict=true
