docs(web): align package layout — move tutorials/web.md to web/README.md

Mirror the rosocket/ layout: rosocket/README.md is the package-shaped reference for the rosocket subpackage, so rclnodejs/web's user-facing guide should live at web/README.md too. Same content, just renamed (git tracks it as a rename, history preserved).

- tutorials/web.md → web/README.md (292 lines, no content change beyond intro link)
- README.md cross-refs updated (Get-started row + 'Browser ↔ ROS 2' bullet)
- tutorials/README.md entry now points at ../web/README.md
- web/README.md intro path adjusted from 'web/client.js' to './client.js' since the doc is now next to the source
- See-also section in web/README.md drops 'web/client.js' → './client.js'

This also gives npmjs.com/package/rclnodejs/web a real rendered landing page (npm renders subpath READMEs), matching what's been true for rosocket since 2.0.0-beta.0.

Author: minggangw

README.md

@@ -30,7 +30,7 @@ This example assumes your ROS 2 environment is already sourced.
 ## Documentation
 
 - Get started:
-  [Installation](#installation), [Quick Start](#quick-start), [Web SDK guide](./tutorials/web.md), [Tutorials](./tutorials/)
+  [Installation](#installation), [Quick Start](#quick-start), [Web SDK guide](./web/README.md), [Tutorials](./tutorials/)
 - Reference:
   [API Documentation](https://robotwebtools.github.io/rclnodejs/docs/index.html), [Using TypeScript](#using-rclnodejs-with-typescript), [ROS 2 Interface Message Generation](#ros-2-interface-message-generation)
 - Features:
@@ -115,7 +115,7 @@ More runnable examples in [example/](https://github.com/RobotWebTools/rclnodejs/
 `rclnodejs` ships **two** browser ↔ ROS 2 bridges — pick one based on
 how much glue you want to write.
 
-- **[`rclnodejs/web`](./tutorials/web.md)** — **typed, allow-listed,
+- **[`rclnodejs/web`](./web/README.md)** — **typed, allow-listed,
   curl-able** browser ↔ ROS 2. A `web.json` file is your public API;
   the browser SDK types `call` / `publish` / `subscribe` end-to-end
   from rclnodejs's auto-generated message maps; and

tutorials/README.md

@@ -42,7 +42,7 @@ Reduce network traffic and improve performance by filtering messages at the DDS
 
 Use RxJS Observables for reactive programming with ROS 2 subscriptions. Apply operators like `throttleTime()`, `combineLatest()`, and `filter()` to process message streams declaratively.
 
-#### [rclnodejs/web — Browser SDK guide](web.md)
+#### [rclnodejs/web — Browser SDK guide](../web/README.md)
 
 Front-end developer guide to talking to ROS 2 from a web app using `rclnodejs/web` and the bundled `rclnodejs-web` CLI. Covers the `connect()` URL forms (WebSocket vs. HTTP vs. split endpoints), the typed verb API (`call` / `publish` / `subscribe`) with single-string-generic typing derived from generated `MessagesMap` / `ServicesMap`, the `"42n"` BigInt convention, structured error codes, and curl recipes.
 

tutorials/web.md web/README.mdtutorials/web.md renamed to web/README.md

@@ -3,7 +3,7 @@
 > Talk to ROS 2 from a web app — typed, allow-listed, no `roslibjs`.
 
 `rclnodejs/web` is the browser-side of `rclnodejs`: a compact ESM
-module (`web/client.js`) plus a server runtime (`bin/rclnodejs-web.js`)
+module (`./client.js`) plus a server runtime (`../bin/rclnodejs-web.js`)
 that exposes a declarative subset of your ROS 2 graph over WebSocket
 **and** plain HTTP. The browser API is three verbs — `call`,
 `publish`, `subscribe` — typed end-to-end from rclnodejs's
@@ -282,7 +282,7 @@ narrow, declarative contract.
 
 ## See also
 
-- [`web/client.js`](../web/client.js) — the SDK source, worth a skim.
+- [`client.js`](./client.js) — the SDK source, worth a skim.
 - [`demo/web/javascript/`](../demo/web/javascript/) — runnable demo,
   no build tools, transport toggle + curl recipes.
 - [`demo/web/typescript/`](../demo/web/typescript/) — same demo with