GitHub Copilot is a cross-platform AI assistant available in multiple IDEs, yet its configuration files are tied to a `.github` directory. This creates confusion for teams using GitLab, Bitbucket, or Azure DevOps, as the folder implies a GitHub-specific feature. The mismatch between a platform-agnostic tool and a platform-branded directory breaks repository organization logic.

The `.github` folder has a clear purpose for GitHub Actions and issue templates. Copilot, however, runs locally and doesn't require a remote host. Forcing its configuration here mixes platform governance with AI tool settings, creating a 'junk drawer' effect. A dedicated `.copilot` directory would separate these concerns cleanly.

Many developers now use multiple AI tools like Cursor and Claude. A tool-specific structure allows teams to add or remove AI configurations without affecting CI/CD or code ownership. This follows the precedent of neutral tools like VS Code using `.vscode/`. A phased migration could look for `.copilot/` first, then fall back to `.github/` for legacy support.