#110353Skip redundant npm ci in lint suites
Description
Problem
The pre-merge job “grunt scss ts html” runs the suites checkGruntClean,
lintScss, lintTypescript and lintHtml sequentially. Each of these suites starts
with “npm ci”, which by design removes Build/node_modules and reinstalls it from
scratch.
Build/node_modules lives on the bind-mounted core root and therefore persists
between the sequential container runs of one job, so three of the four installs
are pure overhead.
Solution
Guard the “npm ci” of lintScss, lintTypescript and lintHtml so that it only runs
when Build/node_modules is not provisioned yet, following the pattern already
used by the playwright suites.
checkGruntClean runs first and deliberately keeps its unconditional “npm ci”, to
guarantee a pristine, lockfile-exact toolchain before it verifies that the grunt
build produces no diff; the guarded suites then reuse that install. Standalone
invocations still provision node_modules on first use.