Copilot instructions

1## PR Review Guidelines
2 
3When reviewing pull requests:
4 
5- Only comment on semantically meaningful issues: bugs, incorrect logic, security problems, or API contract violations.
6- Skip style, formatting, naming, and whitespace observations unless they cause functional problems.
7- Keep each comment short — one or two sentences maximum.
8- Do not write long descriptions or summaries of what the code does.
9- Do not suggest refactors or improvements unrelated to the PR's stated goal.
10- NEVER produce a review body or top-level PR overview comment. The review body MUST be empty. Put findings only in inline comments on specific lines.
11