CHANGELOG.md: kernel(triggers) entry (#5960) was accidentally clobbered

The diff replaced the first sentence of the existing kernel(triggers): TaskClaimed and TaskCompleted triggers gain an optional creator_match filter bullet (#5960, @nevgenov) with the new feat(runtime,kernel) entry, but the second sentence of the kernel(triggers) entry was left in place and is now dangling as a continuation of the async agent_send description.

This line belongs to #5960, not to agent_send:

Accepts an agent UUID, display name, or "self"; absent (#[serde(default)]) it preserves the legacy fire-for-all behaviour and existing string-form triggers still parse. The original poster is threaded onto the TaskClaimed / TaskCompleted events from the task record.

The CHANGELOG should read (two separate bullets):

- **feat(runtime,kernel): non-blocking `agent_send` — `"async": true` delegates without blocking the caller** (#6043) (@DaBlitzStein).
  `agent_send` was synchronous-only: it awaited the target agent's full reply as the tool result, so any delegation longer than `tool_timeout_secs` (default 120s) was killed mid-flight and the caller's loop stayed blocked the whole time (a Telegram-facing agent went unresponsive while it waited).
  Passing `"async": true` now registers the delegation on the existing async-task tracker (#4983, previously wired only to `workflow_start`) via the new `KernelHandle::send_to_agent_async_tracked`, spawns the callee loop detached, and returns a `task_id` immediately. The callee's response is injected back into the caller's session when it finishes — mid-turn if the loop is live, else wake-idle — reusing `TaskKind::Delegation` and `complete_async_task`.
  Blocking `agent_send` (the default) is unchanged; the depth guard still rejects too-deep chains before they can fire async.
- **kernel(triggers): `TaskClaimed` and `TaskCompleted` triggers gain an optional `creator_match` filter** (#5960) (@nevgenov), symmetrical to `TaskPosted`'s `assignee_match`, so an orchestrator can scope claim/completion notifications to tasks it originally posted instead of firing on every claim/completion system-wide.
  Accepts an agent UUID, display name, or `"self"`; absent (`#[serde(default)]`) it preserves the legacy fire-for-all behaviour and existing string-form triggers still parse. The original poster is threaded onto the `TaskClaimed` / `TaskCompleted` events from the task record.

Please restore the kernel(triggers) bullet and remove its dangling sentence from the feat(runtime,kernel) entry.

Generated by Claude Code

CHANGELOG.md: new entry inserted mid-bullet, corrupting the #5960 entry

The #6043 entry is inserted between the first sentence and the continuation sentence of the TaskClaimed/TaskCompleted trigger filter entry (#5960, @nevgenov).

In the resulting file the #5960 entry reads as a single orphaned sentence, and the Accepts an agent UUID, display name, or \"self"`; absent (`#[serde(default)]`) it preserves the legacy fire-for-all behaviour and existing string-form triggers still parse. The original poster is threaded onto the `TaskClaimed` / `TaskCompleted` events from the task record.continuation — which clearly describes thecreator_matchtrigger filter, notagent_send— ends up visually attached to the new#6043` entry.

The fix is to move the #6043 bullet to a position after the full #5960 entry (i.e., after the Accepts an agent UUID… line), so the TaskClaimed entry stays intact:

 - **kernel(triggers): `TaskClaimed` and `TaskCompleted` triggers …** (#5960) (@nevgenov)…
   Accepts an agent UUID, display name, or `"self"`; absent (`#[serde(default)]`) it preserves the legacy fire-for-all behaviour and existing string-form triggers still parse. The original poster is threaded onto the `TaskClaimed` / `TaskCompleted` events from the task record.
+- **feat(runtime,kernel): non-blocking `agent_send` …** (#6043) (@DaBlitzStein).
+  …

Generated by Claude Code

One CHANGELOG formatting issue to fix before merge (see inline comment on CHANGELOG.md)."

Generated by Claude Code

CI is failing with 9 compile errors — all in crates/librefang-runtime/src/tool_runner/tests/mod.rs. Two root causes:

1. DispatchCapture::send_to_agent_async_tracked is missing the chat_id parameter (E0050)

The trait signature in agent_control.rs was extended to include chat_id: Option<&str> as the last parameter, but the test mock at line 654 only has 5 parameters (excluding &self). Fix:

     async fn send_to_agent_async_tracked(
         &self,
         _agent_id: &str,
         _message: &str,
         _caller_agent_id: &str,
         caller_session_id: Option<&str>,
         _conversation_key: Option<&str>,
+        _chat_id: Option<&str>,
     ) -> Result<String, librefang_kernel_handle::KernelOpError> {

2. Eight test call sites pass 4 arguments to tool_agent_send but the function now takes 5 (E0061)

tool_agent_send gained chat_id: Option<&str> as a fifth parameter, but the test updates only added caller_session_id. Each call needs one more trailing None:

line 856:  tool_agent_send(&input, Some(&kernel), None, None)           → …, None, None, None)
line 872:  tool_agent_send(&input, Some(&kernel), Some("parent-agent"), None)   → …, None, None)
line 893:  same
line 902:  same
line 929:  same
line 964:  tool_agent_send(&input, Some(&kernel), Some("parent-agent"), Some(session)) → …, Some(session), None)
line 1001: tool_agent_send(&input, Some(&kernel), None, None)           → …, None, None, None)
line 1034: tool_agent_send(&input, Some(&kernel), Some("parent-agent"), None)   → …, None, None)

No logic changes required — just the trailing None (tests have no channel context, so None is correct). cargo check -p librefang-runtime will be green after these edits.

Generated by Claude Code

Requesting changes — the branch does not compile (CI red on Build / Linux aarch64, Test / Unit, Test / Ubuntu shard 1/4, and Quality).

Root cause from the build logs (run 27844448423), and these are internal to this PR — send_to_agent_async_tracked is newly introduced here and the PR is only 1 commit behind main, so it's not a rebase/drift issue:

• error[E0050]: method 'send_to_agent_async_tracked' has 6 parameters but the declaration in trait 'send_to_agent_async_tracked' has 7 — the trait declaration and its impl disagree on arity; the signature was changed in one place but not the other.
• Multiple error[E0061]: this function takes 5 arguments but 4 arguments were supplied — call sites weren't updated to the new signature.

Please reconcile the trait/impl signature and update every call site so it compiles, then push — happy to re-review once CI is green. The non-blocking-agent_send direction itself looks right; this is purely a half-applied signature change.

The build-breaking test gaps are fixed (f1e1bca): the mock impl and the 8 tool_agent_send callsites now match the new chat_id signature. Approving once CI is green.