proper docs and .version

rig/docs/index.html

@@ -386,7 +386,8 @@ docker load &lt; rig.tgz &amp;&amp; make cluster up PROFILE=offline   <span clas
       derived from the cluster's Docker network at install time, because Docker picks
       that subnet and it differs between machines.</p>
       <p>Those addresses are reachable from the Linux side, including inside WSL. A
-      browser on Windows has no route to them: use the ingress host ports instead.</p>
+      browser on Windows has no route to them: use the environment's HTTP port instead, where
+      an overlay's gateway listens (its kind config maps it to the host).</p>
 
       <h3>Networking and memory</h3>
       <p>The cluster uses kind's built-in networking, which does enforce standard
@@ -417,9 +418,9 @@ OVERLAY=local/myenv make cluster up
 </code></pre>
       <p>With none named, rig runs its own <code>examples/starter</code>.
       <code>examples/data</code> carries postgres, redis and airflow as an overlay's own
-      addons. A project can also carry rig at <code>&lt;project&gt;/rig/</code> and be
-      the overlay itself, with a three-line forwarding Makefile — see
-      <code>docs/notes/overlay.md</code>.</p>
+      addons. A project can carry rig at <code>./rig</code>, or keep it anywhere and name
+      it with <code>RIG_DIR</code>. <code>.version</code> names the release; the project
+      records the one it was last run against. See <code>docs/notes/overlay.md</code>.</p>
 
       <h3>What runs in it</h3>
       <p>Each component is one of three things, and switching between them is a