Files
paseo/packages
paseo-bot 163b6df4b3 fix(omp): keep a prompt's client correlation until OMP echoes it
An OMP prompt's client correlation lived on the active turn, so any turn
completion that landed before OMP echoed the prompt cleared it. The echo
then arrived untagged, the manager could not match it to the submission
it belonged to, and recorded it as a second user row.

Two paths reach it: an interrupt-and-replace where OMP flushes the
aborted turn's agent_end after the replacement turn started, and a
custom message that completes a turn before the prompt is echoed.

Correlations now belong to the dispatched prompt and are claimed by the
echo that emits them, so the same text on different turns stays separate
and a re-emitted frame cannot steal a later submission's id.
2026-09-22 20:01:27 +02:00
..
2026-09-22 12:25:40 +02:00
2026-09-22 12:25:40 +02:00
2026-09-22 12:25:40 +02:00
2026-09-22 12:25:40 +02:00
2026-09-22 12:25:40 +02:00
2026-09-22 12:25:40 +02:00
2026-09-22 12:25:40 +02:00
2026-09-22 12:25:40 +02:00