A repository uses an unusual error-handling convention. The maintainer wants Copilot code review to consider it for future pull requests. What is the best approach?

1. Describe the convention only in one developer's private chat history.
2. Add the convention only to the generated pull request summary after review.
3. Rename every branch to include the entire convention.
4. Add concise, concrete review guidance to supported repository instruction files.