@solidxai/core 0.1.11-beta.1 → 0.1.11-beta.4

package/dist-tests/helpers/auth.js

@@ -1,41 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.getAccessToken = getAccessToken;
-exports.getAuthHeaders = getAuthHeaders;
-const test_1 = require("@playwright/test");
-const env_1 = require("./env");
-async function getAccessToken(baseURL) {
-    const TEST_USER_EMAIL = (0, env_1.getRequiredEnv)("TEST_USER_EMAIL");
-    const TEST_USER_PASSWORD = (0, env_1.getRequiredEnv)("TEST_USER_PASSWORD");
-    const api = await test_1.request.newContext({
-        baseURL,
-        extraHTTPHeaders: {
-            accept: "*/*",
-            "content-type": "application/json",
-        },
-    });
-    try {
-        const res = await api.post("/api/iam/authenticate", {
-            data: {
-                email: TEST_USER_EMAIL,
-                username: "",
-                password: TEST_USER_PASSWORD,
-            },
-        });
-        (0, test_1.expect)(res.status()).toBe(200);
-        const json = await res.json();
-        const token = json?.data?.accessToken;
-        (0, test_1.expect)(token, "Expected access token from authenticate endpoint.").toBeTruthy();
-        return token;
-    }
-    finally {
-        await api.dispose();
-    }
-}
-async function getAuthHeaders(baseURL) {
-    const token = await getAccessToken(baseURL);
-    return {
-        authorization: `Bearer ${token}`,
-    };
-}
-//# sourceMappingURL=auth.js.map

package/dist-tests/helpers/auth.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"auth.js","sourceRoot":"","sources":["../../tests/helpers/auth.ts"],"names":[],"mappings":";;AAGA,wCA6BC;AAED,wCAKC;AAvCD,2CAAmD;AACnD,+BAAuC;AAEhC,KAAK,UAAU,cAAc,CAAC,OAAe;IAClD,MAAM,eAAe,GAAG,IAAA,oBAAc,EAAC,iBAAiB,CAAC,CAAC;IAC1D,MAAM,kBAAkB,GAAG,IAAA,oBAAc,EAAC,oBAAoB,CAAC,CAAC;IAEhE,MAAM,GAAG,GAAG,MAAM,cAAO,CAAC,UAAU,CAAC;QACnC,OAAO;QACP,gBAAgB,EAAE;YAChB,MAAM,EAAE,KAAK;YACb,cAAc,EAAE,kBAAkB;SACnC;KACF,CAAC,CAAC;IAEH,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,MAAM,GAAG,CAAC,IAAI,CAAC,uBAAuB,EAAE;YAClD,IAAI,EAAE;gBACJ,KAAK,EAAE,eAAe;gBACtB,QAAQ,EAAE,EAAE;gBACZ,QAAQ,EAAE,kBAAkB;aAC7B;SACF,CAAC,CAAC;QAEH,IAAA,aAAM,EAAC,GAAG,CAAC,MAAM,EAAE,CAAC,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QAC/B,MAAM,IAAI,GAAG,MAAM,GAAG,CAAC,IAAI,EAAE,CAAC;QAC9B,MAAM,KAAK,GAAG,IAAI,EAAE,IAAI,EAAE,WAAiC,CAAC;QAC5D,IAAA,aAAM,EAAC,KAAK,EAAE,mDAAmD,CAAC,CAAC,UAAU,EAAE,CAAC;QAChF,OAAO,KAAe,CAAC;IACzB,CAAC;YAAS,CAAC;QACT,MAAM,GAAG,CAAC,OAAO,EAAE,CAAC;IACtB,CAAC;AACH,CAAC;AAEM,KAAK,UAAU,cAAc,CAAC,OAAe;IAClD,MAAM,KAAK,GAAG,MAAM,cAAc,CAAC,OAAO,CAAC,CAAC;IAC5C,OAAO;QACL,aAAa,EAAE,UAAU,KAAK,EAAE;KACjC,CAAC;AACJ,CAAC","sourcesContent":["import { expect, request } from \"@playwright/test\";\nimport { getRequiredEnv } from \"./env\";\n\nexport async function getAccessToken(baseURL: string) {\n  const TEST_USER_EMAIL = getRequiredEnv(\"TEST_USER_EMAIL\");\n  const TEST_USER_PASSWORD = getRequiredEnv(\"TEST_USER_PASSWORD\");\n\n  const api = await request.newContext({\n    baseURL,\n    extraHTTPHeaders: {\n      accept: \"*/*\",\n      \"content-type\": \"application/json\",\n    },\n  });\n\n  try {\n    const res = await api.post(\"/api/iam/authenticate\", {\n      data: {\n        email: TEST_USER_EMAIL,\n        username: \"\",\n        password: TEST_USER_PASSWORD,\n      },\n    });\n\n    expect(res.status()).toBe(200);\n    const json = await res.json();\n    const token = json?.data?.accessToken as string | undefined;\n    expect(token, \"Expected access token from authenticate endpoint.\").toBeTruthy();\n    return token as string;\n  } finally {\n    await api.dispose();\n  }\n}\n\nexport async function getAuthHeaders(baseURL: string) {\n  const token = await getAccessToken(baseURL);\n  return {\n    authorization: `Bearer ${token}`,\n  };\n}\n"]}

