Contributing

Good contributions reduce review friction and make intent obvious.

Contribution basics

• keep changes scoped
• explain why the change is needed
• include tests when behavior changes
• update docs when user-facing behavior changes

Before opening a PR

• check whether the issue or request already exists
• sync with upstream expectations for branch and review workflow
• make sure the change can be reviewed commit by commit

For docs work

• prefer clear structure over maximum volume
• keep examples realistic
• link related pages so readers can move through the docs naturally
• avoid copying upstream reference content verbatim when a curated explanation is better