doc: move runner documentation out of west-apis.rst

Now that the runners package no longer depends on west, we can move
the documentation for it from the orphan west-apis.rst page to the
build-flash-debug.rst page that documents the west extension commands
which use that package.

(This is a more logical place for this information, but it was
previously not possible to put it there since we must be able to build
the documentation on a system without west installed, excepting
content in west-apis.rst. Removing the dependency means the runners
automodule directive can safely appear in build-flash-debug.rst.)

Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>

doc/guides/west/build-flash-debug.rst

@@ -463,13 +463,22 @@ determined by the imported subclasses of ``ZephyrBinaryRunner``.
 individual runner implementations are in other submodules, such as
 ``runners.nrfjprog``, ``runners.openocd``, etc.
 
-Hacking and APIs
+Hacking
-****************
+*******
 
-Developers can add support for new ways to flash and debug Zephyr
+This section contains documentation the ``runners.core`` module used by the
-programs by implementing additional runners. To get this support into
+flash and debug commands. This is the core abstraction used to implement
-upstream Zephyr, the runner should be added into a new or existing
+support for these features.
-``runners`` module, and imported from :file:`runner/__init__.py`.
+
+.. warning::
+
+   These APIs are provided for reference, but they are more "shared code" used
+   to implement multiple extension commands than a stable API.
+
+Developers can add support for new ways to flash and debug Zephyr programs by
+implementing additional runners. To get this support into upstream Zephyr, the
+runner should be added into a new or existing ``runners`` module, and imported
+from :file:`runners/__init__.py`.
 
 .. note::
 
@@ -480,8 +489,8 @@ upstream Zephyr, the runner should be added into a new or existing
    changes break existing test cases, CI testing on upstream pull
    requests will fail.
 
-API Documentation for the ``runners.core`` module can be found in
+.. automodule:: runners.core
-:ref:`west-apis`.
+   :members:
 
 Doing it By Hand
 ****************

doc/guides/west/index.rst

@@ -46,8 +46,7 @@ context about the tool.
    planned.rst
    release-notes.rst
 
-For details on west's Python APIs (including APIs provided by extensions in the
+For details on west's Python APIs, see :ref:`west-apis`.
-zephyr), see :ref:`west-apis`.
 
 .. rubric:: Footnotes
 

doc/guides/west/west-apis.rst

@@ -72,24 +72,5 @@ west.util
 .. automodule:: west.util
    :members: west_dir, west_topdir, WestNotFound
 
-.. _west-apis-zext:
-
-Zephyr Extensions
-*****************
-
-This section contains documentation for APIs used by the extension commands
-which are part of the Zephyr repository. In particular, it documents the
-``runners.core`` module used by the :ref:`west-build-flash-debug`
-commands. This is the core abstraction used to implement support for these
-features.
-
-.. warning::
-
-   These APIs are provided for reference, but they are more "shared code" used
-   to implement multiple extension commands than a stable API.
-
-.. automodule:: runners.core
-   :members:
-
 .. _west #38:
    https://github.com/zephyrproject-rtos/west/issues/38

doc/guides/west/west-not-found.rst

@@ -7,7 +7,6 @@
 .. _west-apis-log:
 .. _west-apis-manifest:
 .. _west-apis-util:
-.. _west-apis-zext:
 
 West APIs
 #########