ci: package.json/lockfile mismatch — @vitest/coverage-v8@2.1.9 needs vitest@2.1.9 but package.json wants vitest@^4.1.7

[mizcausevic-dev]

CI fails on npm ci (Node 22 matrix) due to a peer-dependency version mismatch in package.json + package-lock.json.

Surfaced during 2026-05-31 squad triage of the Operator Diagnostics lane. Blocks v1.0-prod hardening on this repo.

Observed (verify step UNKNOWN STEP):

npm error code ERESOLVE
While resolving: @vitest/coverage-v8@2.1.9 / Found: vitest@4.1.7 / peer needs vitest@2.1.9

Suggested fix (Codex lane — package.json + lockfile):

Bump @vitest/coverage-v8 from ^2.1.x to ^4.1.7 in package.json devDependencies to match vitest^4.1.7.

After the fix:

• delete node_modules + package-lock.json
• npm install with npm 11+ to regenerate the lock with Linux optional deps (@emnapi/*, @rolldown/binding-*) baked in (per the existing "Lockfile" doctrine memo)
• commit the regenerated package-lock.json
• CI should go green; I'll resume the v1.0-prod harden once it does

Not blocking — Pages deploy + CNAME + tag can still ship once CI is green. No need to revert any of my squad-lane work.

Additional: missing CNAME file

This is the only Operator-Diagnostics-candidate repo without a CNAME at root. Recommend adding margin.kineticgain.com (one-word noun per the subdomain naming convention).