Routed message scoping and history fixes in gateway
Cluster 92525. Data as of
Nothing open on GitHub. Fix merged in #95088 on 26 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #95088. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address how routed messages and their history are scoped in the gateway, ensuring routed turns read the correct profile's history and that primary-adapter messages are scoped to the appropriate routed profile rather than the wrong context.
Open issues0
Open PRs0
Fixes on record
-
#95088 fix(gateway): routed turns read the routed profile's history, auth stays with the transport owner (salvage #94848)
files:
contributors/emails/[redacted:email],gateway/run.py,tests/gateway/test_multiplex_session_db_profile_scope.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#92527 fix(gateway): scope a routed primary message to the profile it routes to · done elsewhere →
2afed50,9ab748a,#95088
Closed issues · 1
- Closed#92525Routed primary-adapter messages are scoped to the multiplexer's home, not the routed profile
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #95088
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 26 Aug 2026