Feature: Discover custom agents from cwd, not just git root

# Feature Request: Discover custom agents from cwd, not just git root

### Describe the feature or problem you'd like to solve

Custom agent profiles (`.github/agents/*.agent.md`) are currently only discovered at the **git repository root**. In contrast, custom instructions (`AGENTS.md`, `.github/instructions/**/*.instructions.md`) are discovered from **both** the git root and the current working directory.

This inconsistency is a problem for **monorepos and large repositories** where different subtrees represent distinct projects, each with their own specialized agents. Teams working in a subdirectory have no way to define agents scoped to their project — they must place agents at the repo root, where they're visible to (and may conflict with) every other project in the repository.

### Proposed solution

Extend agent profile discovery to mirror how custom instructions already work:

1. Search for `.github/agents/*.agent.md` in **both** the git root **and** the current working directory (or its ancestors up to the git root).
2. When agents with the same name exist at multiple levels, apply the same precedence rules already used for instructions (cwd-level overrides repo-level).

This would be consistent with how the CLI already handles:
- `AGENTS.md` → discovered in git root **and** cwd
- `.github/instructions/**/*.instructions.md` → discovered in git root **and** cwd

### Example prompts or workflows

**Scenario:** A monorepo at `~/repos/platform` with multiple projects:

```
platform/ ← git root
├── .github/agents/ ← repo-wide agents (works today)
│ └── deploy-agent.agent.md
├── frontend/
│ └── .github/agents/ ← frontend-specific agents (not discovered today)
│ └── component-gen.agent.md
└── backend/
└── .github/agents/ ← backend-specific agents (not discovered today)
└── api-scaffold.agent.md
```

**Today:** Running `copilot` from `~/repos/platform/frontend` only shows `deploy-agent`. The `component-gen` agent is invisible to `/agent`.

**Expected:** Running `copilot` from `~/repos/platform/frontend` should show both `deploy-agent` (from repo root) and `component-gen` (from cwd).

### Additional context

- The CLI help text explicitly notes that `AGENTS.md` and `.github/instructions/` are scoped to "git root & cwd" — agent profiles are the outlier.
- This would also benefit organizations that use a single repo but have multiple teams, each wanting to define team-specific agents without polluting the shared repo-root namespace.
- No existing issue appears to cover this request (searched April 2026).

Start by tracing the existing discovery path for AGENTS.md and .github/instructions/**/*.instructions.md, then compare it with discovery of .github/agents/*.agent.md. Verify behavior from a repository root and nested working directory, including same-name precedence. Done means /agent lists both root and cwd-or-ancestor profiles with the closer profile taking precedence.

Rédigé par le modèle d'indexation à partir du texte de l'issue.