@yeaft/webchat-agent 0.1.788 → 0.1.790

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeaft/webchat-agent",
-  "version": "0.1.788",
+  "version": "0.1.790",
   "description": "Remote agent for Yeaft WebChat — connects worker machines to the central server",
   "main": "index.js",
   "type": "module",

package/unify/engine.js

@@ -1782,7 +1782,7 @@ export class Engine {
 
         // PR-L: T2 end-of-turn (asynchronous) reflection. Fires when the
         // total tool count for this query() exceeds TURN_SUMMARY_THRESHOLD
-        // (5) AND no T1 has actually rewritten the arc yet. Kicks off the
+        // (8) AND no T1 has actually rewritten the arc yet. Kicks off the
         // primary-model call without await; the next query()'s
         // `#applyPendingT2Reflections` carries the result forward.
         //

package/unify/tool-folding/index.js

@@ -10,16 +10,30 @@
  *
  * The constants are NOT config-driven — V7 design freezes them in code.
  *
+ * Invariant: TURN_SUMMARY_THRESHOLD < TOOL_BATCH_SIZE. T1 runs inside the
+ * turn and collapses history in place; T2 fires at end_turn and is gated
+ * by `t1CollapsesDone === 0` (engine.js). If T2 were ever set ≥ T1, T1
+ * would collapse first and T2 could never fire — silently disabling the
+ * end-of-turn reflection path. Keep a usefully wide gap between the two
+ * so the (T2, T1) band where T2-alone applies stays meaningful.
+ *
  * TOOL_BATCH_SIZE history: was 13 originally; raised to 30 (2026-05-15)
  * after user feedback that 13 fired too often inside a single task and
  * fragmented otherwise-coherent tool arcs into multiple reflections. 30
  * keeps the periodic-reflection contract (it still fires every N tools,
  * not just once) but gives a single task arc room to breathe before the
  * arc gets collapsed.
+ *
+ * TURN_SUMMARY_THRESHOLD history: was 5 originally; raised to 8
+ * (2026-05-18). 5 was too aggressive — small "read a few files, edit one,
+ * run tests" turns crossed it and produced a T2 reflection card the user
+ * didn't want. 8 lets short-to-medium turns finish without a reflection
+ * while still folding the long ones that genuinely benefit from a summary
+ * before the next turn's history grows.
  */
 
 export const TOOL_BATCH_SIZE = 30;
-export const TURN_SUMMARY_THRESHOLD = 5;
+export const TURN_SUMMARY_THRESHOLD = 8;
 export const DUP_TOOL_THRESHOLD = 3;
 
 export { ExecLog, buildEntry, argsHashOf } from './exec-log.js';

package/unify/tools/route-forward.js

@@ -109,9 +109,11 @@ Returns JSON: { ok, dispatched?, error?, detail? }.`,
     // task-707: hand off control. Successful forward means the originating
     // turn should NOT continue generating — the target VPs are now in
     // charge. Signal the engine to break the tool-loop after this batch.
-    // The structured payload feeds web-bridge's `group_handoff` UX event
-    // so the frontend can render "↪ 已转交给 @vp-x、@vp-y" without
-    // re-parsing a string.
+    // The structured payload lands on `turn_end.detail` as audit metadata
+    // (kind, fromVpId, dispatched, broadcast, text, reason); the frontend
+    // renders the hand-off as a Route tool chip from the tool_call
+    // envelope already on the wire (see PR #793 — the previous
+    // `group_handoff` UI event was removed when its single consumer was).
     if (typeof ctx.requestEndTurn === 'function') {
       try {
         ctx.requestEndTurn({

package/unify/web-bridge.js

@@ -1404,34 +1404,14 @@ function handleEngineEvent(event, hctx) {
       break;
 
     case 'turn_end':
-      // When a tool (currently only `route_forward`) signals
-      // requestEndTurn, the engine emits turn_end with
-      // stopReason='tool_handoff' and a structured `detail` payload.
-      // Surface that to the frontend as a `group_handoff` event so the
-      // originating VP's bubble can render "↪ 已转交给 @vp-b、@vp-c".
-      // Other turn_end variants are ignored (the outer loop handles
-      // result/end_turn semantics already).
-      //
-      // The `version` field is the wire schema version. Today there is
-      // only one shape. Future variants (e.g. a second hand-off tool)
-      // can bump it without breaking older frontends — they ignore
-      // unknown versions.
-      if (event.stopReason === 'tool_handoff' && event.detail && typeof event.detail === 'object') {
-        const detail = event.detail;
-        if (detail.kind === 'route_forward') {
-          sendUnifyEvent({
-            type: 'group_handoff',
-            version: 1,
-            kind: 'route_forward',
-            fromVpId: detail.fromVpId || hctx.vpId,
-            toVpIds: Array.isArray(detail.dispatched) ? detail.dispatched.slice() : [],
-            broadcast: Boolean(detail.broadcast),
-            text: typeof detail.text === 'string' ? detail.text : '',
-            reason: detail.reason || null,
-            ts: Date.now(),
-          }, envelope);
-        }
-      }
+      // turn_end variants are handled by the outer loop (result /
+      // end_turn semantics). PR #793 removed the `group_handoff`
+      // wire event that the frontend used to render a "↪ 已转交给"
+      // pill — the Route tool chip (rendered from the tool_call
+      // envelope already on the wire) is the single source of truth
+      // for hand-off UX. If a future feature (notification toast,
+      // typing-chain animation, …) needs the structured payload,
+      // re-emit a wire event here from `event.detail`.
       break;
 
     case 'usage':