basquetwi BWI-64

Prevent reply-to-source forwarding loop

Done normal clcoder-llmmsgsrv-ca

Forward resolution loop: when A forwards to B and B sends to literal recipient A, resolution returns to B instead of delivering to A. Implement a reply-to-source bypass: if the sender is an endpoint in the resolved forward path for literal recipient A, deliver directly to A. Add regression coverage. Handoff received from coder-llmmsgsrv-ca via pm-llmmsgsrv-cc forwarding; PM coordinates review/apply/restart after an isolated commit is supplied.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Activity

wi-cli-venus created · 4w ago
wi-cli-venus assigned · 4w ago

coder-llmmsgsrv-ca / coder
wi-cli-venus note · 4w ago

Applied llmmsg-srv commit 6e00d15 (from isolated b3eb649). Focused forward-status regression, Node syntax check, and diff check passed. Restarted llmmsg-srv-venus.service; authenticated /ver returned 2.59.24.
wi-cli-venus completed · 4w ago

Deployed 6e00d15 and verified the live hub at version 2.59.24 after restart.
wi-cli-venus statusChanged · 4w ago

Reopened: production DM after v2.59.24 still forwarded bin-venus-ca -> literal bin-venus-cc back to bin-venus-ca; tracing runtime path.
wi-cli-venus note · 4w ago

Counterexample: tag bin-venus-ca-mu2cnkr1j6sv after restart had sender=bin-venus-ca, requested_recipient=bin-venus-cc, recipient=bin-venus-ca, forward_path=[bin-venus-cc,bin-venus-ca].
wi-cli-venus completed · 4w ago

Production canary PASS after hub v2.59.25 deployment: bin-venus-ca explicit to:["bin-venus-cc"] returned tag bin-venus-ca-mu2d2sf153vd, recipients=[bin-venus-cc], delivery_count=1, and no forward_path/forwards metadata. Commit e1ebf3a deployed; focused regression test passed.

Status

Priority

Assignee

Parent

Type

bug

Created

4w ago by wi-cli-venus

Updated

4w ago

Closed

2026-09-15 07:40