From a9a1b04e2f3cee55aa8e080ad6d7cf7c670d93ec Mon Sep 17 00:00:00 2001 From: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com> Date: Mon, 7 Sep 2026 16:37:45 -0300 Subject: [PATCH] chore(a2a): follow-ups changelog MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Changelog fragment for the five items PR-C delivers from #12639. The sixth item on the issue — an authenticated panel path for A2A task creation — stays deliberately out of scope and is recorded as such in a comment on the issue rather than silently dropped: the JSON-RPC endpoint accepts API keys only, and widening that endpoint's auth surface to serve a UI convenience is the operator's call, not the implementation's. Closes #12639 --- changelog.d/fixes/orchestration-followups.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 changelog.d/fixes/orchestration-followups.md diff --git a/changelog.d/fixes/orchestration-followups.md b/changelog.d/fixes/orchestration-followups.md new file mode 100644 index 0000000000..6502c7f40b --- /dev/null +++ b/changelog.d/fixes/orchestration-followups.md @@ -0,0 +1,15 @@ +- **fix(dashboard):** five follow-ups from the Phase 2 Orchestration Canvas review. The History + drawer now shows the memory section for runs that already left the live TTL window: the + persisted `memory_hits` event is parsed into `metadata.memoryHits` with the same defensive + validation the drawer applies, and — because that event is observability rather than a state + transition — it no longer leaks into the timeline, where it had been inheriting the task's + state and rendering as a duplicate transition. The A2A memory recall runs against its own 1.5s + deadline instead of inheriting the memory backend's 30s one; overshooting degrades exactly like + any other recall failure (no hits, task proceeds), and the timer is cleared on both paths. + Repeating a Conductor run carries its `requirements.cli`/`requirements.model` forward, so the + new run is pinned to the same runner profile and model rather than drifting to whatever the + fleet picks. A successful repeat from the Agents tab now focuses the run it created, instead of + leaving the operator on the finished one. And the auth test for `POST /api/conductor/tasks` + moved into the shared `ROUTES` array rather than restating the pattern. + + Closes #12639