Copilot content exclusions now cover app and CLI agents

GitHub says Copilot app and Copilot CLI now respect content-exclusion policies set at enterprise, organization, and repository level, so excluded files are not used as agent context. Why it matters: A repository policy now reaches interactive agent surfaces, reducing the chance that sensitive files enter a coding-agent session by default.

Try this: Test a repo with `.env*`, secret/config paths, customer exports, and internal evaluation fixtures excluded. Save the retrieval-test transcript showing that Copilot app and CLI did not return an excluded file before granting broad repository work.