diff --git a/docs/guides/concurrent-execution.md b/docs/guides/concurrent-execution.md
index 263a85e61d..e01b9aeea0 100644
--- a/docs/guides/concurrent-execution.md
+++ b/docs/guides/concurrent-execution.md
@@ -1019,7 +1019,9 @@ obligations) so reviewers approaching any slice PR see the strategic
 direction below it.
 
 The pipeline work branch is itself the context PR's head — there is no
-separate `egg/<id>/context` doc-only branch. The open path is a single
+separate `egg/<id>/context` doc-only branch, so slice-1's base resolves
+to `egg/<id>/work` (the context PR head) rather than stacking onto an
+`egg/<id>/context` branch. The open path is a single
 idempotent gateway call: `GatewayClient.lookup_open_pr("egg/<id>/work", base)`
 runs `gh pr list --head <branch> --base <base> --state open --json
 number` first; on hit, the existing PR number is reused, on miss
diff --git a/docs/reference/orchestrator-cli.md b/docs/reference/orchestrator-cli.md
index a3b10299c7..6feca7ad8c 100644
--- a/docs/reference/orchestrator-cli.md
+++ b/docs/reference/orchestrator-cli.md
@@ -647,7 +647,7 @@ All five subcommands honour `EGG_ORCHESTRATOR_URL` and `EGG_LIFECYCLE_SECRET` fo
 
 ## Context PR Surfaces ([#2777](https://github.com/jwbron/egg/issues/2777))
 
-Slice-aware pipelines (issue-mode pipelines with `contract.slices`) open the **Context PR** — `egg/<pipeline_id>/work → main` — up-front at the plan→implement boundary, hard-required and idempotent (#2777). See [Orchestrator Architecture: Context PR (slice-aware mode)](../architecture/orchestrator.md#context-pr-slice-aware-mode-2777) and the [Concurrent Execution Slice PR Stack](../guides/concurrent-execution.md#slice-pr-stack) section for the full mechanics. The Context PR is orchestrator-authored; `egg-orch` does **not** ship dedicated `--context-branch` / `--context-pr` flags. Operators inspect the Context PR through the same surfaces used for any other contract metadata:
+Slice-aware pipelines (issue-mode pipelines with `contract.slices`) open the **Context PR** — `egg/<pipeline_id>/work → main` — up-front at the plan→implement boundary, hard-required and idempotent (#2777). The up-front context-PR mechanism originated in [#2548](https://github.com/jwbron/egg/issues/2548) and was hardened into the current orchestrator-authored, idempotent form by #2777. See [Orchestrator Architecture: Context PR (slice-aware mode)](../architecture/orchestrator.md#context-pr-slice-aware-mode-2777) and the [Concurrent Execution Slice PR Stack](../guides/concurrent-execution.md#slice-pr-stack) section for the full mechanics. The Context PR is orchestrator-authored; `egg-orch` does **not** ship dedicated `--context-branch` / `--context-pr` flags. Operators inspect the Context PR through the same surfaces used for any other contract metadata:
 
 ```bash
 # Inspect the contract's pr fields. The top-level --pipeline-id flag goes BEFORE