package/dist-tests/helpers/env.js

@@ -1,11 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.getRequiredEnv = getRequiredEnv;
-function getRequiredEnv(name) {
-    const value = process.env[name];
-    if (!value) {
-        throw new Error(`Missing required env var: ${name}`);
-    }
-    return value;
-}
-//# sourceMappingURL=env.js.map

package/dist-tests/helpers/env.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"env.js","sourceRoot":"","sources":["../../tests/helpers/env.ts"],"names":[],"mappings":";;AAAA,wCAMC;AAND,SAAgB,cAAc,CAAC,IAAY;IACzC,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;IAChC,IAAI,CAAC,KAAK,EAAE,CAAC;QACX,MAAM,IAAI,KAAK,CAAC,6BAA6B,IAAI,EAAE,CAAC,CAAC;IACvD,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC","sourcesContent":["export function getRequiredEnv(name: string): string {\n  const value = process.env[name];\n  if (!value) {\n    throw new Error(`Missing required env var: ${name}`);\n  }\n  return value;\n}\n"]}

package/docs/agent-hub-grooming.md

@@ -1,301 +0,0 @@
-# SolidX AI Agent Builder / Agent Registry Vision
-
-## Concept
-
-The **AI Agent Builder** is a SolidX module that allows teams to define, configure, test, and deploy AI agents as first-class metadata-driven entities.
-
-The goal is to make agents configurable through SolidX rather than hardcoded in application code.
-
-Each agent is powered by a **Mini-SWE style runtime loop**, but the behaviour of the agent is controlled by SolidX metadata:
-
-```text
-Agent Definition
-+ Skills
-+ Tools
-+ Knowledge Base
-+ Policies
-+ Output Schema
-= Runnable Enterprise Agent
-```
-
----
-
-## Module Installation
-
-The AI Agent Builder can be installed as a standard SolidX module.
-
-Once installed, it brings its own domain model, such as:
-
-```text
-Agent
-Agent Skill
-Agent Tool
-Agent Knowledge Base
-Agent Policy
-Agent Run
-Agent Interaction
-Tool Call Log
-```
-
-However, the actual agent configuration can be saved directly into SolidX metadata JSON, instead of requiring every configuration detail to be stored as transactional database rows.
-
-The database can mainly store runtime records such as:
-
-```text
-Agent Run
-Conversation History
-Tool Calls
-Execution Logs
-Errors
-Audit Trail
-```
-
----
-
-## Agent Configuration UI
-
-SolidX can provide either:
-
-1. A native SolidX CRUD-style UI, or  
-2. A custom Agent Builder UI
-
-to manage agent artefacts.
-
-The user can configure:
-
-```text
-Agent name
-Agent description
-System instructions
-Allowed skills
-Allowed tools
-Linked knowledge bases
-Runtime limits
-Approval rules
-Output schema
-```
-
-Example:
-
-```text
-Customer Support Agent
-- Skill: Complaint Handling
-- Skill: Refund Policy Interpretation
-- Tool: Gmail
-- Tool: CRM
-- Knowledge Base: Support SOPs
-- Runtime: Mini-SWE
-```
-
----
-
-## Skills
-
-A skill represents reusable know-how.
-
-Examples:
-
-```text
-Contract Review
-Invoice Validation
-Customer Escalation Handling
-Code Review
-Document Classification
-```
-
-A skill may contain:
-
-```text
-Instructions
-Prompt templates
-Examples
-Decision criteria
-Expected output format
-```
-
-Skill = **how to think / how to perform a task**
-
----
-
-## Tools
-
-Tools are executable capabilities available to agents.
-
-Examples:
-
-```text
-Send Email
-Search Gmail
-Query Database
-Create Ticket
-Read File
-Call API
-Search Knowledge Base
-```
-
-Tool = **what action the agent can perform**
-
-SolidX can provide a screen where all registered/discovered tools are visible.
-
-The tool registry can include:
-
-```text
-Native SolidX tools
-Internal APIs
-MCP tools
-Composio tools
-Custom enterprise tools
-```
-
-Each tool can have metadata:
-
-```text
-Name
-Description
-Input schema
-Output schema
-Auth mode
-Approval requirement
-Allowed roles
-Provider
-```
-
----
-
-## Knowledge Base
-
-Agents can be linked to one or more knowledge bases.
-
-Examples:
-
-```text
-Company policies
-Product documentation
-Support articles
-Technical specifications
-SOPs
-Contract templates
-```
-
-This allows each agent to operate with controlled enterprise context.
-
----
-
-## Agent Runtime
-
-Each configured agent is executed as a Mini-SWE loop.
-
-When invoked, SolidX spawns an agent run and gives it:
-
-```text
-Goal
-User input
-Agent metadata
-Relevant skills
-Available tools
-Knowledge context
-Policies
-Output schema
-```
-
-The agent then runs autonomously:
-
-```text
-Plan
-Act
-Use tool
-Observe
-Re-plan
-Complete
-```
-
-The workflow engine or UI does not need to understand the internal reasoning loop.
-
-It only receives the final structured result.
-
----
-
-## Test Interface
-
-Once an agent is configured, users can test it inside SolidX.
-
-Default interface:
-
-```text
-Chat-based test console
-```
-
-Future interfaces:
-
-```text
-Voice
-WhatsApp
-Slack
-Email
-Embedded app widget
-```
-
-This allows business users and developers to validate the agent before attaching it to workflows.
-
----
-
-## Workflow Integration
-
-Any SolidX workflow can include an Agent Handoff step.
-
-Example:
-
-```text
-Workflow Step:
-Delegate document review to Document Review Agent
-```
-
-The workflow creates an Agent Run.
-
-The agent works asynchronously.
-
-When completed, it sends back a result.
-
-The workflow then continues.
-
-```text
-Workflow
-  ↓
-Agent Handoff
-  ↓
-Mini-SWE Agent Run
-  ↓
-Agent Result
-  ↓
-Workflow Continues
-```
-
----
-
-## Strategic Value
-
-This makes SolidX an enterprise agent platform, not just a workflow or low-code platform.
-
-The key advantage is that agents become:
-
-```text
-Configurable
-Reusable
-Governed
-Auditable
-Workflow-aware
-Tool-aware
-Knowledge-aware
-```
-
-SolidX remains the control plane.
-
-Mini-SWE becomes the execution loop.
-
-Tools provide actions.
-
-Skills provide task expertise.
-
-Knowledge bases provide enterprise context.
-
-Together, this creates a metadata-driven framework for building and deploying enterprise-grade AI agents.