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
This commit is contained in:
slhx agent
2026-06-02 03:28:53 +02:00
parent 9fd614f86d
commit 417bc45d1f
3 changed files with 5 additions and 5 deletions
+2 -2
View File
@@ -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`.