fix(platforms): per-profile adapter settings resolve env → own YAML → default under multiplex (#108440 review, salvage #109036 #109477 #110109 #110111 #110131) - #110293

Merged

teknium1 merged 16 commits into

mainfrom

fix/mux-triage-adapter-config

Sep 13, 2026

Commits on Sep 13, 2026

fix(telegram): let an explicit TELEGRAM_REACTIONS beat the materialized YAML default

liuhao1024
authored and
teknium1
committed
d6d5145
fix(matrix): scope MATRIX_RECOVERY_KEY_OUTPUT_FILE under multiplex profiles

authored and
teknium1
committed
25d8c00
fix(weixin): scope split_multiline_messages under multiplex profiles

authored and
teknium1
committed
53c4412
fix(a2a): scope A2A_PUBLIC_URL per multiplex profile

authored and
teknium1
committed
49eac34
fix(discord): preserve transport owner for thread renames

benjamin-rousseau-shift
authored and
teknium1
committed
42e0735
style(discord): trim rename comments

benjamin-rousseau-shift
authored and
teknium1
committed
09fbf4b
fix(platforms): adapter settings resolve explicit env → own YAML → default, per profile
teknium1
committed
ac44aa5
fix(telegram): a secondary profile's YAML proxy_url reaches request construction without an env bridge
teknium1
committed
414ba4a
fix(gateway): the central allow_bots grant honours a secondary profile's YAML policy
teknium1
committed
3402677
fix(yuanbao): auto-sethome persists platforms.yuanbao.home_channel and updates the live config
teknium1
committed
8e8bb4d
fix(whatsapp): bridge.js runs the adapter's effective dm_policy / allow_from, not the launch env's
teknium1
committed
a94a91f
test(gateway): invariant tests for per-profile setting precedence and its consumers
teknium1
committed
22e22f7
test: trim salvaged test additions to two invariants each
teknium1
committed
0f123d5
docs: state the per-profile setting precedence rule (env → own YAML → default)
teknium1
committed
c8ba86a
fix(telegram): ignored_threads and mention_patterns read scoped env → own YAML like every sibling
teknium1
committed
eaf5b62
test(whatsapp): an explicit empty free_response_chats list is asserted without an explicit env value
teknium1
committed
021100b

Navigation Menu

fix(platforms): per-profile adapter settings resolve env → own YAML → default under multiplex (#108440 review, salvage #109036 #109477 #110109 #110111 #110131) - #110293

fix(platforms): per-profile adapter settings resolve env → own YAML → default under multiplex (#108440 review, salvage #109036 #109477 #110109 #110111 #110131)#110293
teknium1 merged 16 commits into
mainfrom
fix/mux-triage-adapter-config

Commits on Sep 13, 2026

fix(telegram): let an explicit TELEGRAM_REACTIONS beat the materialized YAML default

fix(matrix): scope MATRIX_RECOVERY_KEY_OUTPUT_FILE under multiplex profiles

fix(weixin): scope split_multiline_messages under multiplex profiles

fix(a2a): scope A2A_PUBLIC_URL per multiplex profile

fix(discord): preserve transport owner for thread renames

style(discord): trim rename comments

fix(platforms): adapter settings resolve explicit env → own YAML → default, per profile

fix(telegram): a secondary profile's YAML proxy_url reaches request construction without an env bridge

fix(gateway): the central allow_bots grant honours a secondary profile's YAML policy

fix(yuanbao): auto-sethome persists platforms.yuanbao.home_channel and updates the live config

fix(whatsapp): bridge.js runs the adapter's effective dm_policy / allow_from, not the launch env's

test(gateway): invariant tests for per-profile setting precedence and its consumers

test: trim salvaged test additions to two invariants each

docs: state the per-profile setting precedence rule (env → own YAML → default)

fix(telegram): ignored_threads and mention_patterns read scoped env → own YAML like every sibling

test(whatsapp): an explicit empty free_response_chats list is asserted without an explicit env value