What happened?
extensions/slack/src/monitor/message-handler/prepare.thread-session-key.test.ts > thread-level session keys > routes configured ACP bindings for top-level Slack channels fails deterministically (locally on macOS and on a Linux Testbox, Node 24) with a deep-equality mismatch on the routed binding object (expected { …(3) } to deeply equal { …(3) }).
Context
Both the test and the Slack message-handler prepare code are unchanged relative to current main lineage (verified at 6683a86); the failure reproduces on a clean checkout, so this predates any in-flight branches. Likely broken by a recent change in the shared session-key or ACP-binding routing surfaces that the Slack test pins.
Reproduction
node scripts/run-vitest.mjs extensions/slack/src/monitor/message-handler/prepare.thread-session-key.test.ts → 1 failed / 15 passed.
What happened?
extensions/slack/src/monitor/message-handler/prepare.thread-session-key.test.ts > thread-level session keys > routes configured ACP bindings for top-level Slack channelsfails deterministically (locally on macOS and on a Linux Testbox, Node 24) with a deep-equality mismatch on the routed binding object (expected { …(3) } to deeply equal { …(3) }).Context
Both the test and the Slack message-handler prepare code are unchanged relative to current main lineage (verified at 6683a86); the failure reproduces on a clean checkout, so this predates any in-flight branches. Likely broken by a recent change in the shared session-key or ACP-binding routing surfaces that the Slack test pins.
Reproduction
node scripts/run-vitest.mjs extensions/slack/src/monitor/message-handler/prepare.thread-session-key.test.ts→ 1 failed / 15 passed.