cleanup, docs

site/doc/pages/1_CLI.txt

@@ -5,6 +5,7 @@ CLI
 CLI(Request& context)
 
 :see
+>ob
 >1_RENDER
 >1_COMPONENT
 >1_WS
@@ -23,17 +24,9 @@ The default CLI socket path is `/run/uce/cli.sock` and is configured with `CLI_S
 
 Example convenience script usage:
 
-```sh
-scripts/uce-cli /tests/cli.uce
-scripts/uce-cli /tests/cli.uce action=echo message=hello
-scripts/uce-cli --json '{"action":"echo","message":"hello"}' /tests/cli.uce
-```
 
 Equivalent curl probe:
 
-```sh
-curl --unix-socket /run/uce/cli.sock http://localhost/tests/cli.uce
-```
 
 For structured commands, prefer JSON POST bodies. The `scripts/uce-cli` helper sends `key=value` parameters as JSON POST by default, while still allowing `--get` for simple query-string probes.
 
@@ -48,20 +41,8 @@ CLI responses default to `text/plain; charset=utf-8`, but the handler may set he
 
 Use `cli_input(context)` to merge query parameters, form parameters, and JSON POST fields into one `DValue`.
 
-```cpp
-CLI(Request& context)
-{
-    DValue input = cli_input(context);
-    String action = first(input["action"].to_string(), "ping");
-    if(action == "ping")
-    {
-        print("ok\n");
-        return;
-    }
-
-    context.set_status(400, "Bad Command");
-    print("unknown action: ", action, "\n");
-}
-```
 
 `ONCE(Request& context)` runs before `CLI()` in the same way it runs before render and component entrypoints. `INIT(Request& context)` runs when the unit is loaded into a worker.
+
+:example
+print("CLI is a unit directive; place it at top level in a .uce unit.\n");