Add OrcaReplay to Infrastructure & Proxies

[xizhuomengcontin]

One line added to ## 🏗️ Infrastructure & Proxies, placed by star count between claude-code-open (68 ⭐) and Claudify (32 ⭐), matching the descending order of the section.

- [**OrcaReplay**](https://github.com/Continuum-AI-Corp/OrcaReplay) - (69 ⭐) - Records a Claude Code run through a local proxy, then replays it offline byte-for-byte or forks it from any checkpoint onto a different model.

Why this section

The closest neighbour already listed is claude-code-proxy (seifghazi) — "Proxy that captures and visualizes in-flight Claude Code requests". OrcaReplay is the same shape of thing at capture time and then goes further: the recording is re-executable.

orca record claude                        # your session, unmodified
orca replay last                          # same run again, network off, byte-for-byte
orca replay last --from 4 --model <other> # same prefix, different model from step 4

It also records what the proxy cannot see on its own — shell exit codes and timing, per-turn file changes via a shadow git index, MCP traffic — and merges them into one timeline ordered by when things actually happened.

I considered 📊 Usage & Observability instead, but that section is about token and cost tracking (ccusage, codeburn, Claude-Code-Usage-Monitor), which is not what this does. Move it if you disagree.

Notes

• Searched the README for orcareplay first: 0 hits, no duplicate.
• Left the Changelog alone — it looks like you write those in batches.
• Apache-2.0, Node 20+, npm orcareplay. Validated end to end against Claude Code fixing a real bug (docs/validation.md).

Disclosure: I work on OrcaReplay.