@aloud/runner 0.3.1 → 0.3.3

package/README.md

@@ -23,7 +23,7 @@ The first `aloud start` downloads Chromium, about 350 MB, once.
 | `aloud login [--token <token>]` | Connect this machine to your workspace |
 | `aloud start [--once] [--quiet] [--no-update]` | Update, then wait for studies and run them here |
 | `aloud status` | What is set up, what is not, and whether it is running |
-| `aloud allow <host>` | Let studies open this host from this machine |
+| `aloud allow <host>` | Approve a private or local host on this machine |
 | `aloud mcp` | Connect an MCP host to the web workspace selected by its MCP access token |
 | `aloud logout` | Forget the token on this machine |
 | `aloud --version` | Print the installed runner version |
@@ -34,6 +34,9 @@ Starting with 0.3.1, `aloud start` asks the connected Aloud server which officia
 it recommends. If a newer one is available, it installs that exact `@aloud/runner` version and
 relaunches it before claiming work. It never replaces code during an active study.
 
+Starting with 0.3.3, a runner that is already waiting does the same update automatically while it
+is idle. A customer does not have to notice a release, stop the process, or start it again.
+
 If an optional update cannot be installed, the terminal says why and a still-compatible runner may
 continue. If the server requires the update, nothing starts and the command exits non-zero with the
 manual repair command. `--no-update` is available for managed environments, but it cannot make an
@@ -53,10 +56,14 @@ the web app without deleting existing study history.
 
 ## What it will open
 
-A machine starts allowed to open `localhost` only. Anything else has to be added here, with
-`aloud allow <host>`, and that list lives on this machine in `~/.aloud/credentials.json`. Nothing
-the server sends can add to it, so a study offered for a host you never allowed is refused rather
-than run.
+Public websites work automatically. The runner grants only the public domain named by the current
+lease, checks DNS again immediately before launch and on every later network request, and forces
+private-network access off for that study. The grant disappears with the lease and is never written
+to `~/.aloud/credentials.json`.
+
+Localhost, private IPs, and names that resolve inside a private network remain explicit. Add those
+once with `aloud allow <host>`; that list lives only on this machine. Nothing the server sends can
+widen it, and cloud metadata and link-local targets are always refused.
 
 The token is stored in that same file at mode 0600, and `aloud logout` deletes it. Revoking a
 machine from the web app takes effect immediately, including for a study already running.