# kcode-k1-codex-shim
This crate provides the sequential per-conversation bridge over `kcode-k1-codex-runtime` 0.3.0 and reexports its facade types.
`ToolCallLauncher<B>::launch_stage(text, boxes)` accepts one assistant-output stage: text accumulated since the preceding wave plus an ordered vector of converted tool-call boxes.
On the first tool call, `infer` nonblockingly drains only already-buffered consecutive calls into the same wave; it uses no timer and preserves the first non-call event as ordered lookahead.
Launcher success means all consumer-required work for the wave has completed, including optional active-turn flush, persistence, projection, steering, and commit. It is the complete pre-acknowledgement barrier.
Launcher failure can occur after durable wave acceptance or launch and does not certify replayability. The shim acknowledges none of that wave and remains unusable.
Calls that arrive only after an acknowledgement form later waves. Stage text and calls are not returned again. `ShimOutput` contains only assistant text accumulated after the final wave, or no items.
`ASYNC_TOOL_ACKNOWLEDGEMENT` is the exact successful native result. Available results may be supplied at a later inference boundary within the continuing native turn.
Externally recorded boxes prefix the next fresh turn and clear only after start acceptance. `close_conversation` is ready-only and retains pending boxes.
Tool execution, persistence, steering, scheduling, retries, and recovery remain outside this crate.