docs(examples): describe generated command path

Keep example READMEs aligned with the generated-resource, tuple-composed IntoEffect authoring path instead of lower-level handle/EffectBatch wording.

req: dx/006

req: examples/003

examples/kanban/README.md

@@ -11,8 +11,8 @@ The example is a server-first Kanban board with:
 - add-card form
 - move-left / move-right card controls
 - delete-card controls
-- generated handles and slots
-- application/slhx EffectBatch responses
+- generated resource commands for checked slot updates
+- tuple-composed `IntoEffect` / `application/slhx` responses
 - SSE presence updates
 
 It intentionally uses buttons instead of custom JavaScript drag-and-drop; drag/local-first sync remain north-star features in `examples/kanban.md`.

examples/techdemo/README.md

@@ -11,8 +11,8 @@ This is a polished Linear-style product demo for planning typed work across lane
 - modern SSR-first UI
 - generated resource modules from `.heml`
 - hemplate partials for issue lanes, cards, and inspector panels
-- native form posts carrying generated slhx handle fields
-- multi-target `application/slhx` EffectBatch responses
+- native form posts wired through generated slhx handles
+- multi-target tuple-composed `IntoEffect` / `application/slhx` responses
 - generated slot updates instead of selectors
 - root-scoped runtime lowering (`data-hid`, `data-sid`)
 - page-enhancer navigation with native link fallback

examples/v0/README.md

@@ -8,7 +8,7 @@ cargo run -p slhx-v0-examples
 
 Open <http://127.0.0.1:3000>.
 
-The page includes working examples for:
+The page includes working examples for generated-resource, server-first UI commands:
 
 - counter updates
 - todo form submission