Skip to content

Latest commit

 

History

History
35 lines (25 loc) · 1 KB

contributing.md

File metadata and controls

35 lines (25 loc) · 1 KB

Contributing

Use Development for source setup, local vector service preparation, generated IPC files, and validation commands. This document covers contribution expectations.

Baseline Checks

Before opening a PR:

pnpm check
npm run build

The current unit and integration suites use mocked service contracts. For an end-to-end test with a real vector service, prepare its binary with:

bash scripts/build-daemon.sh

Behavioral Changes

If you change retrieval, compaction, or ranking behavior, add or update the matching validation coverage and avoid weakening checks just to hide a regression.

PR Expectations

  • Keep plugin lifecycle and vector service lifecycle separate.
  • Include focused docs updates for user-visible behavior or config changes.
  • Keep internal design changes reflected in the appropriate design notes.
  • Do not add install-time vector service bootstrap to the npm/OpenClaw package without documenting the security and distribution trade-off.