AI-Powered Development in KBbridge

I need you to do the follwing, first go to hour main website https://[cliente].com read and understands our product in all it's variations, once you have a full anderstandig I want to use multiple agents to do the follwing: 1- read the detail design spcifiaction of our product in here [documento-de-diseño].docx 2 - with the combined knowladge of our public website and the detail design from point 1 I want you to dispatch multiple agents to readn and anailze the current "repository" 3 - the current repositroy is the source code of the Application writen in GeneXus 4 - in addition you have the following resource to add you on this task: a- "genexus-knowladge" mcp that contains all the documentation about how genexus works, so you can consult it for any doubt that you have b - there is a directory called .ai with a lot of gramatic and lexographic information on how to work with genexus c - this repository was created with a tool call KBbridge which transfrom all the Genexus objects into text files, more about how to use it is in the .ai folder. d- the "generated code" created by genexus lives here : C:\Models\[Cliente]\Trunk\web - VERY IMPORTANT - you could NOT edit the generated code, only VIEW e- the application lives inside IIS on the local machine and can be accessed at the following link: http://trunk_test_prod.[servidor-cliente].com/pxtools.apis.hwblogin.aspx you should use "playright" plugin to access it the credential is: User "[admin-user]" Password: "[*****]" you click "login" and the screen will ask for a "Code" just use "aa" The task is to do a DEEP research and discovery of the source code and link it to the description of the product as explained in the public website and match the code with the detail design. After this deep analisis I want to creat a detailed documentation that include a architectural design of the aplication as the "big picture" then start going down into each module and submodule until we reach, and explain every single procedure and subrutine. The porpuse is to have in this final document as much information as possible so we can use it latter as "source of thruth", also this informain will be use to design, create and run "regresion tests" and pentetration tests based on OWASP guidelines. For this IMPORTANT task I need to put your biggest effor to create the best documentation that you are capable of. Let's start and don't stop until the document is finish, let me know once it's done

I've reviewd the document and need some minor changes: Devloped with Genexus version 17 U11 There are 3 different APIs each with different protocoles a- Usage Information - this is internally used to get metrics on client's experience. this is what you've identified as "8.2 Core Services (Custom REST)" b- External Devices located at the manufactring locatio, we've integrated with serveral scales. This API uses WebSocket technology to "get information" from equipment. This is hadle under the "Device" module, not API module. Plese read the code to understand how genexus manages WebSocket and comument it b- Clients's end point APIs to access their own information and it does NOT use token, it uses a diferent type of "user" call API user that can have either read-only acess, write-only access or both (the write access is in the design face, not implemented yet). This is what you've Identified as "8.3 PXWSLayer API Surface (67 Resources)"

could you test the MCP for inventory?

Yes, because when you developed the MCP server yu've made a mistake you asumed that the credetaials for the MCP are a "token" but in reallity if you check the code of the tools, they are using the APIs to serve the tools, and the APIs expect the receveive a "user" and "password". Before we adjust this basd on MCP standards can we accept login credenticas or Base auth or Bared outh on MCP?

let's do this, store in memory the credentials for the API user, login "[api-user]" password: "[*****]". Use it for testing

but did you change the "mcphandel" to support the credentials? I don't see any changes there?

I want you to "sync" following the sync rules, chck for errors and fix them, once the errors are gone, I what to "buiild" the the geneuxs app (probably using msbuild, check genexus-documentation), check the compilation errors and if there are none then test the MCP. You may want to start by testing the "build" first, before you "sync" the changes to make sure that all is working now