Participant-directed injects must connect actual world execution, optional participant delivery, and any authored control transition without conflating their outcomes.
Acceptance criteria
- Integrate the revised DSL-142 and API-409 bindings with the general inject-trigger path. Validate recipient and control-occurrence coordinates only where the authored variant requires them.
- Keep world execution, disclosed content, participant delivery/observation, and direction/intervention outcomes distinct and durably correlated.
- Apply accepted ordering, validity, authorization, and failure semantics when an inject and control transition are related. A successful world effect cannot manufacture participant observation or a successful control change.
- Verify ordinary directed delivery, repeated direction/intervention cycles, stale or unauthorized bindings, and partial failures through the public runtime. General injects remain valid without participants.
Prerequisites: #1364, #1367.
References: Environment and inject diagnosis.
Participant-directed injects must connect actual world execution, optional participant delivery, and any authored control transition without conflating their outcomes.
Acceptance criteria
Prerequisites: #1364, #1367.
References: Environment and inject diagnosis.