docs: config changes are operator merges on the forge

Rewrites the config-change flow around the forge merge and the
DeployRequest{rev} deploy, drops the MergeConfigPr approval, its deploy
DAG, the hive's `/webhook/` route and the `core` merge allowlist from
the docs, and states that operators join the `operators` team by hand.

Refs #4850

docs/web-ui/dashboard.md

@@ -877,11 +877,10 @@ renderApprovals`) with three stacked sections:
   right-aligned `requested <N> ago` relative time from
   `ApprovalView.requested_at`. Glyph and chip vary by kind:
 
-  | kind | glyph | chip | sha shown |
-  |---|---|---|---|
-  | `merge_config_pr` | `⇒` | `merge-pr` | PR-head sha (`sha_short`) |
-  | `update_meta_inputs` | `↻` | `meta-update` | — |
-  | `schedule_prompt` | `⏱` | `schedule` | — |
+  | kind | glyph | chip |
+  |---|---|---|
+  | `update_meta_inputs` | `↻` | `meta-update` |
+  | `schedule_prompt` | `⏱` | `schedule` |
 
   <!-- vale write-good.Passive = NO -->
   The chip ticks live every second via a `data-requested-at`
@@ -889,12 +888,9 @@ renderApprovals`) with three stacked sections:
   the request has been pending ≥ 1h so a stale approval stands out;
   the `.stale` class flips precisely at the 3600s boundary rather
   than at the next `renderApprovals` call.
-- **what-changed body** — the submitting agent's description, then
-  kind-specific drill-in triggers:
-  - `merge_config_pr`: `↳ review PR on forge ↗` deep-links the
-    config PR into `agent-configs/<agent>/pulls/<pr_number>` (shown
-    only when `forge_present` is true and `pr_number` has a value). The config diff
-    lives on the forge PR itself — no inline diff side-panel.
+- **what-changed body** — the submitting agent's description, then the
+  kind's payload: the inputs to bump (`update_meta_inputs`) or the prompt to
+  schedule (`schedule_prompt`).
 - **decision actions** — `◆ APPR0VE` and `DENY`. Deny pops a
   `prompt()` for an optional reason carried to the submitting agent as
   `HelperEvent::ApprovalResolved.note`.