Aggregate guest-mode link, fill out IPC stack feat

Such that we just link on `guest`_ and use in the feat line as well as
the code ex. Fill out the IPC-stack feature bullet and put the
`.trionics` one last. Also fix-n-finish the `uv` shell install section.

docs/README.rst

@@ -41,25 +41,26 @@ Features
 --------
 - **It's just** a ``trio`` API!
 - *Infinitely nesteable* process trees running embedded ``trio`` tasks.
-- Swappable, OS-specific, process spawning via multiple backends.
-- Modular IPC stack, allowing for custom interchange formats (eg.
+- Support for a swappable, OS-specific, process spawning via
+  multiple backends.
+- A modular IPC stack, allowing for custom interchange formats (eg.
   as offered from `msgspec`_), varied transport protocols (TCP, RUDP,
   QUIC, wireguard), and OS-env specific higher-perf primitives (UDS,
   shm-ring-buffers).
-- Optionally distributed_: all IPC and RPC APIs work over multi-host
+- optionally distributed_: all IPC and RPC APIs work over multi-host
   transports the same as local.
-- Builtin high-level streaming API that enables your app to easily
+- A high-level builtin streaming API that enables your app to easily
   leverage the benefits of a "`cheap or nasty`_" `(un)protocol`_.
-- A "native UX" around a multi-process safe debugger REPL using
-  `pdbp`_ (a fork & fix of `pdb++`_)
-- "Infected ``asyncio``" mode: support for starting an actor's
+- "native UX" for a multicore-safe debugger REPL using `pdbp`_ (a
+  fork & fix of `pdb++`_)
+- "infected ``asyncio``" mode: support for starting an actor's
   runtime as a `guest`_ on the ``asyncio`` loop allowing us to
   provide stringent SC-style ``trio.Task``-supervision around any
   ``asyncio.Task`` spawned via our ``tractor.to_asyncio`` APIs.
-- A **very naive** and still very much work-in-progress inter-actor
+- a **very naive** and still very much work-in-progress inter-actor
   `discovery`_ sys with plans to support multiple `modern protocol`_
   approaches.
-- Various ``trio`` extension APIs via ``tractor.trionics`` such as,
+- various ``trio`` extension APIs via ``tractor.trionics`` such as,
   - task fan-out `broadcasting`_,
   - multi-task-single-resource-caching and fan-out-to-multi
     ``__aenter__()`` APIs for ``@acm`` functions,