ContextLattice v3.3.1

Release date: 2026-04-02

This release packages the full commit train since v3.3.0 and adds explicit public-facing spike-lab guardrails.

Summary

• Public startup defaults remain unchanged: COMPOSE_PROFILES=core,llm,observability.
• spike-lab stays available for advanced operators, but now has explicit one-lane controls:
  • gmake mem-spike-ls
  • gmake mem-spike-up SPIKE_LANE=<lane>
  • gmake mem-spike-down SPIKE_LANE=<lane>
• Benchmark transparency is now called out directly in docs:
  • bench/results/backend_lane_matrix_latest.json
  • bench/results/memory_bank_spike_direct_matrix_latest.json
  • docs/perf_v3_spike_matrix.md

Included commits since v3.3.0

• 8b93104 fix: harden env alias sync and stabilize go-runtime continuation status (#121)
• 90e40f6 sync(public): apply mongo_raw+mindsdb go-native cutover + metadata contract (#122)
• 87f799e feat(gateway-go): make telemetry metrics/retrieval/trading routes go-native (#123)
• aa8836c fix(public): restore gateway-go/dashboard docker build integrity (#124)
• docs/ops: enforce public spike-lab one-lane guardrails + release transparency (this release commit)

Operator notes

• If you do not need benchmarking, do not enable spike-lab.
• If you do need benchmarking, run one spike lane at a time and leave Docker VM RSS guard enabled.
• Runtime behavior for default users is unchanged from v3.3.0.