chore: rename example workflow to orca-code-review.yml (v1.2.1)

README.md

@@ -76,8 +76,8 @@ merge.
      it as an external **Connection** under Integrations, then reference it from
      a guardrail rule. OSV is free/public; Snyk and Semgrep need their own keys.
 
-3. Add this workflow at **`.github/workflows/orcarouter-code-review.yml`**
-   (copy from [`workflows/orcarouter-code-review.yml`](./workflows/orcarouter-code-review.yml)):
+3. Add this workflow at **`.github/workflows/orca-code-review.yml`**
+   (copy from [`workflows/orca-code-review.yml`](./workflows/orca-code-review.yml)):
 
    ```yaml
    name: Orca-Code-Review

RELEASE.md

@@ -32,7 +32,7 @@ When cutting a release from a merged feature branch:
 
 Until the tag is moved, do not advertise the new inputs under `@v1`. For
 pre-release dogfooding, pin an immutable commit SHA (as OrcaRouter-O2's own
-`.github/workflows/orcarouter-code-review.yml` does) rather than `@v1`.
+`.github/workflows/orca-code-review.yml` does) rather than `@v1`.
 
 ## Marketplace
 

action.yml

@@ -1,7 +1,7 @@
 # Orca-Code-Review — reusable composite action.
 #
 # Consumers reference this with `uses:` instead of copying the folder; see
-# workflows/orcarouter-code-review.yml for the ~15-line example workflow.
+# workflows/orca-code-review.yml for the ~15-line example workflow.
 #
 # Single-tier review (gpt-5.5): one review pass per run. The cheap->strong
 # cascade was retired after testing showed the cheap tier added no value online