Merge branch 'develop' into patch-1

Author: odilitime

.env.example

@@ -340,3 +340,10 @@ STORY_PRIVATE_KEY= # Story private key
 STORY_API_BASE_URL= # Story API base URL
 STORY_API_KEY= # Story API key
 PINATA_JWT= # Pinata JWT for uploading files to IPFS
+
+# Cronos zkEVM
+CRONOSZKEVM_ADDRESS=
+CRONOSZKEVM_PRIVATE_KEY=
+
+# Fuel Ecosystem (FuelVM)
+FUEL_WALLET_PRIVATE_KEY=

.github/workflows/jsdoc-automation.yml

@@ -0,0 +1,81 @@
+name: JSDoc Automation
+
+on:
+  workflow_dispatch:
+    inputs:
+      pull_number:
+        description: 'Pull Request Number (if not provided, scans root_directory) - PR must be merged to develop branch'
+        required: false
+        type: string
+      root_directory:
+        description: 'Only scans files in this directory (relative to repository root, e.g., packages/core/src)'
+        required: true
+        default: 'packages/core/src/test_resources'
+        type: string
+      excluded_directories:
+        description: 'Directories to exclude from scanning (comma-separated, relative to root_directory)'
+        required: true
+        default: 'node_modules,dist,test'
+        type: string
+      reviewers:
+        description: 'Pull Request Reviewers (comma-separated GitHub usernames)'
+        required: true
+        default: ''
+        type: string
+
+jobs:
+  generate-docs:
+    runs-on: ubuntu-latest
+
+    env:
+      GITHUB_ACCESS_TOKEN: ${{ secrets.GH_PAT }}
+      OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '23'
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 8
+          run_install: false
+
+      - name: Update lockfile
+        working-directory: packages/jsdoc-automation
+        run: |
+          echo "Updating lockfile..."
+          pnpm install --no-frozen-lockfile
+          git config --global user.email "github-actions[bot]@users.noreply.github.com"
+          git config --global user.name "github-actions[bot]"
+          git add pnpm-lock.yaml
+          git commit -m "chore: update pnpm lockfile" || echo "No changes to commit"
+          git push || echo "No changes to push"
+
+      - name: Install root dependencies
+        run: pnpm install --no-frozen-lockfile
+
+      - name: Install package dependencies
+        working-directory: packages/jsdoc-automation
+        run: pnpm install --no-frozen-lockfile
+
+      - name: Run documentation generator
+        working-directory: packages/jsdoc-automation
+        run: |
+          echo "Node version: $(node --version)"
+          echo "NPM version: $(npm --version)"
+          echo "Directory contents:"
+          ls -la
+          NODE_OPTIONS='--experimental-vm-modules --no-warnings' pnpm start
+        env:
+          INPUT_ROOT_DIRECTORY: ${{ inputs.root_directory }}
+          INPUT_PULL_NUMBER: ${{ inputs.pull_number }}
+          INPUT_EXCLUDED_DIRECTORIES: ${{ inputs.excluded_directories }}
+          INPUT_REVIEWERS: ${{ inputs.reviewers }}

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[discord server](https://discord.gg/ai16z).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

agent/jest.config.js

@@ -0,0 +1,17 @@
+/** @type {import('ts-jest').JestConfigWithTsJest} */
+export default {
+  preset: 'ts-jest',
+  testEnvironment: 'node',
+  extensionsToTreatAsEsm: ['.ts'],
+  moduleNameMapper: {
+    '^(\\.{1,2}/.*)\\.js$': '$1',
+  },
+  transform: {
+    '^.+\\.tsx?$': [
+      'ts-jest',
+      {
+        useESM: true,
+      },
+    ],
+  },
+};

agent/package.json

@@ -6,7 +6,8 @@
     "scripts": {
         "start": "node --loader ts-node/esm src/index.ts",
         "dev": "node --loader ts-node/esm src/index.ts",
-        "check-types": "tsc --noEmit"
+        "check-types": "tsc --noEmit",
+        "test": "jest"
     },
     "nodemonConfig": {
         "watch": [
@@ -52,12 +53,18 @@
         "@elizaos/plugin-multiversx": "workspace:*",
         "@elizaos/plugin-near": "workspace:*",
         "@elizaos/plugin-zksync-era": "workspace:*",
+        "@elizaos/plugin-twitter": "workspace:*",
+        "@elizaos/plugin-cronoszkevm": "workspace:*",
         "@elizaos/plugin-3d-generation": "workspace:*",
+        "@elizaos/plugin-fuel": "workspace:*",
         "readline": "1.3.0",
         "ws": "8.18.0",
         "yargs": "17.7.2"
     },
     "devDependencies": {
+        "@types/jest": "^29.5.14",
+        "jest": "^29.7.0",
+        "ts-jest": "^29.2.5",
         "ts-node": "10.9.2",
         "tsup": "8.3.5"
     }

agent/src/__tests__/client-type-identification.test.ts

@@ -0,0 +1,53 @@
+import { Client, IAgentRuntime } from "@elizaos/core";
+import { describe, it, expect } from '@jest/globals';
+
+// Helper function to identify client types
+function determineClientType(client: Client): string {
+    // Check if client has a direct type identifier
+    if ('type' in client) {
+        return (client as any).type;
+    }
+
+    // Check constructor name
+    const constructorName = client.constructor?.name;
+    if (constructorName && !constructorName.includes('Object')) {
+        return constructorName.toLowerCase().replace('client', '');
+    }
+
+    // Fallback: Generate a unique identifier
+    return `client_${Date.now()}`;
+}
+
+// Mock client implementations for testing
+class MockNamedClient implements Client {
+    type = "named-client";
+    async start(_runtime?: IAgentRuntime) { return this; }
+    async stop(_runtime?: IAgentRuntime) { }
+}
+
+class MockConstructorClient implements Client {
+    async start(_runtime?: IAgentRuntime) { return this; }
+    async stop(_runtime?: IAgentRuntime) { }
+}
+
+const mockPlainClient: Client = {
+    async start(_runtime?: IAgentRuntime) { return {}; },
+    async stop(_runtime?: IAgentRuntime) { }
+};
+
+describe("Client Type Identification", () => {
+    it("should identify client type from type property", () => {
+        const client = new MockNamedClient();
+        expect(determineClientType(client)).toBe("named-client");
+    });
+
+    it("should identify client type from constructor name", () => {
+        const client = new MockConstructorClient();
+        expect(determineClientType(client)).toBe("mockconstructor");
+    });
+
+    it("should generate fallback identifier for plain objects", () => {
+        const result = determineClientType(mockPlainClient);
+        expect(result).toMatch(/^client_\d+$/);
+    });
+});