The macOS wrapper starts the container service itself when it is down (from dev 685ce778cf34)

doc/install/macos_container_install.md

@@ -26,8 +26,10 @@ Apple Silicon. It's free.
    container system start
    ```
 
-You only do this once. You can check the service any time with
-`container system status`.
+You only do this once: the first start sets up the service's kernel. After
+a restart the service is down again, and the wrapper you install in Step 3
+starts it for you the next time you run a Klammertext command. You can check
+the service any time with `container system status`.
 
 ## Step 2 — Download Klammertext
 
@@ -142,8 +144,8 @@ That's it — you're running Klammertext.
   still runs your source build and `ktextc` runs the container.
 - **Quitting.** Klammertext only runs while you're using it; there's nothing
   left running afterward. If you want to stop the `container` service entirely,
-  run `container system stop`; start it again with `container system start` next
-  time.
+  run `container system stop`; the wrapper starts it again the next time you
+  run a Klammertext command.
 
 ## Editor support (Emacs, Sublime Text)
 
@@ -167,9 +169,10 @@ Each package's README explains its installation.
   open a fresh Terminal.
 - **`container: command not found`** — the `container` runtime isn't installed
   (Step 1), or the Terminal window predates the install (open a new one).
-- **A command hangs or won't connect** — the `container` service isn't running.
-  Run `container system start` (check with `container system status`), then try
-  again.
+- **`the container service did not start`** — the wrapper starts the
+  `container` service when it is down, and this time it could not. Run
+  `container system start` yourself to see the service's own message (check
+  with `container system status`), then try again.
 - **A run aborted and now seems stuck** — `container run --rm` can leave the
   container behind after an error. Clear leftovers with: