Copilot instructions

1This file contains Copilot-specific additions. See AGENTS.md for the shared cross-tool governance layer.
2 
3# Copilot-specific guidance
4 
5## Test generation
6 
7- Prefer unittest.TestCase for generated tests to match the existing test suite.
8- Mock external calls with unittest.mock.patch.
9 
10## Pull request reminders
11 
12Before suggesting a pull request:
13 
14- Confirm that pytest passes.
15- For changes that belong in the next release notes, add a `changelog.d/<n>.<type>.md` fragment (do not edit `CHANGELOG.md` or bump version manifests). See `CONTRIBUTING.md` / `AGENTS.md` § Changelog and releases and fill the PR template’s Agent disclosure + Relationship sections.
16- If changes were made anywhere under skills/last30days/, confirm the install copy has been refreshed with:
17 
18npx skills add . -g -y
19 
20## Vendor exclusion zone
21 
22- Never suggest changes to skills/last30days/scripts/lib/vendor/.
23- Treat skills/last30days/scripts/lib/vendor/ as a no-touch zone.
24 
25## CI expectations
26 
27GitHub CI runs:
28 
29- pytest
30- ruff
31 
32Generated changes should pass both before review is requested.
33 
34## CLI examples
35 
36When suggesting CLI usage examples for safe local testing, default to:
37 
38--emit=compact --mock
39