cmcts-c-agent-embedding 1.0.13 → 1.0.14-cagent

package/.augment-guidelines

@@ -0,0 +1,24 @@
+### WHEN A USER ASKS IN A LANGUAGE OTHER THAN ENGLISH, PLEASE REITERATE THE USER'S REQUEST IN YOUR UNDERSTANDING IN ENGLISH BEFORE STARTING TO DO THE REQUEST. ALWAYS THINK, ANSWER, PERFORM IN ENGLISH.
+# ###
+
+- Don't write code without using it; ensure everything written is utilized in the project.
+- Comments must explain 'what' and 'why', not 'how' - code should be self-explanatory in implementation. Specifically: 'what' refers to the business logic or purpose the code serves, 'why' explains the reasoning behind design decisions, trade-offs made, or non-obvious choices. The 'how' should be evident from clean, well-structured code with meaningful variable names and clear control flow.
+- Avoid over-commenting - excessive comments indicate poor code quality. A well-written codebase needs minimal comments because the code itself communicates clearly. If you find yourself writing many comments to explain code, refactor the code instead. Comments should be rare and valuable, not cluttering every line.
+- Function comments must explain purpose and reasoning, placed at function beginnings.
+- Code must prioritize readability for human understanding over computer execution efficiency.
+- Maintain long-term maintainability over short-term optimization.
+- Understand and design proper data structures first - good data structures lead to good code.
+- Avoid unnecessary complexity - implement simple solutions unless complexity is truly required.
+- New code you write is garbage if it doesn't follow Linus Torvalds' clean code principles - the father of Linux. These principles include: keep it simple and obvious, make code readable like good prose, avoid premature optimization, write code that clearly expresses intent, minimize abstraction layers, and never add functionality "just in case" - only implement what's needed now. Remember: good taste in code means knowing when to stop adding features and complexity.
+- Before implementation, first use provided reading, searching, browsing, web, and other tools to understand the data structure of the request.
+- Avoid over-engineering - focus on delivering the minimal viable solution that meets the specified acceptance criteria.
+- Only create automated tests if explicitly required in the original requirements.
+- Define all data input/output structures first before writing any logic.
+- Define all function input parameters and return values before implementation.
+- Define all required functions and their signatures at once before writing implementation logic.
+- Implementation logic should be written only after all data structures and function definitions are complete.
+
+- Thís project is using solid-js 1.7.1.
+
+# TO ENSURE THE QUALITY OF THE CODE WRITTEN, EVERY TIME YOU COMPLETE A CODING TASK, YOU ARE REQUIRED TO RUN THE FULL FOLLOWING FLOW:
+  - Flow: write code -> run `yarn run lint` and fix lint errors -> run `yarn run type-check` and finally `yarn run format`.

package/.env

@@ -1,36 +1,36 @@
-# ==============================================
-# REQUIRED CONFIGURATION
-# ==============================================
-
-# API Host URL (required)
-# This should be the URL where your Flowise instance is running
-# Example: https://your-flowise-instance.com
-API_HOST=https://stock.cmcts.ai/c-agent
-
-# Flowise API Key (required)
-# Generate this from your Flowise instance settings page
-# Example: OxxGE-h_LaH7ZYorStjTOik1XY999RxxoHpCSYl8BXxc
-FLOWISE_API_KEY=ztl44tnaaZKMAEHmPBYgCCw3tiEdE-ls5F9Uv7kyMG4
-
-# ==============================================
-# CHATFLOWS CONFIGURATION (required)
-# ==============================================
-
-# Format: [identifier]=[chatflowId],[allowedDomain1],[allowedDomain2],...
-#
-# Each entry consists of:
-# - identifier: Any name you choose (e.g., agent1, support, salesbot)
-# - chatflowId: The UUID of your Flowise chatflow
-# - allowedDomains: Comma-separated list of domains where this chat can be embedded
-#                   Note: Wildcard domains (*) are not supported for security reasons
-#
-# Examples:
-# agent1=20db97c6-64c9-4411-bab4-7d6202171600,https://example1.com
-# support=1c28f529-a70f-5001-9bc5-4f4c5d03d8c0,https://example2.com,https://another-example2.com
-# salesbot=3db97c6-64c9-4411-bab4-7d620217160a,https://sales.example.com
-
-# Add your chatflows below:
-chatflow_1=1d93aaac-ac11-44b8-9646-6ac075fa700d
-chatflow_2=
-
+# ==============================================
+# REQUIRED CONFIGURATION
+# ==============================================
+
+# API Host URL (required)
+# This should be the URL where your Flowise instance is running
+# Example: https://your-flowise-instance.com
+API_HOST=https://stock.cmcts.ai/c-agent
+
+# Flowise API Key (required)
+# Generate this from your Flowise instance settings page
+# Example: OxxGE-h_LaH7ZYorStjTOik1XY999RxxoHpCSYl8BXxc
+FLOWISE_API_KEY=ztl44tnaaZKMAEHmPBYgCCw3tiEdE-ls5F9Uv7kyMG4
+
+# ==============================================
+# CHATFLOWS CONFIGURATION (required)
+# ==============================================
+
+# Format: [identifier]=[chatflowId],[allowedDomain1],[allowedDomain2],...
+#
+# Each entry consists of:
+# - identifier: Any name you choose (e.g., agent1, support, salesbot)
+# - chatflowId: The UUID of your Flowise chatflow
+# - allowedDomains: Comma-separated list of domains where this chat can be embedded
+#                   Note: Wildcard domains (*) are not supported for security reasons
+#
+# Examples:
+# agent1=20db97c6-64c9-4411-bab4-7d6202171600,https://example1.com
+# support=1c28f529-a70f-5001-9bc5-4f4c5d03d8c0,https://example2.com,https://another-example2.com
+# salesbot=3db97c6-64c9-4411-bab4-7d620217160a,https://sales.example.com
+
+# Add your chatflows below:
+chatflow_1=6a63bb88-88f7-4c4d-805e-9c027c85707b
+chatflow_2=
+
 CHATWOOT_BASE_URL=http://203.145.47.214:8003

package/.eslintrc.cjs

@@ -1,3 +1,4 @@
+// eslint-disable-next-line no-undef
 module.exports = {
     root: true,
     extends: ['eslint:recommended', 'plugin:@typescript-eslint/recommended', 'prettier', 'plugin:solid/typescript'],

package/.idea/AICommit.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="com.github.blarc.ai.commits.intellij.plugin.settings.ProjectSettings">
+    <option name="splitButtonActionSelectedLLMClientId" value="1ebebfb1-3058-49aa-ad9b-c8eae648b7de" />
+  </component>
+</project>