rename packages, refactor out tailwind compiler,

go/cmd/examples/go-wasm-web/README.md

@@ -33,10 +33,30 @@ a `static` route, and fetching only exists on the client, so the fetches no-op
 during SSR: the server pre-renders the page's **spinner**, and the client runs
 them for real after hydration.
 
-Styling is **Tailwind**: the dev server (and `build.sh`) run `kjol/cmd/twcss`,
-which scans the Go markup + the `webui` kit for utility classes and compiles
-`css/app.css` → `wwwroot/app.css` with kjol's native Tailwind v4 engine. There is
-**no Bootstrap and no hand-written CSS**. (`build.sh` does a one-off build.)
+Styling is **Tailwind**: the build runs `kjol/cmd/twcss`, which scans the Go markup +
+the `webui` kit for utility classes and compiles `css/app.css` → `wwwroot/app.css` with
+kjol's native Tailwind v4 engine (`kjol/tw`). There is **no Bootstrap and no
+hand-written CSS**.
+
+Saving a `.css` file recompiles **only** Tailwind and swaps the stylesheet into the live
+page — no wasm rebuild, no reload, no lost state. Saving a `.go` file does the full
+rebuild and hot-swaps the wasm.
+
+## Building
+
+The build is Go, not a shell script — `buildsteps/` holds the four steps (codegen →
+Tailwind → wasm → `wasm_exec.js` shim), and both the one-off build and the dev server's
+watch loop call the *same* functions, so they cannot drift apart.
+
+```
+go run ./build      # one-off: codegen + Tailwind + wasm + shim
+go run ./server     # dev server: does the same build, then watches and hot-reloads
+```
+
+In VS Code these are the `gowasm: build` and `gowasm: dev server (hot reload)` tasks;
+both run through `gowasm: prebuild` (codegen + Tailwind), which is also the
+`preLaunchTask` of the debug configs — under the debugger the binary is built by Delve,
+so nothing else would generate `app/*.gen.go`.
 
 ## This is a separate module