Release v0.17.0
Summary
Wolverine event writes are now attributed to the exact current or legacy stream parameter that receives them instead of flattening multi-stream workflows onto a first aggregate.
Added
- Retain independent same-model and different-model stream bindings, identities, reads, and appends. (#4)
- Discover exact receiver-bound
AppendOneand safe directAppendManypayloads while reporting unresolved opaque writes asWOLVERINE0013. (#4) - Retain commandless HTTP, metadata-only loaded streams, current and legacy stream APIs, and deterministic conventional-version ambiguity. (#4)
- Exclude authored saga-state return slots before event, response, and cascade classification without inventing saga workflow facts. (#4)
- Add pinned canonical two-stream evidence and relationship-count assertions. (#4)
Fixed
- Prevent first-stream event and identity leakage across multiple targets. (#4)
- Prevent generated source and unrelated same-named identity/stream APIs from originating semantics. (#4)
- Preserve ordinary HTTP responses, cascades, side effects, messages, and unmarked-stream boundaries separately from persisted events. (#4)