@rotorsoft/act 1.32.26 → 1.32.27

package/README.md

@@ -71,7 +71,7 @@ import { projection, slice } from "@rotorsoft/act";
 // Projection — read-model updater. Handlers receive (event, stream).
 const CounterProjection = projection("counters")
   .on({ Incremented: z.object({ amount: z.number() }) })
-    .do(async ({ stream, data }) => { /* update read model */ })
+    .do(async function updateCounter({ stream, data }) { /* update read model */ })
   .build();
 
 // Slice — partial state + scoped reactions. Handlers receive (event, stream, app).
@@ -79,7 +79,7 @@ const CounterSlice = slice()
   .withState(Counter)
   .withProjection(CounterProjection)
   .on("Incremented")
-    .do(async (event, _stream, app) => { /* dispatch via app */ })
+    .do(async function dispatchCounter(event, _stream, app) { /* dispatch via app */ })
     .to("counter-target")
   .build();
 
@@ -155,7 +155,6 @@ Public API governed by the [Act Stability Charter](../../STABILITY.md). The char
 - **[Architecture](https://rotorsoft.github.io/act-root/docs/architecture)** — concurrency model, cache + snapshots, correlation + drain, cross-process reactions, priority lanes, close-cycle, schema evolution, extension points.
 - **[Guides](https://rotorsoft.github.io/act-root/docs/intro)** — production checklist, projections to database, external integration, writing a custom store/cache/logger, contributing a new package, contracts CLI.
 - **[PERFORMANCE.md](./PERFORMANCE.md)** — measured throughput numbers, optimization history, and the reaction-latency benchmark answering "how long from `do()` to reaction firing?"
-- **[BENCH.md](../../BENCH.md)** — index of every benchmark in the workspace with run commands.
 
 ## License