Rename transport binding to WIP over HTTP

crates/wip-tui/README.md

@@ -8,12 +8,17 @@ owned by the client runtime.
 
 ## Start
 
-HTTPS is the normal mode:
+Supply one `http` or `https` endpoint:
 
 ```console
 cargo run -p wip-tui -- --endpoint https://wip.example.test/api/wip
 ```
 
+The same canonical endpoint is used unchanged to construct requests, perform
+HTTP I/O, and partition the client cache. WIP over HTTP does not define separate
+HTTPS and development-HTTP profiles; URL scheme, TLS, certificate, authentication,
+and proxy policy belong to the HTTP implementation and deployment.
+
 The endpoint may instead be supplied as `WIP_ENDPOINT`. A non-secret cache
 partition identity may be supplied with `--security-context NAME` or
 `WIP_SECURITY_CONTEXT`. The default request timeout is 30 seconds and can be
@@ -31,16 +36,6 @@ Use `--authorization-env OTHER_VARIABLE` to select another variable. The value i
 redacted from `Debug` and is never rendered. Shell and process environment security
 remain the operator's responsibility.
 
-Plain HTTP is rejected by default. It is available only as an explicit loopback
-development mode:
-
-```console
-cargo run -p wip-tui -- http://127.0.0.1:8080/wip --allow-http
-```
-
-Non-loopback HTTP remains rejected even with `--allow-http`. For production, use a
-real HTTPS endpoint and a trusted TLS deployment.
-
 ### Filesystem server example
 
 In one terminal:
@@ -52,14 +47,13 @@ cargo run -p wip-fs-server -- \
   --root /tmp/wip-example \
   --listen 127.0.0.1:8080 \
   --base-path /wip \
-  --development-http \
   --read-write
 ```
 
 In another:
 
 ```console
-cargo run -p wip-tui -- http://127.0.0.1:8080/wip --allow-http
+cargo run -p wip-tui -- http://127.0.0.1:8080/wip
 ```
 
 Expand `/`, select `notes.txt`, focus the Interface/Operation pane, and choose