mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-09-28 06:45:17 +08:00
liuhao1024
00c8e5ca48
Since the questions[]-only schema (#95907) every single question is a one-entry batch on both the tool args and the gateway wire, yet no test exercised that shape (called out in #98645). Lock the behavior down at both layers: - unit: a one-entry batch renders the batch card (not a blank/spinner single card) both with the wire already parked and when the request lands after the tool row, and answers with the qid-keyed lock - e2e: a SINGLE_BATCH trigger drives the real chain (composer -> gateway -> agent -> clarify tool -> clarify.request -> renderer) through mount, pick, confirm, and settle for questions.length === 1 The e2e mock's trigger routing also learns to scope its has-tool-result guard to the answering turn's own question text: the existing any-tool- result check would false-positive once a second scripted clarify shares the conversation history. Adapted to main: the mock server now lives in tests-js/scripts, and a batch confirm answers with clarify.lock.