Skip to content

conformance(v1): the served gate question records reply after the send - #9

Closed
sanctrl wants to merge 1 commit into
mainfrom
fix/receive-texts
Closed

sanctrl wants to merge 1 commit into
mainfrom
fix/receive-texts

Conversation

@sanctrl

@sanctrl sanctrl commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

What

conformance/v1/tray.sample.json carries a copy of the server's gate question, and gate-prompt.expected.txt is its rendering. Both now match the question served after agentchat-platform/agentchat#152:

  • defer: "and say when to look again" → "The server owns the reminder: your first defer brings the conversation back in 15 minutes, a second in 24 hours, a third stops the reminders until something new arrives." (the ladder has been server-owned since migration 082)
  • verdicts: "To reply, open the conversation and send; the send is the verdict." → "Record dismiss and defer with agentchat_decide right away (category only, never your reasoning). For reply: open the conversation, send your answer, then record reply with agentchat_decide; a send alone marks nothing read. If after reading you choose not to answer, record dismiss instead."

Why: a send marks nothing read (agentchat-platform/agentchat#121); a reply recorded before the send and a run that stops in between leaves a peer read and unanswered.

The tool-less triage preamble (gate.ts / gate.py) is unchanged. Read with the new question it still holds: it says not to call agentchat_decide, that the host records the verdicts from the JSON, and that recording and sending happen later, in the turn started for a reply — which is exactly when Hermes and OpenClaw record reply (end of a completed turn).

Both fixture files are byte-identical across agentchat-typescript and agentchat-python (cmp clean). No realtime file and no new scenario file is touched.

No release needed for the fixtures alone; they ride with the next SDK release.

Tests

ruff check src tests ✓ · mypy ✓ (28 files) · pytest -q ✓ 315 passed, 1 skipped (live smoke) — Python 3.12.

tray.sample.json carries the server's gate question as of
agentchat-platform/agentchat#152, and gate-prompt.expected.txt is its
rendering. Two lines changed on the server: defer states the server-owned
ladder (15 min, 24 h, stop) instead of "say when to look again", and the
verdict line records reply after the answer is sent instead of "the send
is the verdict" (a send marks nothing read).

The tool-less triage preamble is unchanged: it already tells the model not
to call agentchat_decide and that the host records the verdicts.

Byte-identical to agentchat-typescript's conformance/v1.
@sanctrl

sanctrl commented Nov 8, 2026

Copy link
Copy Markdown
Contributor Author

Folded into #12 (same reviewed head, merged conflict-free with the other two) so main gets one merge instead of three. Closing in favour of #12.

@sanctrl sanctrl closed this Nov 8, 2026
sanctrl added a commit that referenced this pull request Nov 8, 2026
…erved gate question fixtures (folds #9, #10, #11) (#12)

* conformance(v1): the served gate question records reply after the send

tray.sample.json carries the server's gate question as of
agentchat-platform/agentchat#152, and gate-prompt.expected.txt is its
rendering. Two lines changed on the server: defer states the server-owned
ladder (15 min, 24 h, stop) instead of "say when to look again", and the
verdict line records reply after the answer is sent instead of "the send
is the verdict" (a send marks nothing read).

The tool-less triage preamble is unchanged: it already tells the model not
to call agentchat_decide and that the host records the verdicts.

Byte-identical to agentchat-typescript's conformance/v1.

* fix(realtime): ack an already-handled repeat below the seq anchor; engine conformance scenarios

Default mode dropped a live message.new below the conversation's seq anchor
without an ack, even when this session had already dispatched that message
id. The delivery-ack protocol acknowledges every dedup hit (the earlier
dispatch is the proof), and the TypeScript SDK does. It is now acked again,
still without re-dispatch. A below-anchor frame no handler has seen is
unchanged: dropped unacked, the server re-offers it.

Adds conformance/v1/engine-scenarios.json, run in both modes by a new
harness (identical bytes ship in the TypeScript SDK): drain gap + close
during an earlier handler or inside the gap window, a raising handler during
a drain, and an already-handled repeat below the live anchor as a frame and
as a drain row. Also pins the drain-cursor rule for a socket drop during an
earlier handler with a regression test.

* test(conformance): drain gap with a socket drop during a later row's handler

Shared scenario (identical bytes in agentchat-typescript): page [g1, g3, h1],
h1's handler held, the socket drops, h1 released; the default-mode cursor
stops at g1. This drain awaits each handler while routing, so the drop lands
during a LATER row's handler and clears the parked g3 before the cursor is
computed. Copying a cursor that stops only while a row is still buffered
into _drain_row_ackable now fails this scenario and the reworked unit test
(the earlier-handler shape did not catch it).

CHANGELOG: say where the SDKs still differ on a below-anchor frame no
handler has seen.

* fix(realtime): never hand a message to the handlers twice while its first copy is running

After a reconnect the server pushes its stored backlog on the socket and the
REST drain brings the same rows. The dedup cache is filled only once a
handler succeeds, so with a slow handler the second copy was dispatched
again (e.g. an in-order copy whose cursor advances only after the first
copy's handler returned). _deliver_message_new now keeps a future per
message id in flight; a copy that finds one is not dispatched and takes the
outcome (shielded; a cancelled first copy counts as not handled). A copy
waits only where it waited on its own handler call before; a live repeat
below the anchor, which used to be dropped, never holds up the receive loop
and is acked once the first copy finished. Off with dedup_cache_size=0.

Also closes two races between concurrent copies: the per-conversation
cursor never moves backwards (_advance_past), and _cleanup_if_idle removes
only the state it was handed, never a newer connection's.

Shared scenarios repeat-while-handler-runs-in-order / -below-anchor
(identical bytes in agentchat-typescript).

* fix(realtime): a frame that parks while a gap is resolved is handed over, never cleared unseen

_resolve_gap and _flush_parked_frames snapshotted the buffer, awaited each
handler, then cleared it. The receive loop keeps running during those
awaits, so a frame that parked meanwhile was cleared without dispatch:
under ack_on_receipt (acked at receipt) it was never handled; in the
default mode it waited unacked for the next reconnect. A concurrent
in-order arrival could also pop entries the snapshot still expected
(KeyError in the gap task) or hand them over twice.

Both now pop each frame before handing it over, lowest seq first, and keep
going until nothing is parked (the flush across every conversation, since
disconnect() flushes before it closes the socket). The cursor advances past
each frame after its handler, never backwards.

Shared scenario frame-arrives-while-a-lapsed-gap-is-handled, with a new op
gap_window_lapses (identical bytes in agentchat-typescript).

* fix(realtime): progress beats dedup: nothing waits on another copy, gaps resolve on a snapshot

Review of #11. An in-flight repeat no longer waits for the first copy
anywhere: _adopt_in_flight records the outcome and returns. A live repeat
is acked when the first copy finished cleanly, never if it failed; a drain
row's cursor reads the outcome when computed and stops if the first copy is
not done (the next drain covers it as a dedup hit), so a slow or hung live
handler no longer holds up later drain rows, and a handler that awaits
disconnect() while a repeat of its own message arrives no longer
deadlocks. Adoption is per connection generation: a re-offer on a later
connection is dispatched afresh even if the first copy still runs.

_resolve_gap and the shutdown flush work on the frames parked when they
start; each frame leaves the buffer and the cursor moves past it before its
handler is awaited, so in-order arrivals go to the receive loop, a frame
behind a new hole gets its own gap window and report, and nothing is
cleared unseen (a state being resolved is never dropped as idle).
disconnect() stops taking frames in before it flushes, so it returns
promptly while frames keep arriving; a frame acked at receipt is never
dropped by the flush.

* fix(realtime): a gap fill acks nothing once disconnect() began; an adopted in-order repeat moves the cursor on

A gap fill whose fetch returned while disconnect() was flushing acked its
rows at receipt (ack_on_receipt), and the shutdown then cancelled the gap
task, possibly mid-handover: acked rows never handled. Once disconnect() has
begun, the fill now returns before acking (a gap fill marks nothing on the
server, which keeps the rows).

A live repeat that adopted a drain row still running its handler left the
cursor where it was, so the next live frame parked and opened a spurious gap
(a REST gap fill and a report 2 s later, though nothing was missing). The
in-order branch now moves the cursor on for an adopted copy exactly as for
a dispatch.

Docs: handlers in one conversation can overlap (they start in seq order),
as in the TypeScript SDK.
@sanctrl
sanctrl deleted the fix/receive-texts branch November 11, 2026 12:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant