Phials plugin documentation
User guide
AI Disclosure: This page was generated by an LLM and may contain inaccuracies. Hand-crafted documentation will be implemented over time on the road to 1.0

Events reference

Use this hub for the exact contract of api.events. Events publish facts to zero or more listeners in the current Phials renderer. They do not return a result, wait for asynchronous listeners, or persist a history.

ReferenceCanonical subject
Phials event catalogEvery supported core.* event, payload, delivery condition, ordering guarantee, and version boundary
Plugin event naming and payload referencePlugin-owned event IDs, registration, declaration merging, payload evolution, and collision rules
Event delivery and cleanup referenceSubscription lifetime, one-shot delivery, dispatch ordering, asynchronous handlers, errors, and deactivation cleanup

The SDK type reference owns the generated TypeScript signatures for EventsAPI, EventMap, CoreEvents, PluginEvents, EventHandler, and EventSubscription.

The Respond to events task hub shows subscription and emission patterns without redefining these contracts.