Skip to content

v3.7.0 — Template Validation + Memory Deployment Alignment

Choose a tag to compare

View all tags
@iPythoning iPythoning released this 07 Jun 10:23
v3.7.0
913e2a9

Summary

v3.7.0 turns the template into a more verifiable release artifact: new users and contributors can run npm test locally before touching a server, and the default deployment path now reports ChromaDB memory status explicitly.

Added

  • npm test / npm run validate entrypoint for release and contributor smoke tests.
  • scripts/validate-template.sh covering required template files, shell syntax, product KB JSON, proforma invoice generation, local Chroma memory store/search, and generated OpenClaw config.

Fixed

  • Fixed skills/delivery-queue/deliver.sh bash syntax for empty queue glob handling.
  • Moved chromadb out of the static core skill profile and behind CHROMADB_ENABLED, with the default set to true to match the 4-layer memory promise.
  • Added deploy summary output for ChromaDB memory state.
  • Updated EN/ZH README metadata for Template v3.7.0, 14 pipeline checks, and the 4-layer anti-amnesia model.
  • Corrected multilingual README b2b_trade skill count from 28 to the actual 41 skills.

Verified

  • npm test
  • bash deploy/deploy.sh validation-client --dry-run with generated validation config
  • git diff --check

Next Evolution Ideas

  • Add GitHub Actions CI to run npm test on every PR.
  • Add a deploy doctor command that validates remote OpenClaw, channel, memory, and dashboard health after deployment.
  • Make non-root deployments first-class by parameterizing the remote OpenClaw home path instead of assuming /root/.openclaw.
  • Add richer industry packs with validated product KB, first-touch sequences, and lead-discovery query presets.
Assets 2
Loading