Files
Tyler Slaton 7113c8f932 fix(channels): use channel name for thread lock (#6254)
## Problem

Managed Channel deliveries can request a canonical thread lock with the
inner agent ID, or `default` when that ID is unset. Intelligence owns
the thread under the declared Channel name, so the lock fails with
`THREAD_AGENT_MISMATCH`.

## Why

The SDK treated the agent object identity as the managed Channel
identity. Those values are independent: `createChannel({ name })`
declares the managed thread owner, while an agent ID is optional and may
differ.

## Fix

Pass the declared Channel name into the managed delivery adapter and use
it for canonical runs. Add a public `thread.runAgent()` regression test
that proves an agent with a different ID still runs under the Channel
name.

Validated with the Channels Intelligence test suite, type check, and
build; the runtime Channel manager tests, type check, and build; repo
lint; and the affected-package pre-commit checks.
2026-07-30 08:59:24 -07:00
..
2026-07-30 14:03:24 +00:00
2026-07-28 17:48:23 -07:00
2026-07-28 17:48:23 -07:00
2026-07-28 17:48:23 -07:00
2026-07-28 17:48:23 -07:00