Copilot instructions

1# Review Go dependency bumps carefully
2 
3For Go module, `go.sum`, and `vendor/` bump PRs, review the actual code changes, not just the version bump.
4 
5Check for impact on:
6 
7- daemon or API behavior
8- container runtime, networking, storage, archive, registry, and BuildKit-related paths
9- syscall, namespace, cgroup, mount, or rootless behavior
10- transitive dependency changes
11- major version jumps, default changes, error handling changes, or hidden logic changes in vendored churn
12 
13Do not approve only because the PR is autogenerated, the version bump is small, or CI passes.
14 
15In the review summary, state what changed, what relevant code paths were inspected, and any remaining risk or need for targeted testing.
16