Merge branch 'develop' into fix/postgres-adapter-schema-check

Author: ryanleecode

.env.example

@@ -9,6 +9,7 @@ DISCORD_VOICE_CHANNEL_ID=       # The ID of the voice channel the bot should joi
 
 # AI Model API Keys
 OPENAI_API_KEY=                 # OpenAI API key, starting with sk-
+OPENAI_API_URL=                 # OpenAI API Endpoint (optional), Default: https://api.openai.com/v1
 SMALL_OPENAI_MODEL=             # Default: gpt-4o-mini
 MEDIUM_OPENAI_MODEL=            # Default: gpt-4o
 LARGE_OPENAI_MODEL=             # Default: gpt-4o
@@ -35,6 +36,10 @@ SMALL_HYPERBOLIC_MODEL=         # Default: meta-llama/Llama-3.2-3B-Instruct
 MEDIUM_HYPERBOLIC_MODEL=        # Default: meta-llama/Meta-Llama-3.1-70B-Instruct
 LARGE_HYPERBOLIC_MODEL=         # Default: meta-llama/Meta-Llama-3.1-405-Instruct
 
+# Livepeer configuration
+LIVEPEER_GATEWAY_URL=           # Free inference gateways and docs: https://livepeer-eliza.com/
+LIVEPEER_IMAGE_MODEL=           # Default: ByteDance/SDXL-Lightning
+
 # Speech Synthesis
 ELEVENLABS_XI_API_KEY=          # API key from elevenlabs
 
@@ -157,10 +162,22 @@ LARGE_GAIANET_SERVER_URL=       # Default: https://qwen72b.gaia.domains/v1
 GAIANET_EMBEDDING_MODEL=
 USE_GAIANET_EMBEDDING=          # Set to TRUE for GAIANET/768, leave blank for local
 
+# Volcengine Configuration
+VOLENGINE_API_URL=              # Volcengine API Endpoint, Default: https://open.volcengineapi.com/api/v3/
+VOLENGINE_MODEL=
+SMALL_VOLENGINE_MODEL=          # Default: doubao-lite-128k
+MEDIUM_VOLENGINE_MODEL=         # Default: doubao-pro-128k
+LARGE_VOLENGINE_MODEL=          # Default: doubao-pro-256k
+VOLENGINE_EMBEDDING_MODEL=      # Default: doubao-embedding
+
 # EVM
 EVM_PRIVATE_KEY=
 EVM_PROVIDER_URL=
 
+# Avalanche
+AVALANCHE_PRIVATE_KEY=
+AVALANCHE_PUBLIC_KEY=
+
 # Solana
 SOLANA_PRIVATE_KEY=
 SOLANA_PUBLIC_KEY=
@@ -340,3 +357,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/pull_request_template.md

@@ -1,15 +1,15 @@
-<!-- Use this template by filling in information and copy and pasting relevant items out of the html comments. -->
+<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->
 
-# Relates to:
+# Relates to
 
 <!-- LINK TO ISSUE OR TICKET -->
 
-<!-- This risks section is to be filled out before final review and merge. -->
+<!-- This risks section must be filled out before the final review and merge. -->
 
 # Risks
 
 <!--
-Low, medium, large. List what kind of risks, and what could be effected.
+Low, medium, large. List what kind of risks and what could be affected.
 -->
 
 # Background
@@ -25,7 +25,7 @@ Features (non-breaking change which adds functionality)
 Updates (new versions of included code)
 -->
 
-<!-- This "Why" section is most relevant if there is no linked issue explaining why. If there is a related issue it might make sense to skip this why section. -->
+<!-- This "Why" section is most relevant if there are no linked issues explaining why. If there is a related issue, it might make sense to skip this why section. -->
 <!--
 ## Why are we doing this? Any context or related work?
 -->
@@ -35,10 +35,10 @@ Updates (new versions of included code)
 <!--
 My changes do not require a change to the project documentation.
 My changes require a change to the project documentation.
-If a docs change is needed: I have updated the documentation accordingly.
+If documentation change is needed: I have updated the documentation accordingly.
 -->
 
