canopy-engine 0.1.2 → 0.1.3

package/README.md

@@ -21,7 +21,7 @@ npm install -g canopy-engine   # needs the network
 canopy
 ```
 
-(The two lines marked "needs the network" download from the npm registry. If you were given a file instead, `canopy-engine-0.1.2.tgz`, install that: `npm install -g ./canopy-engine-0.1.2.tgz`.)
+(The two lines marked "needs the network" download from the npm registry. If you were given a file instead, `canopy-engine-0.1.3.tgz`, install that: `npm install -g ./canopy-engine-0.1.3.tgz`.)
 
 **If the `canopy` command clashes with another tool** on your computer, use `canopy-engine` instead. It is the same program under a second name: `canopy-engine --version`, `canopy-engine doctor`, and so on.
 
@@ -100,7 +100,7 @@ The hook starts `canopy sync` in the background after every commit and merge so
 Run `canopy doctor` and send its output with your feedback. Healthy output (the hook line is not critical):
 
 ```
-canopy 0.1.2 doctor (C:\work\my-project)
+canopy 0.1.3 doctor (C:\work\my-project)
 
 OK    Node version >= 18 - v22.12.0
 OK    tree-sitter grammars (wasm) - 5 files
@@ -162,6 +162,7 @@ Each line is backed by a measurement (the numbers are quoted in the lines below)
 - "no map yet": run `canopy sync <path>` (or just `canopy`) before `canopy open <path>`.
 - A commit prints `canopy not found; skipping map update`: neither `canopy` nor `npx` is on the PATH git uses; install Canopy globally (`npm i -g canopy-engine`) or run `canopy hook uninstall`.
 - Parse errors in a few files are normal; the coverage block printed by `canopy sync` lists them and the rest of each file is still analyzed.
+- The viewer answers "forbidden" (403): it only accepts a `127.0.0.1` or `localhost` address. A forwarded port opened under another host name (Codespaces, dev containers, `ssh -L` with a custom name) is refused on purpose; open `http://127.0.0.1:<port>/` instead.
 
 ## License