# Issues and reviews ## Issues Search [open issues]() before creating one. Include current behavior, expected behavior, reproduction steps, and relevant logs without secrets. Use the repository labels rather than inventing priority categories. ## Pull requests A review should establish that: - behavior matches the linked issue; - authentication and current-user rules remain intact; - validation and errors are safe; - pagination remains bounded and deterministic; - risky behavior has tests; - documentation reflects API changes; and - the diff contains no unrelated cleanup. Be specific and constructive. Resolve discussion only after the concern is addressed or the participants agree on the trade-off. Contributors are recognized through commits, pull requests, reviews, and the [GitHub contributors page]().