-<!-- Please show how you tested the PR. This will really help if the PR needs to be retested, and probably help the PR get merged quicker. -->
+<!-- Please show how you tested the PR. This will really help if the PR needs to be retested and probably help the PR get merged quicker. -->
 
 # Testing
 
@@ -47,7 +47,7 @@ If a docs change is needed: I have updated the documentation accordingly.
 ## Detailed testing steps
 
 <!--
-None, automated tests are fine.
+None: Automated tests are acceptable.
 -->
 
 <!--
@@ -63,22 +63,22 @@ None, automated tests are fine.
 ### After
 -->
 
-<!-- If there is anything about the deploy, please make a note. -->
+<!-- If there is anything about the deployment, please make a note. -->
 <!--
 # Deploy Notes
 -->
 
-<!--  Copy and paste commandline output. -->
+<!--  Copy and paste command line output. -->
 <!--
 ## Database changes
 -->
 
-<!--  If there is something more than the automated steps, please specifiy deploy instructions. -->
+<!--  Please specify deploy instructions if there is something more than the automated steps. -->
 <!--
 ## Deployment instructions
 -->
 
-<!-- If you are on Discord, please join https://discord.gg/ai16z and state your Discord username here for contribute role and join us in #development-feed -->
+<!-- If you are on Discord, please join https://discord.gg/ai16z and state your Discord username here for the contributor role and join us in #development-feed -->
 <!--
 ## Discord username
 

.github/workflows/jsdoc-automation.yml

@@ -0,0 +1,87 @@
+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
+      branch:
+        description: 'Target branch for PR (defaults to develop)'
+        required: false
+        default: 'develop'
+        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: scripts/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: scripts/jsdoc-automation
+        run: pnpm install --no-frozen-lockfile
+
+      - name: Run documentation generator
+        working-directory: scripts/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 }}
+          INPUT_BRANCH: ${{ inputs.branch }}

.github/workflows/stale.yml

@@ -12,13 +12,23 @@ jobs:
       issues: write
       pull-requests: write
 
+    env:
+      DAYS_BEFORE_STALE: 30  # Define the days-before-stale value
+      DAYS_BEFORE_CLOSE: 7   # Define the days-before-close value
+
     steps:
     - uses: actions/stale@v5
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
-        stale-issue-message: 'This issue has been automatically marked as stale due to inactivity.'
-        stale-pr-message: 'This pull request has been automatically marked as stale due to inactivity.'
+        stale-issue-message: |
+          This issue has been automatically marked as stale due to ${{
+          env.DAYS_BEFORE_STALE }} days of inactivity.
+          If no further activity occurs within ${{ env.DAYS_BEFORE_CLOSE }} days, it will be closed automatically. Please take action if this issue is still relevant.
+        stale-pr-message: |
+          This pull request has been automatically marked as stale due to ${{
+          env.DAYS_BEFORE_STALE }} days of inactivity.
+          If no further activity occurs within ${{ env.DAYS_BEFORE_CLOSE }} days, it will be closed automatically. Please take action if this pull request is still relevant.
         stale-issue-label: 'no-issue-activity'
         stale-pr-label: 'no-pr-activity'
-        days-before-stale: 30  # Marks issues and PRs as stale after X days of inactivity
-        days-before-close: 7  # Closes issues and PRs X days after being marked as stale
+        days-before-stale: ${{ env.DAYS_BEFORE_STALE }}  
+        days-before-close: ${{ env.DAYS_BEFORE_CLOSE }}  

.gitignore

@@ -45,11 +45,11 @@ packages/core/src/providers/cache
 packages/core/src/providers/cache/*
 cache/*
 packages/plugin-coinbase/src/plugins/transactions.csv
-packages/plugin-coinbase/package-lock.json
 
 tsup.config.bundled_*.mjs
 
 .turbo
+.cursorrules
 
 coverage
 .eslintcache

CHANGELOG.md

@@ -1224,4 +1224,4 @@
 
 
 
-\* *This Changelog was automatically generated by [github_changelog_generator](https://github.com/github-changelog-generator/github-changelog-generator)*
+\* *This Changelog was automatically generated by [github_changelog_generator](https://github.com/github-changelog-generator/github-changelog-generator)*

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.