Proposal: include OrcaReplay (MCP server for recording and replaying a Copilot session)

Proposing [OrcaReplay](https://github.com/Continuum-AI-Corp/OrcaReplay) for the collection, following the shape of #29.

**Disclosure: I maintain it.** Apache-2.0, npm, Node 20+, no paid tier, no account, no hosted service.

## What it is

It records a coding-agent session at the HTTP boundary to the model provider — from outside the process — and can serve that recording back so the same session runs again with the provider unreachable and no key. The recording is also readable: which turn changed a file, which command ran, where the build broke, answered from the trace rather than from the agent's own summary of its context window.

## What it would contribute here

An **MCP server** over stdio with six tools — `orca_list`, `orca_show_run`, `orca_graph`, `orca_checkpoints`, `orca_replay`, `orca_compare`. Four are read-only over a local trace store. There is also a skill (`agent-run-forensics`) that drives them with a fixed protocol, if a skill entry is the better shape.

Nothing is installed into Copilot: the recorder wraps the process it launches and moves a base-URL variable for that child only.

## Why I am asking rather than opening a PR

The **External Plugins** list is currently five entries, all GitHub or Microsoft. I could not find written criteria for community submissions, and #35 suggests I am not the only one unsure where the line sits between this repo, `awesome-copilot`, and self-publishing.

So: **is a third-party plugin in scope here at all?** If yes, I will open the PR in whatever shape you prefer — an External Plugins entry, a skill under `plugin/`, or an MCP entry once that section lands. If no, that is a useful answer too and I will take it to `awesome-copilot` instead; no follow-up needed.

## Three limits, stated up front rather than found later

- **A matching replay is not a determinism result.** It shows the recorded run reproduces, not that the model is stable across calls.
- **`egress=blocked` means model-provider egress only.** Recorded tool calls still execute for real on replay — a recorded `curl` reaches the network. Replay is not a sandbox.
- **Embedding calls are not captured** by the default adapter, so a retrieval step is absent from the trace even when the chat turns are complete.

Happy to answer anything else, and equally happy to hear this is out of scope.

Start by reviewing the current External Plugins list and the discussion in #29 and #35, then compare the proposed MCP-server and skill shapes described here. Done means receiving a decision about whether third-party plugins are in scope and, if so, which contribution shape is preferred.

Escrito por el modelo de indexación a partir del texto del issue.