Commit 646a40e
fix(consults): log positive proof when a cross-Enterprise forward fires (8th-layer#36) (#261)
The L2-to-L2 consult forward path only logged on failure (non-2xx peer
response or transport error). A successful forward was silent — so when
a peer reply never arrived, there was no way to tell a dropped forward
from a slow/absent peer-side auto-responder.
Add an INFO log on the success branch of all three forward paths
(_forward_request, _forward_message, _x_enterprise_forward_request),
recording peer l2_id, thread_id, and peer status. Source-side proof the
forward left this L2, separate from any peer-side delay.
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>1 parent 3a1295d commit 646a40e
1 file changed
Lines changed: 27 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
249 | 249 | | |
250 | 250 | | |
251 | 251 | | |
| 252 | + | |
| 253 | + | |
| 254 | + | |
| 255 | + | |
| 256 | + | |
| 257 | + | |
| 258 | + | |
| 259 | + | |
| 260 | + | |
252 | 261 | | |
253 | 262 | | |
254 | 263 | | |
| |||
285 | 294 | | |
286 | 295 | | |
287 | 296 | | |
| 297 | + | |
| 298 | + | |
| 299 | + | |
| 300 | + | |
| 301 | + | |
| 302 | + | |
| 303 | + | |
288 | 304 | | |
289 | 305 | | |
290 | 306 | | |
| |||
393 | 409 | | |
394 | 410 | | |
395 | 411 | | |
| 412 | + | |
| 413 | + | |
| 414 | + | |
| 415 | + | |
| 416 | + | |
| 417 | + | |
| 418 | + | |
| 419 | + | |
| 420 | + | |
| 421 | + | |
| 422 | + | |
396 | 423 | | |
397 | 424 | | |
398 | 425 | | |
| |||
0 commit comments