* Engine-only: register the catch-up sync promise so the next `execute()` * call awaits it before serving. The handler swallows rejections (the * engine logs them) so a sync failure never propagates as a tool error; * we still want to serve a best-effort result over the same potentially-
(p: Promise<void> | null)
| 834 | * stale data, which is what would have happened without the gate. |
| 835 | */ |
| 836 | setCatchUpGate(p: Promise<void> | null): void { |
| 837 | this.catchUpGate = p; |
| 838 | } |
| 839 | |
| 840 | /** |
| 841 | * Await the catch-up gate, but no longer than the configured timeout (#905). |
no outgoing calls
no test coverage detected