Files
OmniRoute/docs/routing
Diego Rodrigues de Sa e Souza 8b9c7734b8 fix(routing): resolve nested combo-ref panel members in fusion strategy (#6764) (#7259)
Fusion's panel-model extraction in combo.ts only recognized plain string
or {model: string} entries in combo.models; a {kind:"combo-ref", comboName}
step (a first-class, Zod-validated combo-step shape the dashboard already
lets you add to a fusion panel) had neither field, so it was silently
filtered out — no error, no warning, and an opaque 400 if it was the only
panel member.

A combo-ref panel member is now dispatched as one black-box panel voice
(a recursive handleComboChat call into the referenced combo, reusing the
same executeComboRefUnit + cycle/depth guards every other combo-ref-
consuming strategy already uses), not a fan-out of the referenced combo's
own targets.

New module open-sse/services/combo/fusionPanel.ts keeps the frozen
combo.ts god-file's growth minimal (extraction/dispatch-wrapper logic
lives there; the fusion branch itself only wires it in).
2026-07-17 10:41:13 -03:00
..
2026-06-16 01:00:40 -03:00
2026-06-29 08:40:06 -03:00
2026-06-29 08:40:06 -03:00