Copilot Instance Coordination

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

I have multiple instances of copilot working on related code (in different folders, but same repo). I would like to start another copilot instance that could be aware of the other instances and inject control flow to them to coordinate commits and syncs or even pass new context or queries to them.

### Proposed solution

Essentially a local "swarm awareness" layer so multiple agents working on the same codebase can share lock state, task assignments, and file-level conflict detection. Worth calling out both the discovery mechanism (e.g., a local socket/registry) and the coordination protocol (e.g., broadcasting file intents before edits).

### Example prompts or workflows

Tell copilot operating in e:\Github\McpServer to commit and push, then wait for a new commit on the remote, then pull before continuing.

### Additional context

_No response_