ContextLattice v4.0.3: Production Means Production.

ContextLattice already had the right dashboard. v4.0.3 makes sure it ships as one.

The CLI remains the primary interface. The dashboard, HTTP, and MCP remain companion surfaces.

What Changed

The dashboard image now performs a locked Node 24 production build and starts the optimized Next.js server instead of the development server.
Runtime startup uses the bundled Prisma client, performs the required schema synchronization, and never asks npx to fetch packages from the network.
Container health now checks the live /api/public/auth-mode contract, proving both application readiness and runtime mode resolution.
Status probes wait for runtime mode and skip hosted-only billing capability checks in account-free local mode.
Long project and topic paths now wrap inside their rails, trees, and sidecars without causing desktop or mobile horizontal overflow.
The Node runtime audit now rejects dashboard images that regress to development mode, omit a production build/start path, lack the runtime healthcheck, or allow network-fetching npx startup behavior.
Historical paid-release replays now preserve the approved amended source identity through nested artifact checks without moving immutable tags.

The CLI-first agent contract.
Gateway, retrieval, storage, session, runner, and inference semantics.
Public local mode remains account-free; hosted authentication remains opt-in through AUTH_REQUIRED=true.
The public Apache-2.0 and commercial BUSL-1.1 source boundary.
Aggregate Signal remains a controlled activation preview under its existing privacy and utility gates.

Existing v4 installations can update normally. No data migration or new required service is introduced.