CoCoFlow 0.4.3 release notes
CoCoFlow 0.4.3 was released on October 15, 2026.
- Release tag:
v0.4.3 - Package history:
CHANGELOG.md
State mailboxes and delayed events
Section titled “State mailboxes and delayed events”Host-local ICoCoEventInboxAdapter<TEvent> components filter external unmanaged struct events. Logic reads discrete mail through context.Inbox, frozen at the Tick boundary, independently of business Intents. Multiple Adapters and event types can share one Host.
context.Outbox.Publish(in payload) snapshots a struct event and publishes its original type through the ordinary EventBus only after the whole Tick commits successfully. Failure/cancellation publishes nothing; sending requires no Adapter or per-event Binding.
Progress and Conditions
Section titled “Progress and Conditions”[CoCoState("Attack", ProvidesActionProgress = true)] works for ordinary and Config/Memory states. Independent [Condition] classes are discovered, registered with empty config, and factory-bound automatically. Each must be concrete, non-generic, derive from CoCoStateCondition, implement ICoCoStateConditionEvaluator, and have a public parameterless constructor (implicit is sufficient).
Conditions evaluate requested transitions; they do not request them. Progress reaching 1 does not request or complete a transition. The registration source defines the full declaration requirements.
Runtime boundaries
Section titled “Runtime boundaries”- Direct Adapters must stay inside their Host boundary, excluding nested-Host descendants.
- Running accepts direct mail; Suspended/Previewing drops arrivals. Full per-type queues drop new mail without Host Fault.
- Reads do not consume mail, views expire after their State callback, and the next Tick replaces the batch.
- Rejected Temporal calls preserve pending direct mail. Calls reaching Temporal execution still advance
InputAuthorityRevision; successful operations clear mail. - Serialized zero capacity retains no direct mail only when the Graph has no legacy Event declarations. Legacy/mixed Graphs require positive capacity; the Host Inspector minimum stays 1.
- Existing Event-to-Intent and Operator Packet paths remain supported. The Config/Memory runtime generic binding path remains unverified in an IL2CPP Player.