Develop1 min read
Contributing
Keep product behavior and documentation evidence aligned.
Create a focused feature branch, preserve unrelated work, and keep commits reviewable. Read repository guidance before editing. A behavior change must include tests and, when it changes a documented capability, the corresponding concept, task, reference, and evidence updates.
Before handoff, run the relevant checks, inspect the final diff, and document any release or operational assumption that could not be verified locally.
Update the capability inventory when product behavior changes. Documentation claims must cite discoverable source, configuration, tests, or runtime evidence. Historical pages alone are not evidence for current behavior.
Last updated for v2.0.0
Edit this page on GitHub