tutuca 0.13.0 → 0.13.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tutuca",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "type": "module",
   "description": "SPA framework with Immer-powered immutable state and virtual DOM",
   "main": "./dist/tutuca.js",

package/skill/tutuca/core.md

@@ -808,9 +808,11 @@ return nothing (or return `draft`) to commit. Return any other value to swap
 the addressed component for that value. Mutating the draft and returning a
 replacement in the same handler is an error. An unchanged recipe preserves
 the current identity. Routes,
-`ctx.reply` / `ctx.fail` / `ctx.forward` / `ctx.stop`, the three
-outcomes, `ctx.at`, the `$unknown` fallback, and intent-handler
+`ctx.reply` / `ctx.fail` / `ctx.forward` / `ctx.stop` / `ctx.sendReply`, the
+three outcomes, `ctx.at`, the `$unknown` fallback, and intent-handler
 registration are in [messages-and-intents.md](./messages-and-intents.md);
+`ctx.lookupType` (and the routes it shares with `ctx.intent`) is in
+[advanced.md](./advanced.md);
 worked snippets in
 [patterns/coordinate-components.md](./patterns/coordinate-components.md).
 

package/skill/tutuca/testing.md

@@ -223,7 +223,7 @@ the view actually wires these handlers correctly, use
 
 ## Designing handlers so tests stay simple
 
-Tutuca templates resolve handler args by name (see
+Tutuca templates resolve each handler arg from its sigil (see
 [core.md](./core.md) *Event Handling*). When you author a handler,
 **pick the most specific args you need; don't take broad event
 reads**. With narrow args, the test passes a literal; with `e.target`