Reviewable changes

← Back to concept

One coherent problem per change

Describe the problem and resulting behavior so a reviewer can assess the change without its chat history. Include relevant validation and material limitations.

Do not mix architectural migration with unrelated cleanup. Preserve another contributor's working changes. Inspect the diff before publishing and follow the repository's existing branch and review process.

A commit, merge or release is not proof of correctness: the contract, tests and runtime behavior must agree. Deployment order and rollback compatibility are part of the release contract.