Per-profile adapter settings and Discord thread ownership fixes
Cluster 109475. Data as of
Nothing open on GitHub. Fix merged in #110293 on 13 Sep 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 #110293. 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 per-profile configuration resolution ordering for platform adapters and a specific Discord issue where transport owner context was lost, causing auto-thread rename logic to be skipped under shared-token profile routing.
Open issues0
Open PRs0
Fixes on record
-
#110293 fix(platforms): per-profile adapter settings resolve env → own YAML → default under multiplex (#108440 review, salvage #109036 #109477 #110109 #110111 #110131)
files:
gateway/authz_mixin.py,gateway/platforms/_shared.py,gateway/platforms/base.py,gateway/platforms/weixin.py,gateway/platforms/yuanbao.py,gateway/run_topics.py,plugins/platforms/a2a/adapter.py,plugins/platforms/discord/adapter.py,plugins/platforms/feishu/adapter.py,plugins/platforms/matrix/adapter.py,plugins/platforms/slack/adapter.py,plugins/platforms/telegram/adapter.py,plugins/platforms/whatsapp/adapter.py,tests/gateway/test_adapter_settings_scoped_precedence.py,tests/gateway/test_matrix_recovery_key_scope.py,tests/gateway/test_session_title_rename_lane.py,tests/gateway/test_shared_platform_boilerplate.py,tests/gateway/test_slack_thread_require_mention.py,tests/gateway/test_telegram_group_gating.py,tests/gateway/test_telegram_polling_progress.py(+10 more)
1 PR closed without merging
From the close comments: done elsewhere 1
-
#109477 fix(discord): preserve transport owner for thread renames · done elsewhere →
b602ba2,fa787be,27180c8,996a9ac,77180ac,#110293,#109475
Closed issues · 1
- Closed#109475Discord auto-thread semantic rename skipped under shared-token profile routing
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
- #110293
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 13 Sep 2026