Do you envision an A2A adapter for Jido, with DASP handling durable execution underneath? I’d be curious how an uncertain outcome would map to an A2A task state.
The `uncertain` mapping isn't clean. DASP treats it as terminal: the host can't prove whether effects occurred, so it must not retry. A2A's `TASK_STATE_UNSPECIFIED` is indeterminate, but not terminal. The adapter must preserve the DASP outcome in metadata and map it conservatively, likely to `FAILED`.