Contributor Checklist#

Use this checklist before opening or merging a contribution.

Code and behavior#

  • Change scope is focused and justified.

  • New behavior has tests.

  • Existing behavior is not unintentionally regressed.

Documentation#

  • User docs updated when integration behavior changes.

  • Developer docs updated when internals/workflow change.

  • Examples remain coherent with current API.

Contracts#

  • Public API impact is explicit.

  • Configuration precedence remains documented.

  • Diagnostics messages remain actionable.

Final verification#

  • Local tests pass.

  • Docs build is healthy.

  • Ready for review and release pipeline.