Shared code between chromatrix packages and apps: the config schema (zod) + its resolution (~/.config/chromatrix/config.json overridden by CHROMATRIX_* env) and the access-token primitives. Deliberately lean - zod is the only runtime dependency, because b

chromatrix gateway (NestJS + @silkweave/nestjs): raw-WS CDP mux mounted at the underlying http.Server (outside Nest's pipeline) + silkweave mgmt/MCP Actions (provision/allocate/health/takeover) + the bundled dashboard. Run it with `npx @chromatrix/gateway

Browser-fidelity layer for chromatrix: Chrome launch flags, CDP leak-mitigation policies (Runtime.enable suppression + isolated-world emulation), fingerprint hygiene, and verification probes (Runtime.enable getter-trap, WebGL renderer assertions) run by `

chromatrix CLI - a thin remote client over the gateway's MCP surface (@silkweave/mcp cliProxy). Every @Mcp tool the gateway exposes becomes a command automatically; there is no per-command code here by design.

Domain core for chromatrix: identity registry, session/tab-pool orchestration, single-writer profile locking, health checks, and the orphaned-Chrome-tree reaper. Consumed by apps/gateway. Populated after S1/S3.

CDP client + flat-session multiplexer for chromatrix: one upstream connection to Chrome, N downstream clients, per-client command-id remapping, event routing by sessionId, per-tab ACLs, and a pluggable message-interception layer (the mitigating-mux core).

CIEXYZ-based color engine using Float32Array matrix pooling