ContextLattice v3.15.1 - One Runtime. Zero Drift.

The application, local tooling, containers, and release machinery should not
quietly inhabit different JavaScript eras. v3.15.1 converges every
ContextLattice-owned Node surface on the current Node 24 LTS line and turns
that choice into an executable contract.

What changed

• Pinned local version-manager contracts to Node 24.18.0 and npm 11.16.0.
• Added strict dashboard engines and packageManager requirements plus Node
  24 type definitions.
• Moved the dashboard, MemoryMCP, and custom MCP gateway build paths to Node
  24.18.0 images.
• Rebuilt the stale MCP gateway Dockerfile around the current proxy binary;
  it no longer assumes an Alpine package manager that the upstream image does
  not contain.
• Upgraded every JavaScript GitHub Action to a verified Node 24 major,
  including checkout, setup, artifacts, labeling, attestation, and release
  publication.
• Added a dedicated Node 24 CI gate that performs a clean dashboard install,
  runs the full test suite, and produces a production build.
• Added scripts/node24_runtime_audit.py to reject version drift in package,
  Docker, and workflow surfaces.
• Reviewed and version-pinned every dependency install script surfaced by npm
  11. Future unreviewed or stale approvals now fail closed.

The boundary

• This is a runtime-convergence release, not an application architecture
  rewrite.
• ContextLattice still uses the CLI as its primary agent interface.
• No MCP tool, gateway route, retrieval behavior, entitlement, or memory
  contract was added.
• Third-party services retain their vendor-owned runtimes; the audit covers
  ContextLattice-owned build and execution surfaces.

Verify it

node --version
npm --version
python3 scripts/node24_runtime_audit.py --check-local --pretty

Expected runtime line:

Node v24.18.0
npm 11.16.0

The reproducible baseline and verification ledger are in
docs/evals/v3.15.1-node24-runtime.json.