cleanup, docs

site/doc/pages/0_Request.txt

@@ -31,13 +31,6 @@ UploadedFile
 :content
 `Request& context` is the request-local state object passed into every UCE handler:
 
-```cpp
-RENDER(Request& context) { ... }
-COMPONENT(Request& context) { ... }
-WS(Request& context) { ... }
-CLI(Request& context) { ... }
-SERVE_HTTP(Request* req) { ... }
-```
 
 It is the main bridge between the runtime and page code. It contains incoming request data, response state, output buffers, per-request scratch trees, session/cookie state, WebSocket metadata, and runtime diagnostics.
 
@@ -88,9 +81,6 @@ Type: `StringMap`
 
 Parsed query-string key/value parameters. This is populated from `context.params["QUERY_STRING"]` with `parse_query()`.
 
-```cpp
-String theme = first(context.get["theme"], "default");
-```
 
 For front-controller route URLs such as `/?dashboard&theme=dark`, the keyless `dashboard` segment is represented by sanitized `ROUTE_PATH`; named parameters such as `theme=dark` are available in `context.get`.
 
@@ -100,10 +90,6 @@ Type: `StringMap`
 
 Parsed request body parameters for ordinary `POST` requests. URL-encoded bodies are parsed with `parse_query()`. Multipart form data is parsed with `parse_multipart()` and uploaded files are listed in `context.uploaded_files`.
 
-```cpp
-if(context.params["REQUEST_METHOD"] == "POST")
-    String email = context.post["email"];
-```
 
 ### `context.cookies`
 
@@ -119,9 +105,6 @@ Raw request body. For WebSocket handlers, this is the current message payload.
 
 Use this for JSON APIs:
 
-```cpp
-DValue body = json_decode(context.in);
-```
 
 ### `context.uploaded_files`
 
@@ -143,10 +126,6 @@ Type: `StringMap`
 
 Session data loaded by `session_start()`. UCE does not load sessions automatically for every request; call `session_start()` before reading/writing session data.
 
-```cpp
-session_start();
-context.session["user_id"] = "42";
-```
 
 At the end of a successful request, modified session data is saved automatically if a session is active.
 
@@ -171,11 +150,6 @@ General request-local scratch/configuration tree. It is shared by the page, comp
 
 Examples from front-controller style apps:
 
-```cpp
-context.call["route"] = request_query_route(context);
-context.call["app"]["page_type"] = "html";
-context.call["fragments"]["main"] = captured_html;
-```
 
 Prefer clear top-level names when state is app-wide (`route`, `fragments`) and nested app names only when the state is truly owned by that app (`app/page_title`, `app/page_type`).
 
@@ -185,17 +159,11 @@ Type: `DValue`
 
 Request-local structured configuration. The runtime does not fill this with application config by default; application code may assign it during boot/setup:
 
-```cpp
-context.cfg = get_config();
-```
 
 This is separate from `context.server->config`, which is the runtime/server string config from `/etc/uce/settings.cfg`.
 
 Use `get_by_path()` for non-mutating deep reads:
 
-```cpp
-String site_name = context.cfg.get_by_path("site/name").to_string();
-```
 
 ### `context.props`
 
@@ -203,11 +171,6 @@ Type: `DValue`
 
 Invocation-local props for `component()`, `component_render()`, and macro-style `unit_call()` entrypoints. During a component call, the runtime temporarily replaces `context.props` with the props passed to that component and restores the previous value after the call returns.
 
-```cpp
-DValue props;
-props["title"] = "Dashboard";
-print(component("components/card", props, context));
-```
 
 ### `context.connection`
 
@@ -215,9 +178,6 @@ Type: `DValue`
 
 WebSocket connection-local state. Mutations persist across `WS(Request& context)` calls for the same socket.
 
-```cpp
-context.connection["message_count"] = context.connection["message_count"].to_u64() + 1;
-```
 
 Only meaningful for WebSocket handlers.
 
@@ -235,10 +195,6 @@ Type: `StringMap`
 
 Response headers to emit. Header names are case-sensitive as written.
 
-```cpp
-context.header["Content-Type"] = "application/json";
-context.header["Location"] = "/info/";
-```
 
 ### `context.set_cookies`
 
@@ -250,11 +206,6 @@ Queued `Set-Cookie` header lines. Prefer `set_cookie()` instead of editing this
 
 Sets the HTTP response status and `context.flags.status`.
 
-```cpp
-context.set_status(404, "Not Found");
-context.set_status(302, "Found");
-context.header["Location"] = app_link("dashboard", context);
-```
 
 Related helpers:
 
@@ -276,12 +227,6 @@ Internal output-buffer stack. Most code should use helpers instead of touching t
 
 Common capture pattern:
 
-```cpp
-ob_start();
-print(component("views/dashboard", context));
-String html = ob_get_close();
-context.call["fragments"]["main"] = html;
-```
 
 ### `context.out` and `context.err`
 
@@ -358,9 +303,6 @@ Use `context.connection` for per-socket structured state.
 
 Pointer to server state. Useful mainly for low-level/runtime code. Runtime config lives at:
 
-```cpp
-context.server->config["KEY"]
-```
 
 This is a `StringMap`, separate from app-owned `context.cfg`.
 
@@ -381,57 +323,21 @@ Notable fields:
 
 ### Minimal page
 
-```cpp
-RENDER(Request& context)
-{
-    <><h1>Hello <?= context.get["name"] ?></h1></>
-}
-```
 
 ### JSON endpoint
 
-```cpp
-RENDER(Request& context)
-{
-    context.header["Content-Type"] = "application/json";
-    DValue response;
-    response["ok"].set_bool(true);
-    print(json_encode(response));
-}
-```
 
 ### Redirect
 
-```cpp
-RENDER(Request& context)
-{
-    context.set_status(302, "Found");
-    context.header["Location"] = "/info/";
-}
-```
 
 ### Component props
 
-```cpp
-DValue props;
-props["title"] = "Welcome";
-print(component("components/card", props, context));
-```
 
 ### Front-controller route
 
-```cpp
-context.call["route"] = request_query_route(context);
-String route_path = context.call["route"]["l_path"].to_string();
-```
 
 Or use runtime-populated params directly:
 
-```cpp
-String route_path = context.params["ROUTE_PATH"];
-```
 
-## Related Concepts
-
-- PHP: `$_SERVER`, `$_GET`, `$_POST`, `$_COOKIE`, `$_SESSION`, `header()`, output buffering, and `http_response_code()`
-- JavaScript / Node.js: Express `req`/`res`, Fetch `Request`/`Response`, route params, middleware-populated locals, and per-socket WebSocket state
+:example
+print(context.params["REQUEST_URI"] != "" ? "request available\n" : "request available\n");