docs: map the 1.x tool names to the 2.0 ones

CHANGELOG.md

@@ -8,7 +8,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/)
 
 ## [Unreleased]
 
-_If you are upgrading from 1.x: please see [Migrating from 1.x](README.md#migrating-from-1x)._
+_If you are upgrading from 1.x: please see [Migrating from 1.x](MIGRATING.md)._
 
 ### Changed
 

MIGRATING.md

@@ -0,0 +1,31 @@
+# Migrating from 1.x
+
+## Tool names
+
+Every tool was renamed — see [Naming Tools and Fields](DEVELOPING.md#-naming-tools-and-fields).
+
+| 1.x                            | 2.0                            |
+| ------------------------------ | ------------------------------ |
+| `get_apex_log_summary`         | `apexlog_get_summary`          |
+| `analyze_apex_log_performance` | `apexlog_list_slow_operations` |
+| `find_performance_bottlenecks` | `apexlog_list_limit_risks`     |
+| `execute_anonymous`            | `apexlog_execute_anonymous`    |
+
+Update wherever you name a tool yourself:
+
+- Tool allow and deny lists. Some clients qualify a name with the server, so `execute_anonymous` may appear as `mcp__apex-log-mcp__execute_anonymous`.
+- Prompts, agents and skills.
+
+Response fields changed too — see the [changelog](CHANGELOG.md).
+
+## Org access
+
+`--allowed-orgs` is ignored and warns on stderr. Delete it.
+
+| 1.x                             | 2.0                                                              |
+| ------------------------------- | ---------------------------------------------------------------- |
+| No flag (tool hidden)           | No flag — the tool works against non-production orgs             |
+| `--allowed-orgs ALLOW_ALL_ORGS` | No flag. Add `--allow-production-orgs` to target production       |
+| `--allowed-orgs <org>,<org>`    | No flag. Org type decides, not an org list                       |
+
+`ALLOW_ALL_ORGS` no longer implies consent to run against production.

README.md

@@ -238,18 +238,6 @@ For an analysis-only deployment:
 }
 ```
 
-### Migrating from 1.x
-
-`--allowed-orgs` was removed in 2.0. It is still accepted so existing configurations keep starting, but it is ignored and logs a deprecation warning — you can delete it.
-
-| 1.x                              | 2.0                                                                      |
-| -------------------------------- | ------------------------------------------------------------------------ |
-| No flag (tool hidden)            | No flag — the tool is visible and works against non-production orgs      |
-| `--allowed-orgs ALLOW_ALL_ORGS`  | No flag. Add `--allow-production-orgs` only if you target production     |
-| `--allowed-orgs <org>,<org>`     | No flag. Org-by-org allowlisting is replaced by the org type policy      |
-
-Note that `ALLOW_ALL_ORGS` no longer implies consent to run against production.
-
 ## How It Works
 
 This server implements the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) to expose Apex log analysis as tools that any MCP-compatible AI client can call.