Eliminate all the remaining static mappings by wiring in all backend capabilities - #650
Conversation
|
I put this back to draft until the dependencies are cleared up. |
6c3ba6d to
070170b
Compare
070170b to
a74cd67
Compare
Replace WORKFLOW_NAME_TO_PATTERN_SLUG with patternTypeFromSummary and getApiUrlForChatTarget so catalog chat_api_target and capability flags drive workflow pattern selection. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: pdobrei <pdobrei@cisco.com>
…ity CID maps Apply backend-provided agent_directory_cid, identity_app_slug, badge/policy overrides, and verification status from topology wire data. Route OASF and identity API calls via chat_api_target instead of static slug/CID maps. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: pdobrei <pdobrei@cisco.com>
…p transport config fetch Render transport node labels and GitHub links from backend message_transport wire fields and remove the dynamic /transport/config polling path. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: pdobrei <pdobrei@cisco.com>
…ties Previously implemented backend capabilities and features make it possible to remove statically mapped and other constant-defined behaviors from the UI and replace them with dynamically calculated results based on backend provided data. This restructure was applied wherever possible, and corresponding cleanup was done in a wide range of frontend files. Appropriate tests added, updated. Signed-off-by: pdobrei <pdobrei@cisco.com>
536a673 to
66abe64
Compare
delthazor
changed the title
Some data files were misformated, and the corresponding loading mechanism hade minor race conditions leading to some graphs not always loading properly. Such discrepancies were resolved, and graph positioning was rewired so it appears correctly every time. Signed-off-by: pdobrei <pdobrei@cisco.com>
misi-bp
left a comment
misi-bp
left a comment
There was a problem hiding this comment.
The code is OK, a small type simplification can be dealt but it's also OK like this.
No console issues, the modals work fine, but
- A2A Http / Directory details look like this:
- and the 'Buyer' issue is still there - IDK if it will be gone after rebase, let's see.
Some data types were casted as unknown due to some fields sometimes missing from the datatype. Such fields are now casted without the unknown cast wherever it can be omitted, and a special wrapper was added for the cases it can not be removed. Signed-off-by: pdobrei <pdobrei@cisco.com>
I cleaned up the type conversion issue. The directory data you screenshotted seems fine to me, or at least I don't know how should it look like. The buyer issue was not part of the scope of this PR, but it was addressed earlier, during the backend enrichment process. If it is still not appearing as it should be, please open a separate issue for that one. You can instantly assign it to me, I will look into it. |
|
The UI will be fixed separately (by myself). |
misi-bp
left a comment
misi-bp
left a comment
There was a problem hiding this comment.
lgtm, the issues founf will be dealt separately.
3 participants
Description
Enriched workflow capabilities with backend-driven and OASF-based processing changes, and corresponding UI rewrite to consume the new signals and data instead of applying the previous static maps to each agent data.
Agent capabilities are now derived on the backend side from their OASF annotations, and then sent to the frontend through the already existing and now expanded WorkflowSummary.
Frontend then fetches that data and uses it for all the purposes the static maps were used previously.
Test coverage was extended to cover both the new code and previously uncovered existing code parts.
Issue Link
Fixes #569
Fixes #568
Type of Change
Checklist