Thanks for improving Sol-Governed Codex. Focused bug fixes, documentation corrections, compatibility improvements, and carefully scoped workflow changes are welcome.
- Search existing issues before opening a new one.
- Use an issue for behavior changes that need design discussion.
- Keep changes narrow and preserve the role boundary: workers implement, Sol reviews.
- Never include credentials, tokens, private prompts, personal paths, or machine-specific state.
- For vulnerabilities, follow SECURITY.md instead of opening a public issue.
Fork and clone the repository, then create a topic branch. The validation suite needs Git, Bash, and Python 3.11 or later.
bash scripts/validate_repo.shIf you change anything below skills/sol-governed-workers, refresh the marketplace package before validation:
bash scripts/sync_plugin_skill.sh
bash scripts/validate_repo.shThe validator checks shell/TOML/JSON structure, routing semantics, prompt budgets, plugin drift, isolated installation, refusal paths, model failures, managed-contract updates, and idempotency.
In your pull request:
- Explain the user-visible outcome and why the change is needed.
- Keep unrelated formatting or cleanup out of the diff.
- Add or update tests and documentation when behavior changes.
- Keep always-loaded instructions inside the enforced word and character budgets.
- Run
bash scripts/validate_repo.shand report the result. - Review the complete diff and commit history for secrets and personal data.
- Confirm that new README commands and local links point to real targets.
By participating, you agree to follow the Code of Conduct. Contributions are licensed under the repository's MIT License.