Contributions that improve correctness, clarity, compatibility, or measurable project outcomes are welcome.
- Open an issue for a substantial behavioral or architectural proposal.
- Keep each pull request focused on one problem.
- Preserve backward compatibility unless the change explicitly documents and justifies a breaking release.
- Do not add secrets, private project data, generated caches, or machine-local paths.
python -m pip install -e ".[dev]"Run the same checks used by CI:
python validate.py
python -m pytest -q
python scripts/validate_publication.py
python scripts/build_release.py --version 1.1.0-rc.1 --output distWhen changing a skill:
- keep its
SKILL.mdconcise and put detailed guidance inreferences/; - update relevant trigger cases and executable project trials;
- preserve the distinction between observed evidence and inferred conclusions;
- run the promotion gate and explain any metric change;
- update
docs/ARCHITECTURE.mdwhen public architecture, data flow, configuration, or important commands change.
Describe the problem, the chosen solution, risks, validation commands, and any checks that could not be run. Documentation and tests should change together with user-visible behavior.
By contributing, you agree that your contribution is licensed under Apache License 2.0.