@iblai/iblai-js 2.7.4 → 2.7.6

package/dist/playwright/index.d.ts

@@ -817,15 +817,17 @@ declare function addSkillToAgent(page: Page, skillName: string): Promise<void>;
  */
 declare function verifySkillAdded(page: Page, skillName: string): Promise<void>;
 /**
- * Open the three-dots actions menu for a skill row on the active sub-tab.
- * Agent-tab rows offer "Remove from Agent" only; catalog rows offer
- * Edit/Delete (for editable skills). The menu content portals to
- * document.body, so the returned locator is page-level by design.
+ * Open the three-dots actions menu for a CATALOG skill row (Edit/Delete on
+ * editable skills). Agent-tab rows have no menu — detaching is a direct
+ * "Remove" button there (see `removeSkillFromAgent`). The menu content
+ * portals to document.body, so the returned locator is page-level by design.
  */
 declare function openSkillActionsMenu(page: Page, skillName: string): Promise<Locator>;
 /**
- * Detach a skill from the agent via its row menu ("Remove from Agent") on the
- * "Agent Skills" sub-tab. Waits for the toast and for the row to disappear.
+ * Detach a skill from the agent via its row's direct "Remove" button on the
+ * "Agent Skills" sub-tab (the visible text is just "Remove"; the button's
+ * accessible name carries the skill, mirroring the catalog's Add button).
+ * Waits for the toast confirming the detach.
  */
 declare function removeSkillFromAgent(page: Page, skillName: string): Promise<void>;
 /**

package/dist/playwright/index.esm.js

@@ -2917,10 +2917,10 @@ async function verifySkillAdded(page, skillName) {
     logger.info(`Skill "${skillName}" shows as Added`);
 }
 /**
- * Open the three-dots actions menu for a skill row on the active sub-tab.
- * Agent-tab rows offer "Remove from Agent" only; catalog rows offer
- * Edit/Delete (for editable skills). The menu content portals to
- * document.body, so the returned locator is page-level by design.
+ * Open the three-dots actions menu for a CATALOG skill row (Edit/Delete on
+ * editable skills). Agent-tab rows have no menu — detaching is a direct
+ * "Remove" button there (see `removeSkillFromAgent`). The menu content
+ * portals to document.body, so the returned locator is page-level by design.
  */
 async function openSkillActionsMenu(page, skillName) {
     const actionsButton = page.getByRole('button', { name: `${skillName} actions` });
@@ -2931,12 +2931,17 @@ async function openSkillActionsMenu(page, skillName) {
     return menu;
 }
 /**
- * Detach a skill from the agent via its row menu ("Remove from Agent") on the
- * "Agent Skills" sub-tab. Waits for the toast and for the row to disappear.
+ * Detach a skill from the agent via its row's direct "Remove" button on the
+ * "Agent Skills" sub-tab (the visible text is just "Remove"; the button's
+ * accessible name carries the skill, mirroring the catalog's Add button).
+ * Waits for the toast confirming the detach.
  */
 async function removeSkillFromAgent(page, skillName) {
-    const menu = await openSkillActionsMenu(page, skillName);
-    await menu.getByRole('menuitem', { name: /Remove from Agent/i }).click();
+    const removeButton = page.getByRole('button', {
+        name: `Remove ${skillName} from this agent`,
+    });
+    await expect(removeButton).toBeVisible({ timeout: 10000 });
+    await removeButton.click();
     await expect(page.getByText(`${skillName} removed`, { exact: false })).toBeVisible({
         timeout: 10000,
     });