Thank you for contributing.
- Open an issue describing the problem or proposal (when relevant).
- Align small scope and objective.
- Avoid mixing large refactors with feature/bugfix in the same PR.
- Fork + dedicated branch.
- (Optional) Install pre-commit for secret scanning:
pip install pre-commit && pre-commit install(gitleaks hook in.pre-commit-config.yaml). - Run locally:
go test ./pkg/... ./services/...go vet ./...- In
sdk/ts:npm run build && npm test
- Update documentation when public behavior changes.
- Send PR with context of “why” the change.
Include in the PR:
- problem solved;
- approach adopted;
- risks and limitations;
- how to test.
Changes that affect protocol interoperability must prioritize backward compatibility whenever possible.
Do not open vulnerability reports in public issues. See SECURITY.md.