jwbron · james-in-a-box · Jun 2, 2026 · Jun 2, 2026 · Jun 2, 2026 · Jun 2, 2026
diff --git a/.egg-state/brc-history/issue-2908-impl2-implement-slice-6.json b/.egg-state/brc-history/issue-2908-impl2-implement-slice-6.json
diff --git a/.egg-state/brc-history/issue-2908-impl2-implement-slice-6.md b/.egg-state/brc-history/issue-2908-impl2-implement-slice-6.md
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -39,9 +39,16 @@ If `.venv` is absent, run `make deps` to install everything. This installs `uv`
 ## Key Entry Points
 
 - **Headless agents** use the Agent SDK (`egg_agent` package)
-- **Agent work** goes through the MCP server — see
-  [`submit_task`](docs/guides/sdlc-pipeline.md) (full
-  refine → plan → implement). The legacy interactive-mode CLI
-  (`bin/egg`) was removed in
-  [#1762](https://github.com/jwbron/egg/issues/1762).
+- **Operators submit work** through the orchestrator MCP server's
+  [`submit_task`](docs/guides/sdlc-pipeline.md) tool (full
+  refine → plan → implement). That MCP server is operator-facing
+  (port 9850); sandbox agents drive pipeline lifecycle operations
+  through the `egg-orch` / `egg-contract` / `egg-checkpoint` shell
+  CLIs. The legacy interactive-mode CLI (`bin/egg`) was removed in
+  [#1762](https://github.com/jwbron/egg/issues/1762); the
+  in-process agent-side MCP tool surface was retired alongside
+  these docs in [#2908](https://github.com/jwbron/egg/issues/2908)
+  slice-6 (the operator-facing orchestrator MCP server is
+  unaffected). See
+  [Agent Pipeline-Lifecycle Surface](docs/reference/agent-tools.md).
 - See [CONTRIBUTING.md](CONTRIBUTING.md) for dev setup, branching, and PR workflow
diff --git a/docs/architecture/git-isolation.md b/docs/architecture/git-isolation.md
@@ -35,7 +35,7 @@ This document focuses on the specific challenge of **multi-agent git isolation**
 | Agent accesses another agent's workspace | Filesystem isolation---other workspaces don't exist in container's view |
 | Agent pushes to unauthorized branches | Gateway enforces branch ownership policy |
 | Agent pushes malicious code directly to main | Gateway blocks direct pushes to protected branches; PRs require human review |
-| Agent bypasses BRC consensus in pipeline session | Gateway blocks direct `git push` for pipeline sessions; requires `consensus_push` marker from `mcp__brc__propose` (or fallback `egg-orch consensus propose --push`) |
+| Agent bypasses BRC consensus in pipeline session | Gateway blocks direct `git push` for pipeline sessions; requires `consensus_push` marker from `egg-orch consensus propose --push` (the agent-side `mcp__brc__propose` MCP tool was retired alongside this surface in [#2908](https://github.com/jwbron/egg/issues/2908) slice-6 — the CLI is the single agent surface) |
 | Agent uses `git rebase origin/main` to contaminate pipeline branch | Gateway blocks any `git rebase` where the bare-form upstream or the `--onto` target is a protected base ref (`origin/main`, `main`, `origin/HEAD`, `FETCH_HEAD`) in pipeline sessions (#2224); base-branch rebase runs only via orchestrator-controlled `_rebase_pipeline_branch_onto_base` |
 | Agent discovers or exfiltrates credentials | Credentials only exist in gateway; container never sees them |
 | Agent modifies git config to bypass security | Container has no access to git metadata; config is gateway-controlled |
@@ -259,7 +259,7 @@ Each agent works on its own isolated worktree with its own staging area. This ap
 
 **Pipeline agents:** In concurrent pipeline execution, all agents push to the same shared branch (e.g., `egg/issue-{N}`) but each agent has its own worktree. Since each role has mutually exclusive file write permissions (coder → source code, tester → tests, documenter → docs), push rebases cannot conflict. Reviewer agents sync their worktrees before reviewing by fetching and merging the pipeline branch, ensuring they evaluate up-to-date code from producers. See [Concurrent Execution Guide](../guides/concurrent-execution.md#per-agent-worktree-isolation) for details.
 
-**Pipeline-session push enforcement:** For all pipeline sessions (refine/plan/implement), the gateway blocks direct `git push` — all pushes must go through `mcp__brc__propose` (which pushes to origin and sends CONSENSUS_PROPOSE in one step; push is on by default). The fallback CLI is `egg-orch consensus propose --push`. This structurally enforces the "all changes must be reviewed" invariant rather than relying on agent compliance. See [Gateway README — Pipeline Push Enforcement](../../gateway/README.md#pipeline-push-enforcement-brc-sessions) for details.
+**Pipeline-session push enforcement:** For all pipeline sessions (refine/plan/implement), the gateway blocks direct `git push` — all pushes must go through `egg-orch consensus propose --push` (which pushes to origin and sends CONSENSUS_PROPOSE in one step; `--push` is opt-in and is the flag that carries the `consensus_push` marker the gateway requires). The agent-side `mcp__brc__propose` MCP tool was retired alongside this surface in [#2908](https://github.com/jwbron/egg/issues/2908) slice-6 — the CLI is the single agent surface. This structurally enforces the "all changes must be reviewed" invariant rather than relying on agent compliance. See [Gateway README — Pipeline Push Enforcement](../../gateway/README.md#pipeline-push-enforcement-brc-sessions) for details.
 
 **Worktree-aware APIs:** All gateway APIs that access the filesystem use `map_container_path_to_worktree()` to resolve container repo paths to worktree paths. This includes git operations and contract operations (`egg-contract show`, `add-commit`, `add-decision`, etc.). The mapping is transparent to agents --- they use their normal repo path and the gateway resolves it to the correct worktree.
 

diff --git a/docs/architecture/orchestrator.md b/docs/architecture/orchestrator.md
@@ -896,7 +896,7 @@ WS7-observed 10–13 min idle ceiling on real BRC phases).
 
 | `EGG_BRC_IDLE_BUDGET_MIN` | Behaviour |
 |---------------------------|-----------|
-| default `30` (minutes) | At budget threshold, wrapper emits `mcp__progress__overseer_alert` (anomaly `stuck-phase-transition`, priority `high`) **and keeps blocking**. At `2 ×` budget, the alert priority escalates and the wrapper still keeps blocking. Idleness is **not** a FAILED transition. |
+| default `30` (minutes) | At budget threshold, wrapper emits an `OVERSEER_ALERT` (via `egg-orch overseer alert`, anomaly `stuck-phase-transition`, priority `high`) **and keeps blocking**. At `2 ×` budget, the alert priority escalates and the wrapper still keeps blocking. Idleness is **not** a FAILED transition. |
 
 The slice-2/-3 era also exposed an `EGG_BRC_EVENT_PUMP=false` escape
 to the legacy capped-restart wrapper; that escape is gone after
@@ -1334,7 +1334,7 @@ if is_orchestrator_mode():
 | `EGG_ORCH_SLICE_FAILURE_GRACE_SECONDS` | Slice-DAG: grace window before failure-cascade marks downstream subtree `BLOCKED_ON_FAILED_DEPENDENCY` (#2137) | `60.0` |
 | `EGG_ORCH_STACKED_PR_RECONCILER_INTERVAL_SECONDS` | Slice-DAG: stacked-PR reconciler polling cadence for orphaned child PRs (#2137) | `30.0` |
 | `EGG_BRC_EVENT_PUMP` | **Removed in [#2908](https://github.com/jwbron/egg/issues/2908) slice-4 task-4-2.** During the slice-2/-3 rollout this flag selected between the legacy `_CONSENSUS_WRAPPER_TEMPLATE` (`false`) and the new `_EVENT_PUMP_WRAPPER_TEMPLATE` (`true`). Slice-4 deleted the legacy template, the surrounding selector logic, and the env var read itself — the orchestrator no longer consults this variable. Operators that referenced it in helm values / pod-spec env can drop the row. The supported regression path is `git revert` of slices 1–3 / slice-4 in reverse-merge order (see [Rollback plan](#rollback-plan)); reverting slice-4 restores the env var alongside the legacy template. | n/a (removed) |
-| `EGG_BRC_IDLE_BUDGET_MIN` | BRC consensus wrapper idle / no-progress safety budget in minutes ([#2908](https://github.com/jwbron/egg/issues/2908)). Replaced the legacy 3-restart FAIL cap with an overseer-alert escalation that does not transition the pipeline to FAILED. At budget threshold the wrapper emits `mcp__progress__overseer_alert` (anomaly `stuck-phase-transition`, priority `high`) and keeps blocking; at `2 ×` budget the priority escalates and the wrapper still keeps blocking. Default 30 min is well above the WS7-observed 10–13 min idle ceiling on real BRC phases. See [Idle / no-progress safety budget](#idle--no-progress-safety-budget). | `30` |
+| `EGG_BRC_IDLE_BUDGET_MIN` | BRC consensus wrapper idle / no-progress safety budget in minutes ([#2908](https://github.com/jwbron/egg/issues/2908)). Replaced the legacy 3-restart FAIL cap with an overseer-alert escalation that does not transition the pipeline to FAILED. At budget threshold the wrapper emits an `OVERSEER_ALERT` (via `egg-orch overseer alert`, anomaly `stuck-phase-transition`, priority `high`) and keeps blocking; at `2 ×` budget the priority escalates and the wrapper still keeps blocking. Default 30 min is well above the WS7-observed 10–13 min idle ceiling on real BRC phases. See [Idle / no-progress safety budget](#idle--no-progress-safety-budget). | `30` |
 
 ### Constants
 

diff --git a/docs/guides/agent-teams.md b/docs/guides/agent-teams.md
@@ -163,7 +163,7 @@ The reasoning layer combines two complementary mechanisms with different purpose
 
 > **Tester `checks_passed` requirement:** The Tester's attestation must include a `checks_passed` list naming every configured check that **passed** (e.g. `["lint", "test"]`). Only include checks with a clean exit — do not include checks that failed. The server validates that all checks listed in `repositories.yaml` appear in this list and rejects the proposal if any are missing. Running tests alone is not sufficient — all configured checks must pass and be reported.
 
-> **Tester `attestation.tests_run` vs propose `tests_run`:** The `attestation.tests_run` field is an **integer count** of tests executed (e.g. `42`). This is distinct from the propose call's top-level `tests_run` argument, which is a **list of test identifiers** (e.g. `["tests/test_foo.py::test_bar"]`). Passing a list for `attestation.tests_run` (or leaving it at the default `0`) causes a validation error. The `mcp__brc__propose` handler validates tester attestation locally before sending to the orchestrator, so misconfigured payloads fail with an actionable error rather than a 400 from the server (#2338).
+> **Tester `attestation.tests_run` vs propose `tests_run`:** The `attestation.tests_run` field is an **integer count** of tests executed (e.g. `42`). This is distinct from the propose call's top-level `tests_run` argument, which is a **list of test identifiers** (e.g. `["tests/test_foo.py::test_bar"]`). Passing a list for `attestation.tests_run` (or leaving it at the default `0`) causes a validation error. The `egg-orch consensus propose` handler validates tester attestation locally before sending to the orchestrator, so misconfigured payloads fail with an actionable error rather than a 400 from the server (#2338).
 
 **Reviewer evaluations (`CONSENSUS_ACK/NACK`):**
 
@@ -238,7 +238,7 @@ When a producer pushes new commits after proposing, existing reviews become stal
 
 This mechanism enforces the principle that **all changes must be reviewed**: post-proposal pushes cannot bypass the review process. The `check_confirm_guard()` provides a server-side blocking mechanism even if a reviewer misses the `CONSENSUS_RE_REVIEW` notification. See [Concurrent Execution — Auto Re-Propose on Push/Commit](concurrent-execution.md#auto-re-propose-on-pushcommit) for the full details.
 
-Additionally, the gateway enforces that **direct `git push` is blocked** for pipeline sessions — agents must use `mcp__brc__propose` (or the fallback CLI `egg-orch consensus propose --push`) to bundle the push with a BRC proposal. This makes the review invariant structural rather than relying on auto-repropose detection. See [Concurrent Execution — Gateway-Level Push Enforcement](concurrent-execution.md#gateway-level-push-enforcement-pipeline-sessions) for details.
+Additionally, the gateway enforces that **direct `git push` is blocked** for pipeline sessions — agents must use `egg-orch consensus propose --push` to bundle the push with a BRC proposal (the agent-side `mcp__brc__propose` MCP tool was retired alongside this surface in [#2908](https://github.com/jwbron/egg/issues/2908) slice-6 — the CLI is the single agent surface). This makes the review invariant structural rather than relying on auto-repropose detection. See [Concurrent Execution — Gateway-Level Push Enforcement](concurrent-execution.md#gateway-level-push-enforcement-pipeline-sessions) for details.
 
 ### Agent Crash Mid-Protocol