feat(agent-platform): explain route conflicts and fallback

This commit is contained in:
huanghuoguoguo
2026-07-11 10:59:58 +08:00
parent 3aeae92707
commit b8d8bbadd5
6 changed files with 242 additions and 45 deletions
@@ -31,12 +31,14 @@ steps:
- "Create a temporary HTTP Bot with a saved message.received route to the discard processor."
- "Open the Bot configuration in the WebUI."
- "Confirm the adapter capability summary, friendly event name, target, and route status are visible."
- "Confirm overlapping routes and unmatched-event fallback behavior are explained before save."
- "Open Test event route and run a dry-run against the current form."
- "Run the saved runtime route with a synthetic event."
- "Close the dialog and confirm the route card shows the latest discarded status."
checks:
- "UI: A user can choose a channel and add event routes during initial Bot creation."
- "UI: Event routing uses user-facing labels and does not require the raw event name in the primary route card."
- "UI: Definite route shadowing and unmatched-event fallback behavior are visible without opening raw logs."
- "UI: Dry-run visibly reports that the route matched the discard processor."
- "UI: Saved-route execution visibly succeeds, explains its side-effect boundary, and updates route status to discarded."
- "Console: No unexpected frontend errors appear during the flow."