{
  "prompt_name": "intel",
  "category": "strategy",
  "date": "2025-12-20",
  "generated_text": "# ElizaOS Strategic Intel \u2014 2025-12-20\n\n## 1) Quantitative Pulse (Last observed day: 2025-12-19)\n\n### Development velocity (GitHub: elizaOS/eliza, 2025-12-19)\n- PRs: **0 opened / 1 merged**\n- Issues: **0 created**\n- Contributors active: **2**\n- Merged PR: **#6261** \u201cbootstrap action/provide format change fix + initPromise fix\u201d (stability + plugin compatibility)\n\n**Signal:** low throughput day, but shipping \u201cplumbing\u201d fixes that unblock ecosystem work (plugins + cloud). Risk of slipping schedule if release-critical work is waiting on non-code dependencies (NPM token, merge order).\n\n### Community engagement (Discord, 2025-12-19)\nPrimary discussion concentration by theme:\n- **Token migration + price sentiment** (dominant; repeated Q&A, confusion on eligibility/utility)\n- **Cloud streaming release readiness** (core-devs; explicit dependency chain)\n- **EVM/onchain capability confidence** (coders; questions about plugin-evm viability)\n- **Knowledge repo + analytics endpoints** (coders/core-devs; new JSON endpoints + infographic idea)\n\n**Signal:** community attention is heavily skewed to migration/price narrative; engineering narrative needs a clearer \u201cwhat shipped / what\u2019s next\u201d bridge to reduce churn.\n\n---\n\n## 2) Data Pattern Recognition\n\n### 2.1 Release-critical dependency chain (Cloud streaming)\nA clear operational pattern emerged:\n1) **Release monorepo**\n2) **Review/merge elizacloud-plugin**\n3) **Update cloud-v2 to latest core**\n4) Ensure elizacloud-plugin uses **stable core version (not old alpha)**\n\n**Bottlenecks / failure modes**\n- Tooling dependency: **NPM token change/deletion of classic tokens** blocking releases.\n- Integration risk: plugin pinned to older core \u2192 \u201cworks locally\u201d but fails in cloud-v2.\n- Process risk: multi-repo sequencing increases coordination overhead and regression risk.\n\n### 2.2 Onchain capability perception gap (EVM)\n- Users are actively questioning whether **plugin-evm is the \u201cgo-to\u201d** and if it\u2019s maintained.\n- Team signals ongoing work (Spartan EVM support PR), but this is not landing as \u201ctrusted default.\u201d\n\n**Pattern:** capability exists-in-progress, but \u201cblessed path\u201d is unclear \u2192 users seek alternatives and may build off-platform.\n\n### 2.3 Migration narrative as a retention risk\n- Confirmed deadline: **2026-02-04**; after that, **unmigrated tokens abandoned** and supply locked.\n- Repeated user confusion: \u201c0 eligible,\u201d exchange snapshot discrepancies, \u201cai16z still tradable\u201d confusion.\n- Sentiment: mixed; frustration with price decline is persistent and cross-day (12-17 to 12-19).\n\n**Pattern:** migration is functioning as both support burden and sentiment amplifier; the same questions recur \u2192 missing single-source canonical guidance.\n\n---\n\n## 3) User Experience Intelligence\n\n### 3.1 Feedback themes (impact x frequency)\n**High impact / High frequency**\n- **Migration clarity & safety**: eligibility (\u201c0 eligible\u201d), exchange snapshot rules, official ticker, \u201cshould I buy ai16z\u201d confusion.\n- **Perceived product delivery gap**: price-driven sentiment maps to \u201cwhat shipped?\u201d uncertainty.\n\n**High impact / Medium frequency**\n- **Cloud streaming reliability expectations**: users/devs want streaming to \u201cjust work\u201d across simple messages + actions, with clear rollout status.\n- **Onchain plugin confidence**: uncertainty about maintenance status; asks for recommended stack.\n\n**Medium impact / Medium frequency**\n- **Plugin/dev ergonomics**: version pinning, TypeScript compatibility issues, action registration patterns, provider performance debates (parallelism + timeouts).\n\n### 3.2 Usage patterns vs intended design (observed mismatches)\n- Users treat Discord as the primary migration support surface; this increases exposure to impersonation/scam risk and increases repetitive load.\n- Developers expect plugins to remain compatible across core changes, but **format changes (bootstrap action/provide)** required a fix (PR #6261). This indicates plugin API stability needs stronger guardrails (semver + migration notes + CI for plugins).\n\n### 3.3 Implementation opportunities (UX + support load reduction)\n- Convert repeated Q&A into **in-product / docs-driven flows**:\n  - Migration \u201celigibility troubleshooting\u201d wizard\n  - Exchange snapshot FAQ with examples (Kraken/Bithumb patterns)\n  - Clear \u201cai16z has no utility\u201d banner with safe links\n\n---\n\n## 4) Strategic Prioritization (Impact vs Risk)\n\n### P0 \u2014 Must execute (next 3\u20135 days)\n1) **Unblock releases (NPM token + release pipeline)**\n   - **User impact:** high (blocks cloud streaming release)\n   - **Tech risk:** medium (release creds + automation changes)\n   - **Recommendation:** assign single owner; rotate backup; add runbook + validation step for token rotation.\n\n2) **Ship cloud streaming via the defined sequence**\n   - **User impact:** high (visible product progress; reduces \u201cno delivery\u201d narrative)\n   - **Tech risk:** medium-high (multi-repo dependency + version pinning pitfalls)\n   - **Recommendation:** create a \u201crelease checklist PR\u201d (tracking issue) that gates each step with explicit version numbers and smoke tests.\n\n3) **Stabilize elizacloud-plugin core version targeting**\n   - **User impact:** high (prevents production breakage)\n   - **Tech risk:** medium\n   - **Recommendation:** enforce via CI: fail builds if plugin depends on alpha core when stable exists; document supported core range.\n\n### P1 \u2014 High leverage (next 1\u20132 weeks)\n4) **Canonical \u201cMigration Center\u201d documentation + pinned messaging**\n   - **User impact:** high (reduces confusion + support load; improves trust)\n   - **Tech risk:** low\n   - **Recommendation:** publish a single page with:\n     - deadline + consequences\n     - eligibility checklist (\u201c0 eligible\u201d paths)\n     - safe official links + scam warnings\n     - exchange snapshot explanation patterns\n   - Add Discord bot autoreply for top 5 repeated questions linking to this page.\n\n5) **EVM capability positioning (\u201cblessed path\u201d)**\n   - **User impact:** medium-high (retains builders; reduces fragmentation)\n   - **Tech risk:** medium\n   - **Recommendation:** publish a short \u201cOnchain integrations: recommended options\u201d doc:\n     - what plugin-evm supports today\n     - what Spartan EVM work changes\n     - maintenance status + roadmap\n     - minimal working example + test vector\n\n### P2 \u2014 Foundational improvements (2\u20134 weeks)\n6) **Plugin API compatibility contract**\n   - **User impact:** medium-high (reduces ecosystem breakage)\n   - **Tech risk:** medium-high\n   - **Recommendation:** introduce:\n     - deprecation window policy\n     - changelog entries for plugin-facing breaking changes\n     - integration tests across top plugins (discord/telegram/cloud/sql/bootstrap)\n\n7) **Provider performance guidance + tooling**\n   - **User impact:** medium (fewer timeouts; better reliability)\n   - **Tech risk:** medium\n   - **Recommendation:** merge/align provider parallelism approach (avoid duplicated PRs), and ship warning logs + caching best practices.\n\n---\n\n## 5) Resource Allocation Recommendation (pragmatic, near-term)\n- **1 Release captain (50\u201370% for 1 week):** NPM token + monorepo\u2192plugin\u2192cloud-v2 sequence, smoke tests, rollback plan.\n- **1 Dev (30\u201340% for 1 week):** EVM \u201cblessed path\u201d doc + minimal example + validation of current plugin-evm status.\n- **1 DevRel/Support (20\u201330% for 1 week):** Migration Center doc + Discord pin/autoreply + scam-safety language.\n\n---\n\n## 6) Key Risks to Track\n- **Operational:** release blocked by credential/token management; repeat occurrence likely without runbook + ownership.\n- **Ecosystem:** plugin compatibility breaks from core changes; developers lose time updating action/provider formats.\n- **Community trust:** migration confusion + price sentiment dominates discourse; absence of visible shipping milestones compounds negativity.\n- **Adoption:** unclear onchain path leads builders to alternatives, reducing ElizaOS ecosystem gravity.\n\n---\n\n## 7) Actionable Next Steps (24\u201372 hours)\n1) Create a **single tracking issue** for \u201cCloud streaming Monday release\u201d with:\n   - exact versions, merge order, owners, smoke test checklist, go/no-go criteria.\n2) Resolve **NPM token** and update CI secrets; add **release runbook** + \u201ccredential rotation\u201d procedure.\n3) Merge/fix **elizacloud-plugin core version** to stable; add CI guardrails for version pinning.\n4) Publish **Migration Center** v1 and pin in Discord (discussion + migration-support); add bot response for \u201c0 eligible\u201d, \u201cdeadline\u201d, \u201cticker\u201d, \u201cai16z utility\u201d.\n5) Post a short weekly \u201cWhat shipped / What\u2019s next\u201d update tying:\n   - merged PRs (e.g., #6261)\n   - streaming readiness\n   - EVM progress\n   - knowledge repo analytics endpoints (and intended use cases).",
  "source_references": [
    "2025-12-20\n---\n2025-12-19.md\n---\n# elizaOS Discord - 2025-12-19\n\n## Overall Discussion Highlights\n\n### Token Migration & Ecosystem\n- The community continues to discuss the migration from ai16z to elizaOS tokens, with mixed sentiments\n- February 4, 2026 is the confirmed deadline for token migration, after which unmigrated tokens will be abandoned\n- Some users expressed frustration about price decline while others remain optimistic\n- Clarification that ai16z no longer has utility and elizaOS is the path forward, though ai16z remains tradable on DEXs\n\n### Development Progress\n- **Cloud Streaming Functionality**: Team preparing for Monday release with streaming capabilities\n- **EVM Support**: Ongoing development work on EVM support for Spartan with active PRs\n- **Knowledge Repository**: Updates to the repository providing data for building agents that can reason with activity in the elizaOS ecosystem\n- **GitHub Analytics**: New JSON endpoints for leaderboards and summaries at different time intervals (daily, weekly, monthly)\n- **Plugin Development**: Odilitime shared a GitHub repository for an engagement plugin and mentioned committing recent work\n\n### Technical Infrastructure\n- Monorepo management workflow established: release monorepo first, then review/merge elizacloud-plugin, finally update core version in cloud-v2\n- NPM token issues being addressed as NPM changed their tokens and deleted classic tokens\n- Conversation blocking issue fixed when no summary existed, improving chat creation\n\n## Key Questions & Answers\n\n**Q: What happens to unmigrated tokens after the deadline?**  \nA: The unmigrated tokens will be abandoned in the old contract, and no more tokens will be minted after February 4, 2026, making the supply completely locked. (Kenk)\n\n**Q: How can I migrate my ai16z tokens if I have 0 eligible?**  \nA: Go to the migration-support channel. (Omid Sa)\n\n**Q: Should I buy ai16z?**  \nA: No. (Serikiki)\n\n**Q: What's the elizaOS ticker?**  \nA: It's elizaos. (Serikiki)\n\n**Q: Why is ai16z still pumping despite the migration?**  \nA: The token having no utility doesn't mean it doesn't have a market; it's still available on DEXs so people may pump it for various reasons. (Serikiki)\n\n**Q: Is there anything else remaining for streaming on cloud?**  \nA: Need to release monorepo, review/merge elizacloud-plugin, and use latest core version into cloud-v2, in that order. (Stan \u26a1)\n\n## Community Help & Collaboration\n\n- **Token Migration Support**: Omid Sa directed roybot to the migration-support channel when they couldn't migrate tokens and had \"0 eligible\" showing\n- **Token Status Clarification**: Serikiki and Odilitime helped multiple users understand the current status of ai16z vs elizaOS\n- **EVM Capabilities**: Odilitime shared a PR showing ongoing development work on EVM support in response to Roman V's concerns\n- **Knowledge Repository**: Jin shared updated information on the knowledge repository and various API endpoints for data integration to help Roman V with onchain capabilities\n- **GitHub Analytics**: Jin fixed and merged a feature for JSON endpoints for leaderboard in the knowledge repo submitted by 0xbbjoker\n\n## Action Items\n\n### Technical\n- Release monorepo before merging elizacloud-plugin (Mentioned by Stan \u26a1)\n- Review and merge elizacloud-plugin for streaming on cloud (Mentioned by Stan \u26a1)\n- Update cloud-v2 to use latest core version (Mentioned by Stan \u26a1)\n- Fix core version on elizacloud-plugin to use stable version instead of old alpha (Mentioned by Stan \u26a1)\n- Get new NPM token for release as classic token was deleted (Mentioned by cjft)\n- Complete Monday release with streaming functionality (Mentioned by Borko)\n- Update GitHub repository with latest code for engagement plugin (Mentioned by Odilitime)\n- Review and potentially contribute to the plugin-evm pull request for improved EVM support (Mentioned by Odilitime)\n- Explore the knowledge repository for building agents that can reason with elizaOS ecosystem activity (Mentioned by Jin)\n- Investigate using nano banana pro with knowledge data to generate infographics (Mentioned by Jin)\n\n### Documentation\n- Create clear explanation of token migration process and deadlines (Mentioned by roybot, Error P015-A)\n- Choose a name for the GitHub analytics project (currently considering \"GitScape\") (Mentioned by Jin)\n\n### Feature\n- Develop AI agents for internet support and customer service applications (Mentioned by Error P015-A)\n- Develop plugin-visualization to help make infographics from any data (Mentioned by Odilitime)\n---\n2025-12-18.md\n---\n# elizaOS Discord - 2025-12-18\n\n## Overall Discussion Highlights\n\n### Technical Development\n- **Starknet Plugin Integration**: FenrirFawks worked on integrating a Starknet plugin into ElizaOS, encountering TypeScript compatibility issues between `AgentRuntime` and `IAgentRuntime` types, and a missing handler error for deploying unruggable meme tokens.\n- **Provider Performance Optimization**: Stan proposed PR #6263 implementing parallel execution for providers with a configurable timeout (default 1s), which would abort the pipeline if providers take too long. This sparked a technical debate about proper provider implementation.\n- **Package Versioning**: Confirmation that `@elizaos/*` packages should continue using specific version pinning rather than `latest` tags in plugins.\n- **Hyperfy v0.16.0 Release**: Major update announced with AI integration capabilities (ChatGPT, Grok, Gemini), remote database support, XR/VR improvements, and new app features including primitive shape optimization and physics enhancements.\n\n### Project Status & Community Concerns\n- **Community Sentiment**: Significant frustration expressed in the discussion channel regarding token price decline and perceived lack of delivered products.\n- **Korean Community Concerns**: Several Korean users expressed feeling marginalized by the project leadership.\n- **Migration Issues**: Users reported problems with the migration from AI16Z to ELIZAOS, describing it as \"disastrous\" and a \"dilution.\"\n- **Project Defense**: Some community members defended the project, noting that building innovative products takes time and mentioning developments like a decentralized OTC desk and upcoming Babylon launch.\n\n## Key Questions & Answers\n\n### Technical\n- **Q**: In plugins are we using `latest` or pinning to a specific version for `@elizaos/*`?  \n  **A**: \"We are using specific versions. And I think that we should keep doing that.\" (Stan \u26a1)\n\n- **Q**: Is it normal I get type conversion issues in all the action's files?  \n  **A**: \"Yea they probably need to be updated. Cursor is great for that\" (Odilitime)\n\n- **Q**: What is the seal 991 hotline?  \n  **A**: \"It's 911, not 991. The SEAL 911 hotline is https://t.me/seal_911_bot for Web3 security emergencies.\" (jintern)\n\n### Project Status\n- **Q**: Since January of this year, has ELIZA delivered even a single tangible product, launch, or measurable achievement?  \n  **A**: \"A decentralized OTC desk is under development. Babylon also in the verge of lunching.\" (Omid Sa)\n\n## Community Help & Collaboration\n\n1. **Starknet Plugin Support**:\n   - Odilitime helped FenrirFawks with TypeScript compatibility issues, suggesting the action files needed updating and recommending Cursor for the task.\n   - jintern provided guidance on proper ElizaOS plugin CLI commands.\n\n2. **Provider Performance Optimization**:\n   - Stan and Odilitime collaborated on improving provider handling, eventually agreeing on implementing a configurable timeout with warnings for slow providers.\n\n3. **Migration Assistance**:\n   - The Light helped Freya who was stuck in AI16Z by providing a channel reference containing migration information.\n\n4. **Content Summarization**:\n   - jintern provided a concise summary of Skullcross's lengthy post about project concerns for other users.\n\n## Action Items\n\n### Technical\n- Implement parallel execution for providers with configurable timeout (default 1s) (Stan \u26a1)\n- Add warning logs for slow providers (e.g., \"\u26a0\ufe0f Provider X took 2500ms - consider caching\") (Stan \u26a1)\n- Review PR #6263 for provider performance improvements (Stan \u26a1)\n- Verify PR #6261 compatibility with latest develop branch (Odilitime)\n- Check if PR #6263 is a duplicate of PR #6209 (Odilitime)\n- Update action files to resolve type compatibility issues between AgentRuntime and IAgentRuntime (FenrirFawks)\n- Fix missing handler for delegate type in DEPLOY_STARKNET_UNRUGGABLE_MEME_TOKEN action (FenrirFawks)\n- Complete integration of Starknet plugin into the ElizaOS project (FenrirFawks)\n- Update existing apps that use world space nodes to handle the breaking change where apps remain active while being moved (Hyperfy)\n- Implement environment variable configuration for AI integration (ChatGPT, Grok, Gemini) (Hyperfy)\n- Test the new primitive shapes optimization for high-count scenarios (Hyperfy)\n\n### Documentation\n- Document best practices for providers (avoid API calls, use caching) (Odilitime)\n- Document the migration process from AI16Z to ELIZAOS more clearly (Freya)\n- Document the new animate event for distance-based animation (Hyperfy)\n- Update documentation for the breaking change regarding app.resetOnMove and app.isMoving (Hyperfy)\n- Document the new player.push(force) functionality (Hyperfy)\n- Document the new event.isLocalPlayer property for physics events (Hyperfy)\n\n### Feature Requests\n- Decentralized OTC desk mentioned as under development (Omid Sa)\n---\n2025-12-17.md\n---\n# elizaOS Discord - 2025-12-17\n\n## Overall Discussion Highlights\n\n### Development Updates\n- **Streaming Functionality**: Now working for simple messages and actions, with PRs in both eliza-cloud-v2 and eliza monorepo (shared by Stan)\n- **Discord Plugin**: Large PR with 66 commits is ready to merge after being open for three weeks (mentioned by Odilitime)\n- **Agent Actions Extension**: Discussions about how to properly extend agent functionality in the Starknet plugin environment, including creating new action files and registering them correctly\n\n### Token Migration Issues\n- **Exchange Handling Discrepancies**: Different exchanges (Bithumb and Kraken) are handling the AI16Z to ELIZAOS token swap differently, causing confusion\n- **Korean Community Concerns**: Frustration expressed about Bithumb exchange issues with the token swap, with requests for evidence of communications between the project team and Bithumb regarding snapshot timing\n- **Migration Confirmation**: Clarification that migration from AI16Z to ELIZAOS is still possible on Solana Network\n\n### Business Development\n- **Market Maker Requirements**: Market makers require agents to be deployed in production and actively engaging in social environments before further investment\n- **Product Development Philosophy**: Emphasis on having a live product that can be iteratively improved rather than waiting for perfection\n\n## Key Questions & Answers\n\n### Development\n- **Q**: How to add more actions for the agent when we can't see the starknet-plugin folder?  \n  **A**: \"Usually I just clone the plugin into the packages folder\" (Odilitime)\n\n- **Q**: How do we extend the current actions for the agent? Is creating a `zpaceship.ts` in the `actions` folder the right way?  \n  **A**: \"You should take a look at actions documentation and you also have to put it in src/index\" (Stan and Odilitime)\n\n- **Q**: Is it worth reviewing the Discord plugin PR before merging?  \n  **A**: Yes, but it's already 3 weeks old and getting too big (Odilitime)\n\n### Token Migration\n- **Q**: Is the $ai16z migration to $elizaOS still possible on Solana Network?  \n  **A**: Yes (Odilitime)\n\n- **Q**: Why Elizaos dump?  \n  **A**: Diamondhandwhiteboy suggested it was due to \"jeets\" (likely referring to retail investors selling)\n\n## Community Help & Collaboration\n\n1. **Plugin Development Assistance**\n   - **Helper**: Odilitime\n   - **Helpee**: FenrirFawks\n   - **Context**: Couldn't locate starknet-plugin folder to add more agent actions\n   - **Resolution**: Suggested cloning the plugin into the packages folder\n\n2. **Agent Actions Documentation**\n   - **Helper**: Stan\n   - **Helpee**: FenrirFawks\n   - **Context**: Needed guidance on extending agent actions\n   - **Resolution**: Provided documentation link about plugin components and actions\n\n3. **Exchange Token Swap Explanation**\n   - **Helper**: hildi\n   - **Helpee**: syanel4859\n   - **Context**: Explaining why exchanges might have difficulty with token swaps\n   - **Resolution**: Explained that centralized exchanges mix coins in shared wallets making it difficult to untangle, and advised not to keep crypto on exchanges\n\n4. **Kraken Token Swap Clarification**\n   - **Helper**: Serikiki\n   - **Helpee**: painfr\n   - **Context**: Confusion about how Kraken is handling token swaps\n   - **Resolution**: Clarified that Kraken would not give tokens to users who sold after the snapshot, explaining that exchanges distribute based on snapshot data\n\n## Action Items\n\n### Technical\n- Clone the plugin into the packages folder to access and modify it (Odilitime)\n- Create action files in the actions folder (like zpaceship.ts) (FenrirFawks)\n- Add new actions to src/index file (Odilitime)\n- Review and merge plugin-discord PR (https://github.com/elizaos-plugins/plugin-discord/pull/30) (Odilitime)\n- Ensure AI16Z migration to ELIZAOS on Solana Network is functioning properly (akshaydeep)\n\n### Documentation\n- Review plugin components documentation at https://docs.elizaos.ai/plugins/components (Stan)\n- Update/clean/sync documentation (Stan)\n- Provide clear documentation about exchange-specific token swap procedures (painfr)\n- Share evidence of communications with Bithumb regarding snapshot timing (syanel4859)\n- Check enterprise subscription solution for unspecified issue (Odilitime)\n\n### Feature\n- Consider implementing a more straightforward token swap mechanism for future migrations (Alexei)\n---\n2025-12-19.json\n---\nelizaosDailySummary\n---\nDaily Report - 2025-12-19\n---\nGitHub Activity Summary\n---\nOn December 19, 2025, the elizaOS/eliza repository showed moderate activity with 0 new PRs opened, 1 PR merged, 0 new issues created, and 2 active contributors working on the project.\n---\nIssues\n---\nIssue #6185 titled 'Optimize Agent Builder Model Selection' by @borisudovicic is CLOSED.\n---\nhttps://github.com/elizaOS/eliza/issues/6185\n---\nIssue #6259 titled 'Allow JSON export without deploying' by @borisudovicic is CLOSED.\n---\nhttps://github.com/elizaOS/eliza/issues/6259\n---\nIssue #6258 titled 'Rename chat assistant to \"Agent Builder\"' by @borisudovicic is CLOSED.\n---\nhttps://github.com/elizaOS/eliza/issues/6258\n---\nIssue #6257 titled 'Fix markdown bullet point rendering' by @borisudovicic is CLOSED.\n---\nhttps://github.com/elizaOS/eliza/issues/6257\n---\nIssue #6256 titled 'Fix gallery tab refresh behavior' by @borisudovicic is CLOSED.\n---\nhttps://github.com/elizaOS/eliza/issues/6256\n---\nPull Requests\n---\nPR #6261 by @elizaOS titled 'fix: bootstrap action/provide format change fix + initPromise fix' is completed, addressing bootstrap action formatting and initPromise issues.\n---\nhttps://github.com/elizaOS/eliza/pull/6261\n---\nSummary for github_other\n---\nThe repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input.\n---\n2025-12-19.md\n---\n# Daily Report - 2025-12-19\n\n## GitHub Activity Summary\n- On December 19, 2025, the elizaOS/eliza repository showed moderate activity with 0 new PRs opened, 1 PR merged, 0 new issues created, and 2 active contributors working on the project.\n\n## Issues\n- Issue #6185 titled 'Optimize Agent Builder Model Selection' by @borisudovicic is CLOSED. (Source: https://github.com/elizaOS/eliza/issues/6185)\n- Issue #6259 titled 'Allow JSON export without deploying' by @borisudovicic is CLOSED. (Source: https://github.com/elizaOS/eliza/issues/6259)\n- Issue #6258 titled 'Rename chat assistant to \"Agent Builder\"' by @borisudovicic is CLOSED. (Source: https://github.com/elizaOS/eliza/issues/6258)\n- Issue #6257 titled 'Fix markdown bullet point rendering' by @borisudovicic is CLOSED. (Source: https://github.com/elizaOS/eliza/issues/6257)\n- Issue #6256 titled 'Fix gallery tab refresh behavior' by @borisudovicic is CLOSED. (Source: https://github.com/elizaOS/eliza/issues/6256)\n\n## Pull Requests\n- PR #6261 by @elizaOS titled 'fix: bootstrap action/provide format change fix + initPromise fix' is completed, addressing bootstrap action formatting and initPromise issues. (Source: https://github.com/elizaOS/eliza/pull/6261)\n\n## Summary for github_other\n- The repository elizaOS/eliza has a list of top contributors, though specific contributor details are not provided in the input.\n---\n2025-12-19.json\n---\nelizaOS\n---\nelizaOS Discord - 2025-12-19\n---\n1253563209462448241\n---\n\ud83d\udcac-discussion\n---\n# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around the migration from ai16z to elizaOS tokens, with community members expressing mixed sentiments about the project's direction. Several users voiced frustration about the token's price decline from previous highs, while others remained optimistic. Key technical points discussed include the February 4, 2026 deadline for token migration, after which unmigrated tokens will be abandoned in the old contract and no more tokens will be minted. Odilitime shared a GitHub repository link for an engagement plugin (https://github.com/elizaos-plugins/plugin-engagement) and mentioned committing recent work soon. There was confusion from some users about the migration process, with one user (roybot) seeking help to migrate their tokens. The community clarified that ai16z no longer has utility and elizaOS is the path forward, though ai16z remains tradable on DEXs.\n\n## 2. FAQ\nQ: What happens to unmigrated tokens after the deadline? (asked by Error P015-A) A: The unmigrated tokens will be abandoned in the old contract, and no more tokens will be minted after February 4, 2026, making the supply completely locked. (answered by Kenk)\nQ: How can I migrate my ai16z tokens if I have 0 eligible? (asked by roybot) A: Go to the migration-support channel. (answered by Omid Sa)\nQ: Should I buy ai16z? (asked by maxon3d.) A: No. (answered by Serikiki)\nQ: What's the elizaOS ticker? (asked by maxon3d.) A: It's elizaos. (answered by Serikiki)\nQ: Why is ai16z still pumping despite the migration? (asked by maxon3d.) A: The token having no utility doesn't mean it doesn't have a market; it's still available on DEXs so people may pump it for various reasons. (answered by Serikiki)\n\n## 3. Help Interactions\nHelper: Omid Sa | Helpee: roybot | Context: User couldn't migrate tokens and had \"0 eligible\" showing | Resolution: Directed user to migration-support channel, which resolved the issue\nHelper: Kenk | Helpee: Error P015-A | Context: User was confused about migration deadline and token supply information | Resolution: Confirmed the plan details and explained migration volume has slowed down in recent weeks\nHelper: Serikiki | Helpee: anon | Context: User was confused about the status of ai16z | Resolution: Explained it's the old coin that was migrated to elizaOS\nHelper: Odilitime | Helpee: anon | Context: User asking about ai16z status | Resolution: Clarified that ai16z has no utility anymore and only elizaOS is moving forward\n\n## 4. Action Items\nTechnical: Update GitHub repository with latest code for engagement plugin | Description: Odilitime mentioned committing recent work to the plugin-engagement repository | Mentioned By: Odilitime\nDocumentation: Create clear explanation of token migration process and deadlines | Description: Multiple users were confused about migration eligibility and deadlines | Mentioned By: roybot, Error P015-A\nFeature: Develop AI agents for internet support | Description: Suggestion to use elizaOS for customer service applications | Mentioned By: Error P015-A\n---\n1300025221834739744\n---\n\ud83d\udcac-coders\n---\n# Discord Chat Analysis for \ud83d\udcac-coders Channel\n\n## 1. Summary:\nThe discussion centers around ElizaOS's blockchain capabilities, particularly its EVM (Ethereum Virtual Machine) support. Roman V expressed concerns about the plugin-evm's functionality and maintenance status, seeking alternatives for onchain capabilities. Jin shared updates about the ElizaOS roadmap and the knowledge repository, which provides data for building agents that can reason with activity in the ElizaOS ecosystem. Odilitime mentioned working on EVM support for Spartan and shared a pull request showing ongoing development. Jin also detailed various API endpoints in the knowledge repository that provide GitHub analytics data, including leaderboards and summaries at different time intervals (daily, weekly, monthly). Jin mentioned experimenting with using this data to generate infographics and is seeking a name for this GitHub analytics project.\n\n## 2. FAQ:\nQ: Is plugin-evm our actual go-to plugin for EVM capabilities? (asked by Roman V) A: Partially answered by Odilitime who shared a PR showing ongoing development work on EVM support\nQ: What are people using for onchain capabilities in ElizaOS? (asked by Roman V) A: Partially answered by Odilitime who mentioned working on EVM support for Spartan\nQ: Need a name for this project. GitScape? (asked by jin) A: Unanswered\n\n## 3. Help Interactions:\nHelper: jin | Helpee: Roman V | Context: Roman was looking for up-to-date information on ElizaOS's onchain capabilities | Resolution: Jin shared the updated knowledge repository and various API endpoints for data integration\nHelper: Odilitime | Helpee: Roman V | Context: Roman was concerned about plugin-evm functionality | Resolution: Odilitime shared a PR showing ongoing development work on EVM support\nHelper: Odilitime | Helpee: FenrirFawks | Context: Unspecified issue | Resolution: Suggested running with log level debug\n\n## 4. Action Items:\nTechnical: Review and potentially contribute to the plugin-evm pull request for improved EVM support | Mentioned By: Odilitime\nTechnical: Explore the knowledge repository for building agents that can reason with ElizaOS ecosystem activity | Mentioned By: jin\nTechnical: Investigate using nano banana pro with knowledge data to generate infographics | Mentioned By: jin\nFeature: Develop plugin-visualization to help make infographics from any data | Mentioned By: Odilitime\nDocumentation: Choose a name for the GitHub analytics project (currently considering \"GitScape\") | Mentioned By: jin\n---\n1301363808421543988\n---\n\ud83e\udd47-partners\n---\nThe chat segment is extremely brief, consisting of only a single message from user Odilitime sharing a Twitter/X link. There are no technical discussions, decisions, or problem-solving interactions present in this limited exchange. The content is insufficient to provide any meaningful technical summary.\n---\n1377726087789940836\n---\ncore-devs\n---\n# Discord Chat Analysis for \"core-devs\" Channel\n\n## 1. Summary\nThe core-devs team is working on several critical development tasks focused on cloud streaming functionality, monorepo management, and plugin integration. Stan fixed conflicts and reviews on cloud components and resolved a conversation blocking issue when no summary existed, improving chat creation. The team is preparing for a Monday release that requires releasing the monorepo first, then reviewing and merging the elizacloud-plugin, and finally updating the core version in cloud-v2. There was discussion about fixing the core version in the elizacloud-plugin to use a stable version rather than an old alpha. Jin fixed and merged a feature for JSON endpoints for leaderboard in the knowledge repo. The team is also dealing with NPM token issues as NPM changed their tokens and deleted their classic token. Additionally, several developer tools were shared including Bugster (an automated QA tester), claude-mem (a GitHub repository), and Claude's Chrome extension documentation.\n\n## 2. FAQ\nQ: Is there anything else remaining for streaming on cloud? (asked by Borko) A: Need to release monorepo, review/merge elizacloud-plugin, and use latest core version into cloud-v2, in that order. (answered by Stan \u26a1)\nQ: Should we fix the core version on the elizacloud plugin? (asked by Stan \u26a1) A: Unanswered\n\n## 3. Help Interactions\nHelper: jin | Helpee: 0xbbjoker | Context: Feature submitted to knowledge repo for JSON endpoints for leaderboard | Resolution: Fixed and merged the feature, updated readme in the knowledge repository\nHelper: Stan \u26a1 | Helpee: Team | Context: Conversation blocking issue when no summary existed | Resolution: Fixed the issue making new chat creation smoother\n\n## 4. Action Items\nType: Technical | Description: Release monorepo before merging elizacloud-plugin | Mentioned By: Stan \u26a1\nType: Technical | Description: Review and merge elizacloud-plugin for streaming on cloud | Mentioned By: Stan \u26a1\nType: Technical | Description: Update cloud-v2 to use latest core version | Mentioned By: Stan \u26a1\nType: Technical | Description: Fix core version on elizacloud-plugin to use stable version instead of old alpha | Mentioned By: Stan \u26a1\nType: Technical | Description: Get new NPM token for release as classic token was deleted | Mentioned By: cjft\nType: Technical | Description: Complete Monday release with streaming functionality | Mentioned By: Borko\n---\n2025-12-19.md\n---\n# elizaOS Discord - 2025-12-19\n\n## Overall Discussion Highlights\n\n### Token Migration & Ecosystem\n- The community continues to discuss the migration from ai16z to elizaOS tokens, with mixed sentiments\n- February 4, 2026 is the confirmed deadline for token migration, after which unmigrated tokens will be abandoned\n- Some users expressed frustration about price decline while others remain optimistic\n- Clarification that ai16z no longer has utility and elizaOS is the path forward, though ai16z remains tradable on DEXs\n\n### Development Progress\n- **Cloud Streaming Functionality**: Team preparing for Monday release with streaming capabilities\n- **EVM Support**: Ongoing development work on EVM support for Spartan with active PRs\n- **Knowledge Repository**: Updates to the repository providing data for building agents that can reason with activity in the elizaOS ecosystem\n- **GitHub Analytics**: New JSON endpoints for leaderboards and summaries at different time intervals (daily, weekly, monthly)\n- **Plugin Development**: Odilitime shared a GitHub repository for an engagement plugin and mentioned committing recent work\n\n### Technical Infrastructure\n- Monorepo management workflow established: release monorepo first, then review/merge elizacloud-plugin, finally update core version in cloud-v2\n- NPM token issues being addressed as NPM changed their tokens and deleted classic tokens\n- Conversation blocking issue fixed when no summary existed, improving chat creation\n\n## Key Questions & Answers\n\n**Q: What happens to unmigrated tokens after the deadline?**  \nA: The unmigrated tokens will be abandoned in the old contract, and no more tokens will be minted after February 4, 2026, making the supply completely locked. (Kenk)\n\n**Q: How can I migrate my ai16z tokens if I have 0 eligible?**  \nA: Go to the migration-support channel. (Omid Sa)\n\n**Q: Should I buy ai16z?**  \nA: No. (Serikiki)\n\n**Q: What's the elizaOS ticker?**  \nA: It's elizaos. (Serikiki)\n\n**Q: Why is ai16z still pumping despite the migration?**  \nA: The token having no utility doesn't mean it doesn't have a market; it's still available on DEXs so people may pump it for various reasons. (Serikiki)\n\n**Q: Is there anything else remaining for streaming on cloud?**  \nA: Need to release monorepo, review/merge elizacloud-plugin, and use latest core version into cloud-v2, in that order. (Stan \u26a1)\n\n## Community Help & Collaboration\n\n- **Token Migration Support**: Omid Sa directed roybot to the migration-support channel when they couldn't migrate tokens and had \"0 eligible\" showing\n- **Token Status Clarification**: Serikiki and Odilitime helped multiple users understand the current status of ai16z vs elizaOS\n- **EVM Capabilities**: Odilitime shared a PR showing ongoing development work on EVM support in response to Roman V's concerns\n- **Knowledge Repository**: Jin shared updated information on the knowledge repository and various API endpoints for data integration to help Roman V with onchain capabilities\n- **GitHub Analytics**: Jin fixed and merged a feature for JSON endpoints for leaderboard in the knowledge repo submitted by 0xbbjoker\n\n## Action Items\n\n### Technical\n- Release monorepo before merging elizacloud-plugin (Mentioned by Stan \u26a1)\n- Review and merge elizacloud-plugin for streaming on cloud (Mentioned by Stan \u26a1)\n- Update cloud-v2 to use latest core version (Mentioned by Stan \u26a1)\n- Fix core version on elizacloud-plugin to use stable version instead of old alpha (Mentioned by Stan \u26a1)\n- Get new NPM token for release as classic token was deleted (Mentioned by cjft)\n- Complete Monday release with streaming functionality (Mentioned by Borko)\n- Update GitHub repository with latest code for engagement plugin (Mentioned by Odilitime)\n- Review and potentially contribute to the plugin-evm pull request for improved EVM support (Mentioned by Odilitime)\n- Explore the knowledge repository for building agents that can reason with elizaOS ecosystem activity (Mentioned by Jin)\n- Investigate using nano banana pro with knowledge data to generate infographics (Mentioned by Jin)\n\n### Documentation\n- Create clear explanation of token migration process and deadlines (Mentioned by roybot, Error P015-A)\n- Choose a name for the GitHub analytics project (currently considering \"GitScape\") (Mentioned by Jin)\n\n### Feature\n- Develop AI agents for internet support and customer service applications (Mentioned by Error P015-A)\n- Develop plugin-visualization to help make infographics from any data (Mentioned by Odilitime)\n---\n2025-12-20.md\n---\nFile not found\n---\n2025-12-14.md\n---\n# elizaos/eliza Weekly Report (Dec 14 - 20, 2025)\n\n## \ud83d\ude80 Highlights\nThis week's efforts were characterized by a dual focus on backend stabilization and a significant strategic push toward enhancing the user experience. Key technical work centered on critical bug fixes, including a robust optimization of the SQL plugin to ensure smooth schema migrations for users updating from older versions. Concurrently, a large volume of new issues were opened, outlining a comprehensive roadmap for a major UI/UX overhaul. This initiative aims to simplify the user journey, from onboarding and agent creation to replacing technical jargon with more accessible language, signaling a clear focus on usability and broader adoption.\n\n## \ud83d\udee0\ufe0f Key Developments\nWhile no new features were merged, crucial work was completed to improve the stability and reliability of the core system and its development environment.\n\n- **SQL Plugin Migration and Optimization:** To ensure backward compatibility and a seamless update process, the SQL plugin was enhanced to handle smooth data migration from pre-1.6.5 (camelCase) schemas to the current standard ([#6215](https://github.com/elizaos/eliza/pull/6215)). This effort also included optimizations for Row-Level Security (RLS) handling and the addition of comprehensive test coverage to guarantee idempotency.\n\n- **CLI and Testing Infrastructure Fixes:** Development reliability was improved by addressing test failures. A key fix resolved an API signature mismatch in the CLI's end-to-end tests that was causing command failures ([#6207](https://github.com/elizaos/eliza/pull/6207)). Additionally, a unit test mock function was corrected to ensure accurate character retrieval testing.\n\n## \ud83d\udc1b Issues & Triage\nThe week saw a flurry of activity in issue tracking, with a clear emphasis on planning future work related to user experience and new capabilities.\n\n- **Closed Issues:** Two recently opened UI issues were quickly resolved, improving the plugin selection process. The changes provide better visual feedback on selection ([#6235](https://github.com/elizaos/eliza/issues/6235)) and implement a more intuitive toggle behavior, replacing the previous plus button ([#6236](https://github.com/elizaos/eliza/issues/6236)).\n\n- **New & Active Issues:** A significant number of new issues were created, collectively forming a detailed plan for a user-centric redesign. Key themes include:\n    - **Onboarding and Dashboard:** Proposals to redesign the dashboard to prioritize agent creation ([#6222](https://github.com/elizaos/eliza/issues/6222), [#6225](https://github.com/elizaos/eliza/issues/6225)) and implement guided onboarding overlays for new users ([#6221](https://github.com/elizaos/eliza/issues/6221)).\n    - **Simplifying Terminology:** A concerted effort to improve accessibility by replacing technical terms in the UI, such as \"Knowledge\" with \"Files\" ([#6237](https://github.com/elizaos/eliza/issues/6237]), removing \"RAG\" in favor of plain language ([#6240](https://github.com/elizaos/eliza/issues/6240)), and using \"Services\" instead of \"MCP\" ([#6241](https://github.com/elizaos/eliza/issues/6241)).\n    - **Agent Management UX:** Numerous suggestions were made to streamline agent interaction, including renaming \"Save\" to \"Deploy\" ([#6232](https://github.com/elizaos/eliza/issues/6232]), adding quick-action menus to agent cards ([#6234](https://github.com/elizaos/eliza/issues/6234)), and improving the file upload process ([#6238](https://github.com/elizaos/eliza/issues/6238)).\n    - **Future Capabilities:** Planning for major new features has begun, with issues opened to implement web search functionality ([#6246](https://github.com/elizaos/eliza/issues/6246)) and to create a guide for AI agent payments ([#6244](https://github.com/elizaos/eliza/issues/6244)).\n\n## \ud83d\udcac Community & Collaboration\nThe provided reports do not indicate a high degree of discussion on specific PRs or issues. However, the large, coordinated creation of dozens of UI/UX-focused issues on a single day suggests a focused product or design review session occurred. This activity has generated a clear and detailed backlog for upcoming development sprints. The rapid closure of two UI issues just a day after their creation demonstrates a responsive and agile development process.\n---\n2025-12-01.md\n---\n# elizaos/eliza Monthly Report (December 2025)\n\n## \ud83d\ude80 Highlights\nDecember was a month of foundational improvements and strategic planning. Development focused on enhancing core stability through significant server refactoring, dependency updates, and widespread TypeScript error resolution. This backend work was complemented by a major push to refine the user experience, with numerous UI/UX issues closed and a comprehensive set of new issues opened to guide a future overhaul of the agent creation workflow and dashboard. Key new capabilities were introduced, including a unified serverless API and streamlined ElizaOS Cloud integration in the CLI, setting the stage for greater scalability and ease of use.\n\n## \ud83d\udee0\ufe0f Key Developments\nThis month's efforts were balanced between strengthening the existing codebase and introducing new, strategic features.\n\n-   **Core Stability and Modernization:**\n    -   A major server refactoring optimized the codebase and reorganized API endpoints and services ([#6199](https://github.com/elizaos/eliza/pull/6199)).\n    -   Server reliability was enhanced by properly configuring Socket.IO timeouts and implementing explicit HTTP server timeouts ([#6198](https://github.com/elizaos/eliza/issues/6198)).\n    -   A comprehensive effort resolved TypeScript build errors across numerous packages, including `core`, `server`, `client`, and `cli`, ensuring type safety and code stability ([#6218](https://github.com/elizaos/eliza/pull/6218)).\n    -   All monorepo dependencies were updated to their latest versions, resolving compatibility conflicts, particularly with `drizzle-orm` ([#6210](https://github.com/elizaos/eliza/pull/6210)).\n\n-   **New Features & Integrations:**\n    -   A unified API for serverless Node.js environments was implemented, streamlining core functionalities for broader deployment options ([#6201](https://github.com/elizaos/eliza/pull/6201)).\n    -   The CLI was enhanced to make ElizaOS Cloud the default AI provider, featuring a new browser-based login flow to simplify API key setup ([#6208](https://github.com/elizaos/eliza/pull/6208)).\n    -   Work began on JWT authentication and user management ([#6200](https://github.com/elizaos/eliza/pull/6200)) and parallel action execution ([#6209](https://github.com/elizaos/eliza/pull/6209)).\n\n-   **Plugin and CLI Enhancements:**\n    -   The SQL plugin was significantly improved with smooth schema migration for backward compatibility, optimized Row-Level Security (RLS) handling, and auto-creation of PGLite directories ([#6215](https://github.com/elizaos/eliza/pull/6215), [#6202](https://github.com/elizaos/eliza/pull/6202)).\n    -   Standalone examples were modernized to use the new `messageService.handleMessage()` API, deprecating the old event system ([#6202](https://github.com/elizaos/eliza/pull/6202)).\n    -   An API signature mismatch in the CLI's end-to-end tests was corrected, restoring test reliability ([#6207](https://github.com/elizaos/eliza/pull/6207)).\n\n-   **Bug Fixes and Code Quality:**\n    -   A critical security bug in character secret encryption was fixed to ensure the correct order of operations ([#6217](https://github.comcom/elizaos/eliza/pull/6217)).\n    -   Markdown rendering issues causing inconsistent spacing in the client UI were resolved ([#6159](https://github.com/elizaos/eliza/pull/6159), [#6197](https://github.com/elizaos/eliza/pull/6197)).\n    -   A substantial code cleanup removed technical debt by fixing `any`/`unknown` types, eliminating dead code, and removing unnecessary `try-catch` blocks ([#6213](https://github.com/elizaos/eliza/pull/6213)).\n\n## \ud83d\udc1b Issues & Triage\nIssue management this month was characterized by clearing a backlog of UI/UX tickets and defining a clear roadmap for future front-end development.\n\n-   **Closed Issues:**\n    -   **UI/UX Simplification:** A large number of issues were resolved to streamline the user interface. This included consolidating sidebar navigation ([#6173](https://github.com/elizaos/eliza/issues/6173)), cleaning up user info ([#6174](https://github.com/elizaos/eliza/issues/6174)), implementing a distinct \"Build Mode\" theme ([#6177](https://github.com/elizaos/eliza/issues/6177)), adding an \"Unsaved Changes\" warning ([#6183](https://github.com/elizaos/eliza/issues/6183)), and improving plugin selection feedback ([#6235](https://github.com/elizaos/eliza/issues/6235), [#6236](https://github.com/elizaos/eliza/issues/6236)).\n    -   **Bug Fixes:** Critical bugs were addressed, including a container deployment failure ([#6187](https://github.com/elizaos/eliza/issues/6187)), server connection timeouts ([#6198](https://github.com/elizaos/eliza/issues/6198)), and an issue preventing the SQL plugin from starting without a pre-existing directory ([#6204](https://github.com/elizaos/eliza/issues/6204)).\n    -   **Documentation:** The long-standing documentation issue was closed with the launch of a new public docs UI featuring an API explorer ([#6128](https://github.com/elizaos/eliza/issues/6128)).\n\n-   **New & Active Issues:**\n    -   **Strategic UI/UX Overhaul:** A significant batch of over 20 issues was opened on Dec 15, outlining a comprehensive plan to improve user onboarding and agent management. Key proposals include a redesigned dashboard ([#6222](https://github.com/elizaos/eliza/issues/6222)), guided onboarding overlays ([#6221](https://github.com/elizaos/eliza/issues/6221)), and simplifying terminology like \"RAG\" to \"Files\" ([#6237](https://github.com/elizaos/eliza/issues/6237), [#6240](https://github.com/elizaos/eliza/issues/6240)).\n    -   **Future Features:** The groundwork for future development was laid with new issues for implementing streaming support ([#6206](https://github.com/elizaos/eliza/issues/6206)) and web search functionality ([#6246](https://github.com/elizaos/eliza/issues/6246)).\n    -   **Community & Web3 Challenges:** Users reported challenges with the AI16Z \u2192 ElizaOS migration, specifically concerning snapshot eligibility for tokens held in Tangem wallets ([#6158](https://github.com/elizaos/eliza/issues/6158), [#6211](https://github.com/elizaos/eliza/issues/6211)). This highlights a key area of concern for the Web3 portion of the community.\n    -   **Persistent Bugs:** The long-standing Twitter plugin database error ([#39](https://github.com/elizaos/eliza/issues/39)) remains active, with a new comment confirming the issue persists in recent versions, indicating a challenging underlying problem.\n\n## \ud83d\udcac Community & Collaboration\nCollaboration this month was evident in both strategic planning and community support. The large, coordinated creation of UI/UX issues on December 15 suggests a focused effort by the core team to define the project's next steps for front-end development. Concurrently, active discussions around token migration and wallet support ([#6158](https://github.com/elizaos/eliza/issues/6158), [#6211](https://github.com/elizaos/eliza/issues/6211)) demonstrate the project's responsiveness to direct feedback from its Web3 user base. Finally, community members continued to collaborate on diagnosing persistent, older issues like the Twitter plugin bug ([#39](https://github.com/elizaos/eliza/issues/39)), showcasing ongoing engagement in maintaining the ecosystem's health.\n---\n{\n  \"interval\": {\n    \"intervalStart\": \"2025-12-01T00:00:00.000Z\",\n    \"intervalEnd\": \"2026-01-01T00:00:00.000Z\",\n    \"intervalType\": \"month\"\n  },\n  \"repository\": \"elizaos/eliza\",\n  \"overview\": \"From 2025-12-01 to 2026-01-01, elizaos/eliza had 23 new PRs (15 merged), 45 new issues, and 18 active contributors.\",\n  \"topIssues\": [\n    {\n      \"id\": \"I_kwDOMT5cIs7V2Buf\",\n      \"title\": \"Where did packages/docs/ go?\",\n      \"author\": \"LinuxIsCool\",\n      \"number\": 6122,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"There was always packages/docs/ where did it get moved to?\",\n      \"createdAt\": \"2025-11-04T18:08:54Z\",\n      \"closedAt\": \"2025-12-01T14:35:46Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 2\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs7cPNBC\",\n      \"title\": \".eliza needed or plugin-sql crashes, should autocreate\",\n      \"author\": \"lalalune\",\n      \"number\": 6204,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"You can see here, I am building an Eliza agent from scratch\\n\\n```\\nimport { AgentRuntime, type Character, type Plugin } from \\\"@elizaos/core\\\";\\nimport { plugin } from \\\"@elizaos/plugin-sql\\\"\\nimport { openaiPlugin } from \\\"@elizaos/plugin-openai\\\"\\nimport fs from \\\"fs\\\";\\n\\n// if .eliza directory does not exist, create it\\nif (!fs.existsSync(\\\".eliza\\\")) {\\n    fs.mkdirSync(\\\".eliza\\\");\\n}\\n\\nconst character: Character = {\\n    name: \\\"Eliza\\\",\\n    bio: \\\"You are a helpful assistant\\\",\\n};\\n\\nconst plugins: Plugin[] = [\\n    plugin,\\n    openaiPlugin,\\n];\\n\\nconst agent = new AgentRuntime({\\n    character, // need a character to start the agent\\n    plugins // bare minimum is db plugin and inference plugin\\n});\\n\\nagent.initialize().then(() => {\\n    console.log(\\\"Agent initialized\\\");\\n\\n\\n});\\n```\\n\\nIn order to get it to work I have to add\\n```\\nimport fs from \\\"fs\\\";\\n\\n// if .eliza directory does not exist, create it\\nif (!fs.existsSync(\\\".eliza\\\")) {\\n    fs.mkdirSync(\\\".eliza\\\");\\n}\\n```\\n\\nBut this should happen automatically\",\n      \"createdAt\": \"2025-12-04T14:37:44Z\",\n      \"closedAt\": \"2025-12-08T13:17:08Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 1\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs7cwyy7\",\n      \"title\": \"Snapshot Eligibility Issue + Tangem Wallet Connection Not Supported (Discord Support Compromised)\",\n      \"author\": \"pereslavlland\",\n      \"number\": 6211,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"Hi ElizaOS team,\\n\\nI\u2019m trying to complete the AI16Z \u2192 ElizaOS migration, but I\u2019m running into two major issues and Discord support has become unreliable due to impersonators. I need help from the real development team to determine the correct path.\\n\\nMy situation:\\n\\n\u2022 I purchased AI16Z tokens on Oct 26 using my Phantom wallet.\\n\u2022 I then moved them to my Tangem wallet for safety.\\n\u2022 On Nov 11 (snapshot date), the tokens were held inside my Tangem wallet.\\n\u2022 The migration portal shows my Phantom wallet as \u201c0 eligible\u201d (expected since Phantom didn\u2019t hold them during snapshot).\\n\u2022 I cannot connect my Tangem wallet to the migration portal because WalletConnect does not support Tangem.\\n\u2022 My Tangem wallet was created using key cards only, so I do not have a seed phrase to export into Phantom.\\n\\nThe Discord server is currently compromised \u2014 multiple impersonators posing as support are entering tickets and attempting to direct users to send tokens manually. Because of this, I cannot rely on Discord support or email responses that appear to be spoofed.\\n\\nWhat I need from the real team:\\n\\nConfirmation of whether Tangem-held tokens during the snapshot are eligible for migration.\\nWhether a manual backend whitelist update is possible so my Phantom wallet can perform migration safely.\\nIf not, what the official and safe method is for users whose eligible snapshot wallet cannot connect to the portal (Tangem case).\\nAny announcements regarding potential whitelist updates or support for non-exportable wallets.\\nI have NOT sent my tokens anywhere and I have NOT interacted with any unofficial links. My tokens are safe. I\u2019m only seeking official guidance from the verifiable team here on GitHub.\\n\\nThank you \u2014 I appreciate your time. I prefer to resolve this safely through GitHub to avoid Discord impersonation issues.\\n\\nActivity\\n\",\n      \"createdAt\": \"2025-12-07T18:00:25Z\",\n      \"closedAt\": null,\n      \"state\": \"OPEN\",\n      \"commentCount\": 1\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs7V2Gw0\",\n      \"title\": \"Docs\",\n      \"author\": \"borisudovicic\",\n      \"number\": 6128,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"* Build new /docs UI (public, not auth-locked).\\n* Include:\\n  * OpenAI-style API explorer.\\n  * Character setup & API key usage examples.\\n  * Overview of Cloud architecture.\",\n      \"createdAt\": \"2025-11-04T18:15:26Z\",\n      \"closedAt\": \"2025-12-10T14:27:42Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 0\n    },\n    {\n      \"id\": \"I_kwDOMT5cIs7YjZ7G\",\n      \"title\": \"can i use deepseek api?\",\n      \"author\": \"870171594\",\n      \"number\": 6156,\n      \"repository\": \"elizaos/eliza\",\n      \"body\": \"**Is your feature request related to a problem? Please describe.**\\n\\n<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->\\n\\n**Describe the solution you'd like**\\n\\n<!-- A clear and concise description of what you want to happen. -->\\n\\n**Describe alternatives you've considered**\\n\\n<!-- A clear and concise description of any alternative solutions or features you've considered. -->\\n\\n**Additional context**\\n\\n<!-- Add any other context or screenshots about the feature request here. -->\\n\",\n      \"createdAt\": \"2025-11-17T12:36:09Z\",\n      \"closedAt\": \"2025-12-08T13:17:30Z\",\n      \"state\": \"CLOSED\",\n      \"commentCount\": 0\n    }\n  ],\n  \"topPRs\": [\n    {\n      \"id\": \"PR_kwDOMT5cIs64E0uE\",\n      \"title\": \"Eliza Cloud Integration, add MCP + A2A service starter, integrate CLI and starter projects tight\",\n      \"author\": \"lalalune\",\n      \"number\": 6216,\n      \"body\": \"The goal of this PR is to tightly integrate the elizaos cloud plugin, which now can use cloud as a db and storage provider, and encourage users through the CLI to get up and running with elizaos cloud. CLI should auto log them in, provision API key and make sure project is set up.\\r\\n\\r\\nPlease thoroughly review and understand the create -> deploy -> publish and monetize flow, may still need some work\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-12-10T07:26:45Z\",\n      \"mergedAt\": null,\n      \"additions\": 9989,\n      \"deletions\": 101\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs630tVJ\",\n      \"title\": \"Shaw/chore/deslop\",\n      \"author\": \"lalalune\",\n      \"number\": 6213,\n      \"body\": \"This PR removes a lot of slop\\r\\n\\r\\n- Fixes any and unknown and cast types with real types\\r\\n- Removes try catch\\r\\n- Removes sloppy comments\\r\\n- Removes dead files and code\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-12-09T03:59:26Z\",\n      \"mergedAt\": \"2025-12-09T06:22:34Z\",\n      \"additions\": 9246,\n      \"deletions\": 7105\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs64kuni\",\n      \"title\": \"Main\",\n      \"author\": \"DevGruGold\",\n      \"number\": 6220,\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review and merge. -->\\r\\n\\r\\n# Risks\\r\\n\\r\\n<!--\\r\\nLow, medium, large. List what kind of risks and what could be affected.\\r\\n-->\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n<!--\\r\\nBug fixes (non-breaking change which fixes an issue)\\r\\nImprovements (misc. changes to existing features)\\r\\nFeatures (non-breaking change which adds functionality)\\r\\nUpdates (new versions of included code)\\r\\n-->\\r\\n\\r\\n<!-- 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. -->\\r\\n<!--\\r\\n## Why are we doing this? Any context or related work?\\r\\n-->\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n<!--\\r\\nMy changes do not require a change to the project documentation.\\r\\nMy changes require a change to the project documentation.\\r\\nIf documentation change is needed: I have updated the documentation accordingly.\\r\\n-->\\r\\n\\r\\n<!-- 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. -->\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n<!--\\r\\nNone: Automated tests are acceptable.\\r\\n-->\\r\\n\\r\\n<!--\\r\\n- As [anon/admin], go to [link]\\r\\n\u00a0 - [do action]\\r\\n\u00a0 - verify [result]\\r\\n-->\\r\\n\\r\\n<!-- If there is a UI change, please include before and after screenshots or videos. This will speed up PRs being merged. It is extra nice to annotate screenshots with arrows or boxes pointing out the differences. -->\\r\\n<!--\\r\\n## Screenshots\\r\\n### Before\\r\\n### After\\r\\n-->\\r\\n\\r\\n<!-- If there is anything about the deployment, please make a note. -->\\r\\n<!--\\r\\n# Deploy Notes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Copy and paste command line output. -->\\r\\n<!--\\r\\n## Database changes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Please specify deploy instructions if there is something more than the automated steps. -->\\r\\n<!--\\r\\n## Deployment instructions\\r\\n-->\\r\\n\\r\\n<!-- 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 -->\\r\\n<!--\\r\\n## Discord username\\r\\n\\r\\n-->\\r\\n\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-12-12T14:04:11Z\",\n      \"mergedAt\": null,\n      \"additions\": 6952,\n      \"deletions\": 840\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs620Si3\",\n      \"title\": \"feat(auth): implement JWT authentication and user management\",\n      \"author\": \"standujar\",\n      \"number\": 6200,\n      \"body\": \"## Relates to\\r\\n\\r\\n- Data isolation / multi-entity support\\r\\n- External JWT provider integration (Privy, Auth0, Clerk, Supabase, Google, Embbeded)\\r\\n\\r\\n## Risks\\r\\n\\r\\n**Low**\\r\\n\\r\\n- Requires `ENABLE_DATA_ISOLATION=true` to activate JWT auth mode\\r\\n\\r\\n## Background\\r\\n\\r\\n### What does this PR do?\\r\\n\\r\\nImplements a complete JWT authentication system for ElizaOS with support for multiple verification strategies:\\r\\n\\r\\n1. **JWT Verifier Factory** - Priority-based verifier selection:\\r\\n   - Ed25519 (highest priority) - For self-signed JWTs with Ed25519 keys\\r\\n   - JWKS (medium priority) - For external providers (Auth0, Clerk, Privy, Supabase, Google)\\r\\n   - Secret (lowest priority) - For simple HS256 symmetric key verification\\r\\n\\r\\n2. **Entity ID derivation from JWT `sub` claim**:\\r\\n   - `entityId = stringToUuid(payload.sub)`\\r\\n   - Compatible with ANY JWT provider since `sub` is a standard claim\\r\\n   - No custom claims needed in external JWTs\\r\\n\\r\\n3. **Dual authentication modes**:\\r\\n   - `ENABLE_DATA_ISOLATION=true` \u2192 JWT authentication required\\r\\n   - `ENABLE_DATA_ISOLATION=false` \u2192 X-Entity-Id header (legacy mode)\\r\\n\\r\\n4. **Internal service bypass** - Process-local UUID secret for service-to-service calls\\r\\n\\r\\n5. **Credentials-based auth endpoints** (`/api/auth/*`) - only in custom - JWT-SECRET mode:\\r\\n   - `POST /register` - User registration with bcrypt password hashing\\r\\n   - `POST /login` - User login with JWT generation\\r\\n   - `POST /refresh` - Token refresh\\r\\n   - `GET /me` - Current user info\\r\\n\\r\\n6. **Client UI default implementation using self mode (Secret)\\r\\n\\r\\n### What kind of change is this?\\r\\n\\r\\n**Features** (non-breaking change which adds functionality)\\r\\n\\r\\n## Architecture\\r\\n\\r\\n```\\r\\n\u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\\r\\n\u2502                    JWT Verification Flow                         \u2502\\r\\n\u251c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2524\\r\\n\u2502  Request with Bearer token                                       \u2502\\r\\n\u2502       \u2193                                                          \u2502\\r\\n\u2502  JWTVerifierFactory.create()                                     \u2502\\r\\n\u2502       \u2193                                                          \u2502\\r\\n\u2502  Priority: Ed25519 > JWKS > Secret > Disabled                   \u2502\\r\\n\u2502       \u2193                                                          \u2502\\r\\n\u2502  verifier.verify(token)                                          \u2502\\r\\n\u2502       \u2193                                                          \u2502\\r\\n\u2502  Extract payload.sub                                             \u2502\\r\\n\u2502       \u2193                                                          \u2502\\r\\n\u2502  entityId = stringToUuid(sub)  \u2190 Derived, NOT stored in JWT     \u2502\\r\\n\u2502       \u2193                                                          \u2502\\r\\n\u2502  req.entityId = entityId                                         \u2502\\r\\n\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\\r\\n```\\r\\n\\r\\n## Environment Variables\\r\\n\\r\\n| Variable | Description | Example |\\r\\n|----------|-------------|---------|\\r\\n| `ENABLE_DATA_ISOLATION` | Enable JWT auth mode | `true` |\\r\\n| `JWT_SECRET` (optional) | HS256 symmetric secret | `your-secret-key` |\\r\\n| `JWT_PUBLIC_KEY_ED25519` (optional) | Ed25519 public key (base64) | `MCowBQYDK2Vw...` |\\r\\n| `JWT_JWKS_URI` (optional) | JWKS endpoint URL | `https://auth0.com/.well-known/jwks.json` |\\r\\n| `JWT_ISSUER_WHITELIST` (optional) | Allowed issuers (comma-separated) | `https://auth0.com/,https://clerk.dev` |\\r\\n\\r\\n## Documentation changes needed?\\r\\n\\r\\nYes - Documentation should be added for:\\r\\n- Environment variable configuration\\r\\n- External provider setup (Auth0, Clerk, Privy examples)\\r\\n\\r\\n## Testing\\r\\n\\r\\n### Where should a reviewer start?\\r\\n\\r\\n1. `packages/server/src/services/jwt-verifiers/factory.ts` - Core factory logic\\r\\n2. `packages/server/src/middleware/jwtMiddleware.ts` - HTTP middleware\\r\\n3. `packages/server/src/socketio/index.ts` - SocketIO authentication\\r\\n\\r\\n### Detailed testing steps\\r\\n\\r\\n**Unit Tests:**\\r\\n```bash\\r\\ncd packages/server\\r\\nbun run test:unit\\r\\n```\\r\\n\\r\\n**Integration Tests:**\\r\\n```bash\\r\\ncd packages/server\\r\\nbun run test:integration\\r\\n```\\r\\n\\r\\n**Results:** 489 unit tests pass, 6 integration test files pass\\r\\n\\r\\n### Manual Testing\\r\\n\\r\\n1. **Test with JWT_SECRET (HS256):**\\r\\n```bash\\r\\nENABLE_DATA_ISOLATION=true JWT_SECRET=test-secret bun run dev\\r\\n```\\r\\n\\r\\n2. **Register a user:**\\r\\n```bash\\r\\ncurl -X POST http://localhost:3000/api/auth/register \\\\\\r\\n  -H \\\"Content-Type: application/json\\\" \\\\\\r\\n  -d '{\\\"email\\\":\\\"test@example.com\\\",\\\"username\\\":\\\"testuser\\\",\\\"password\\\":\\\"password123\\\"}'\\r\\n```\\r\\n\\r\\n3. **Use returned token:**\\r\\n```bash\\r\\ncurl http://localhost:3000/api/agents \\\\\\r\\n  -H \\\"Authorization: Bearer <token>\\\"\\r\\n```\\r\\n\\r\\n## External Provider Compatibility\\r\\n\\r\\nTested JWT formats:\\r\\n- **Auth0**: `sub: \\\"auth0|1234567890\\\"`\\r\\n- **Clerk**: `sub: \\\"user_2abcdefgh123456\\\"`\\r\\n- **Google**: `sub: \\\"1234567890\\\"` with `email`, `email_verified`\\r\\n- **Supabase**: `sub: \\\"uuid\\\"` with `role: \\\"authenticated\\\"`\\r\\n- **Privy**: `sub: \\\"did:privy:...\\\"`\\r\\n\\r\\nAll providers work because we only require the standard `sub` claim.\\r\\n\\r\\n## Next Idea Steps: Access Control Layer (ACL)\\r\\n\\r\\nThe next phase will add access control on agents and rooms: \\r\\n\\r\\nAgents:\\r\\n- Each user can create their own agents (ownerId = entityId)\\r\\n- Visibility: public or private\\r\\n- Private = only the owner can chat with it\\r\\n- Public = everyone can chat, but only the owner can modify/delete\\r\\n\\r\\nRooms:\\r\\n- Each room has an owner\\r\\nOnly the owner can:\\r\\n- Delete the room (DELETE /rooms/:id)\\r\\n- Clear message history (DELETE /rooms/:id/messages)\\r\\n- Change visibility\\r\\n\\r\\nThis will enable true multi-tenant mode where each user manages their resources in isolation.\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-12-03T11:55:47Z\",\n      \"mergedAt\": null,\n      \"additions\": 6072,\n      \"deletions\": 354\n    },\n    {\n      \"id\": \"PR_kwDOMT5cIs64fjY5\",\n      \"title\": \"Main\",\n      \"author\": \"DevGruGold\",\n      \"number\": 6219,\n      \"body\": \"<!-- Use this template by filling in information and copying and pasting relevant items out of the HTML comments. -->\\r\\n\\r\\n# Relates to\\r\\n\\r\\n<!-- LINK TO ISSUE OR TICKET -->\\r\\n\\r\\n<!-- This risks section must be filled out before the final review and merge. -->\\r\\n\\r\\n# Risks\\r\\n\\r\\n<!--\\r\\nLow, medium, large. List what kind of risks and what could be affected.\\r\\n-->\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n## What kind of change is this?\\r\\n\\r\\n<!--\\r\\nBug fixes (non-breaking change which fixes an issue)\\r\\nImprovements (misc. changes to existing features)\\r\\nFeatures (non-breaking change which adds functionality)\\r\\nUpdates (new versions of included code)\\r\\n-->\\r\\n\\r\\n<!-- 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. -->\\r\\n<!--\\r\\n## Why are we doing this? Any context or related work?\\r\\n-->\\r\\n\\r\\n# Documentation changes needed?\\r\\n\\r\\n<!--\\r\\nMy changes do not require a change to the project documentation.\\r\\nMy changes require a change to the project documentation.\\r\\nIf documentation change is needed: I have updated the documentation accordingly.\\r\\n-->\\r\\n\\r\\n<!-- 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. -->\\r\\n\\r\\n# Testing\\r\\n\\r\\n## Where should a reviewer start?\\r\\n\\r\\n## Detailed testing steps\\r\\n\\r\\n<!--\\r\\nNone: Automated tests are acceptable.\\r\\n-->\\r\\n\\r\\n<!--\\r\\n- As [anon/admin], go to [link]\\r\\n\u00a0 - [do action]\\r\\n\u00a0 - verify [result]\\r\\n-->\\r\\n\\r\\n<!-- If there is a UI change, please include before and after screenshots or videos. This will speed up PRs being merged. It is extra nice to annotate screenshots with arrows or boxes pointing out the differences. -->\\r\\n<!--\\r\\n## Screenshots\\r\\n### Before\\r\\n### After\\r\\n-->\\r\\n\\r\\n<!-- If there is anything about the deployment, please make a note. -->\\r\\n<!--\\r\\n# Deploy Notes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Copy and paste command line output. -->\\r\\n<!--\\r\\n## Database changes\\r\\n-->\\r\\n\\r\\n<!-- \u00a0Please specify deploy instructions if there is something more than the automated steps. -->\\r\\n<!--\\r\\n## Deployment instructions\\r\\n-->\\r\\n\\r\\n<!-- 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 -->\\r\\n<!--\\r\\n## Discord username\\r\\n\\r\\n-->\\r\\n\",\n      \"repository\": \"elizaos/eliza\",\n      \"createdAt\": \"2025-12-12T05:13:08Z\",\n      \"mergedAt\": null,\n      \"additions\": 5104,\n      \"deletions\": 662\n    }\n  ],\n  \"codeChanges\": {\n    \"additions\": 14134,\n    \"deletions\": 6079,\n    \"files\": 286,\n    \"commitCount\": 187\n  },\n  \"completedItems\": [\n    {\n      \"title\": \"fix: markdown spacing compact\",\n      \"prNumber\": 6159,\n      \"type\": \"bugfix\",\n      \"body\": \"# Relates to\\r\\n\\r\\nFixes excessive vertical spacing in AI-generated markdown responses in the ElizaOS client UI.\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low Risk**\\r\\n\\r\\n- Only CSS changes affecting markdown content rendering\\r\\n- Uses well-supported CSS features (Chrome \",\n      \"files\": [\n        \"packages/client/src/components/ai-elements/response.tsx\",\n        \"packages/client/src/index.css\"\n      ]\n    },\n    {\n      \"title\": \"refactor(server): optimization and reorganization\",\n      \"prNumber\": 6199,\n      \"type\": \"refactor\",\n      \"body\": \"# Risks\\r\\n\\r\\n**Low to Medium**\\r\\n\\r\\n- Socket.IO configuration changes may affect existing client connections (tested with multiple browsers)\\r\\n- Code reorganization changes import paths - all imports have been updated and verified\\r\\n\\r\\n# Backgroun\",\n      \"files\": [\n        \"bun.lock\",\n        \"packages/server/src/__tests__/builders/channel.builder.ts\",\n        \"packages/server/src/__tests__/builders/message.builder.ts\",\n        \"packages/server/src/__tests__/integration/agent-server-interaction.test.ts\",\n        \"packages/server/src/__tests__/integration/database-operations.test.ts\",\n        \"packages/server/src/__tests__/integration/message-bus-service.test.ts\",\n        \"packages/server/src/__tests__/unit/api/crud-uuid.test.ts\",\n        \"packages/server/src/__tests__/unit/api/jobs.test.ts\",\n        \"packages/server/src/__tests__/unit/features/socketio-router.test.ts\",\n        \"packages/server/src/__tests__/unit/services/message-bus-compatibility.test.ts\",\n        \"packages/server/src/__tests__/unit/utils/loader-uuid.test.ts\",\n        \"packages/server/src/__tests__/unit/utils/loader.test.ts\",\n        \"packages/server/src/api/index.ts\",\n        \"packages/server/src/api/messaging/channels.ts\",\n        \"packages/server/src/api/messaging/core.ts\",\n        \"packages/server/src/api/messaging/jobs.ts\",\n        \"packages/server/src/api/messaging/messageServers.ts\",\n        \"packages/server/src/api/messaging/sessions.ts\",\n        \"packages/server/src/api/shared/uploads/index.ts\",\n        \"packages/server/src/index.ts\",\n        \"packages/server/src/services/index.ts\",\n        \"packages/server/src/services/loader.ts\",\n        \"packages/server/src/services/message-bus.ts\",\n        \"packages/server/src/services/message.ts\",\n        \"packages/server/src/socketio/index.ts\",\n        \"packages/server/src/types/server.ts\",\n        \"packages/server/src/utils/config.ts\",\n        \"packages/server/src/utils/index.ts\",\n        \"packages/server/src/utils/media-transformer.ts\",\n        \"packages/server/src/utils/upload.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix(client): improve markdown content spacing\",\n      \"prNumber\": 6197,\n      \"type\": \"bugfix\",\n      \"body\": \"This PR includes two fixes for markdown content spacing in the client:\\n\\n1. Add missing heading and separator spacing to markdown-content\\n2. Reduce blockquote vertical spacing for more compact display\\n\\nThese changes improve the visual consis\",\n      \"files\": [\n        \"packages/client/src/index.css\"\n      ]\n    },\n    {\n      \"title\": \"feat: Unified API - serverless - nodejs\",\n      \"prNumber\": 6201,\n      \"type\": \"feature\",\n      \"body\": \"\",\n      \"files\": [\n        \"bun.lock\",\n        \"packages/core/src/__tests__/elizaos-sendmessage.test.ts\",\n        \"packages/core/src/__tests__/elizaos.test.ts\",\n        \"packages/core/src/elizaos.ts\",\n        \"packages/core/src/types/elizaos.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix(examples): respect user LOG_LEVEL in standalone-cli-chat\",\n      \"prNumber\": 6203,\n      \"type\": \"bugfix\",\n      \"body\": \"\",\n      \"files\": [\n        \"examples/standalone-cli-chat.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix(plugin-sql): migrate to messageService API and auto-create PGLite directories\",\n      \"prNumber\": 6202,\n      \"type\": \"bugfix\",\n      \"body\": \"## Summary\\n\\nThis PR modernizes the standalone example files and improves the SQL plugin's directory handling by:\\n1. Migrating examples from the deprecated `MESSAGE_RECEIVED` event system to the new `messageService.handleMessage()` API\\n2. Ad\",\n      \"files\": [\n        \"examples/standalone-cli-chat.ts\",\n        \"examples/standalone.ts\",\n        \"packages/plugin-sql/src/__tests__/unit/directory-creation.test.ts\",\n        \"packages/plugin-sql/src/index.node.ts\",\n        \"packages/plugin-sql/src/index.ts\"\n      ]\n    },\n    {\n      \"title\": \"feat: Add ElizaOS Cloud as Default AI Provider in CLI\",\n      \"prNumber\": 6208,\n      \"type\": \"feature\",\n      \"body\": \"## Add ElizaOS Cloud as Default AI Provider in CLI\\n\\n### Summary\\n- Add **ElizaOS Cloud** as the first/recommended option in `elizaos create` AI model selection\\n- Integrate browser-based login flow for seamless API key setup\\n- Fix env variabl\",\n      \"files\": [\n        \"bun.lock\",\n        \"packages/cli/src/commands/create/actions/setup.ts\",\n        \"packages/cli/src/commands/create/utils/selection.ts\",\n        \"packages/cli/src/commands/deploy/utils/api-client.ts\",\n        \"packages/cli/src/commands/login/README.md\",\n        \"packages/cli/src/commands/login/actions/login.ts\",\n        \"packages/cli/src/utils/get-config.ts\",\n        \"packages/cli/tests/commands/create.test.ts\",\n        \"packages/cli/tests/unit/utils/elizacloud-config.test.ts\",\n        \"packages/cli/tests/unit/utils/selection.test.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix(cli): correct startAgents API signature in e2e-tests\",\n      \"prNumber\": 6207,\n      \"type\": \"bugfix\",\n      \"body\": \"## Summary\\r\\n\\r\\n- Fixed `startAgents` API signature mismatch in CLI's e2e-tests.ts\\r\\n- Fixed unit test mock function name (`getElizaCharacter` \u2192 `getDefaultCharacter`)\\r\\n\\r\\n## Problem\\r\\n\\r\\nThe CLI's `elizaos test` command was failing with:\\r\\n```\\r\\nu\",\n      \"files\": [\n        \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n        \"packages/cli/tests/unit/commands/test/e2e-tests.test.ts\"\n      ]\n    },\n    {\n      \"title\": \"feat: bump deps, fix drizzle-kit across ecosystem\",\n      \"prNumber\": 6210,\n      \"type\": \"feature\",\n      \"body\": \"## \ud83d\udd04 Update All Dependencies to Latest Versions\\n\\n### Problem\\n\\nFound conflicting `drizzle-orm` versions across the monorepo causing compatibility issues:\\n\\n- `drizzle-orm@0.45.0` (root)\\n- `drizzle-orm@0.44.7` (from `@elizaos/plugin-sql`)\\n- `\",\n      \"files\": [\n        \".github/workflows/cli-tests.yml\",\n        \".github/workflows/client-cypress-tests.yml\",\n        \".github/workflows/jsdoc-automation.yml\",\n        \".github/workflows/release.yaml\",\n        \".github/workflows/tauri-ci.yml\",\n        \".github/workflows/update-news.yml\",\n        \"bun.lock\",\n        \"package.json\",\n        \"packages/api-client/package.json\",\n        \"packages/app/package.json\",\n        \"packages/cli/package.json\",\n        \"packages/cli/tests/commands/agent.test.ts\",\n        \"packages/cli/tests/commands/create.test.ts\",\n        \"packages/cli/tests/commands/dev.test.ts\",\n        \"packages/cli/tests/commands/env.test.ts\",\n        \"packages/cli/tests/commands/monorepo.test.ts\",\n        \"packages/cli/tests/commands/plugins.test.ts\",\n        \"packages/cli/tests/commands/publish.test.ts\",\n        \"packages/cli/tests/commands/start.test.ts\",\n        \"packages/cli/tests/commands/tee.test.ts\",\n        \"packages/cli/tests/commands/test.test.ts\",\n        \"packages/cli/tests/commands/update.test.ts\",\n        \"packages/cli/tests/unit/utils/elizacloud-config.test.ts\",\n        \"packages/client/package.json\",\n        \"packages/config/package.json\",\n        \"packages/core/package.json\",\n        \"packages/plugin-bootstrap/package.json\",\n        \"packages/plugin-dummy-services/package.json\",\n        \"packages/plugin-quick-starter/package.json\",\n        \"packages/plugin-sql/build.ts\",\n        \"packages/plugin-sql/package.json\",\n        \"packages/plugin-starter/package.json\",\n        \"packages/project-starter/package.json\",\n        \"packages/project-tee-starter/package.json\",\n        \"packages/server/package.json\",\n        \"packages/service-interfaces/package.json\",\n        \"packages/test-utils/package.json\"\n      ]\n    },\n    {\n      \"title\": \"feat: enhance streaming support in text generation\",\n      \"prNumber\": 6212,\n      \"type\": \"feature\",\n      \"body\": \"# Relates to\\r\\n\\r\\n- Streaming support for text generation models\\r\\n- CLI test runner improvements\\r\\n\\r\\n# Risks\\r\\n\\r\\n**Low**. Changes are additive and backward-compatible:\\r\\n- New streaming API is opt-in via `stream: true` parameter\\r\\n\\r\\n# Background\\r\",\n      \"files\": [\n        \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n        \"packages/cli/src/utils/test-runner.ts\",\n        \"packages/cli/tests/unit/commands/test/e2e-tests.test.ts\",\n        \"packages/client/src/components/ChatMessageListComponent.tsx\",\n        \"packages/client/src/components/chat.tsx\",\n        \"packages/client/src/hooks/use-query-hooks.ts\",\n        \"packages/client/src/hooks/use-socket-chat.ts\",\n        \"packages/client/src/lib/socketio-manager.ts\",\n        \"packages/core/src/__tests__/message-service.test.ts\",\n        \"packages/core/src/__tests__/runtime.test.ts\",\n        \"packages/core/src/__tests__/utils.test.ts\",\n        \"packages/core/src/elizaos.ts\",\n        \"packages/core/src/runtime.ts\",\n        \"packages/core/src/services/default-message-service.ts\",\n        \"packages/core/src/services/message-service.ts\",\n        \"packages/core/src/types/elizaos.ts\",\n        \"packages/core/src/types/model.ts\",\n        \"packages/core/src/types/primitives.ts\",\n        \"packages/core/src/types/runtime.ts\",\n        \"packages/core/src/utils.ts\",\n        \"packages/server/src/api/messaging/core.ts\",\n        \"packages/server/src/services/message.ts\",\n        \"packages/server/src/socketio/index.ts\",\n        \"packages/api-client/src/__tests__/services/sessions.test.ts\",\n        \"packages/api-client/src/services/sessions.ts\",\n        \"packages/api-client/src/types/sessions.ts\",\n        \"packages/core/src/__tests__/elizaos-handlemessage.test.ts\",\n        \"packages/core/src/__tests__/elizaos.test.ts\",\n        \"packages/core/src/__tests__/messaging-types.test.ts\",\n        \"packages/core/src/types/messaging.ts\",\n        \"packages/core/src/types/plugin.ts\",\n        \"packages/server/src/__tests__/integration/message-bus-service.test.ts\",\n        \"packages/server/src/__tests__/unit/api/channels-mode.test.ts\",\n        \"packages/server/src/__tests__/unit/api/response-handlers.test.ts\",\n        \"packages/server/src/__tests__/unit/api/sessions.test.ts\",\n        \"packages/server/src/__tests__/unit/services/message-stream-events.test.ts\",\n        \"packages/server/src/api/messaging/channels.ts\",\n        \"packages/server/src/api/messaging/sessions.ts\",\n        \"packages/server/src/api/shared/constants.ts\",\n        \"packages/server/src/api/shared/response-handlers.ts\",\n        \"packages/server/src/api/shared/validation.ts\",\n        \"packages/server/src/types/server.ts\",\n        \"packages/cli/src/commands/scenario/src/UserSimulator.ts\",\n        \"packages/core/src/__tests__/e2e/core-runtime.test.ts\",\n        \"packages/core/src/__tests__/integration/character-runtime.test.ts\",\n        \"packages/core/src/__tests__/integration/memory-runtime.test.ts\",\n        \"packages/core/src/__tests__/runtime-embedding.test.ts\",\n        \"packages/core/src/__tests__/runtime-streaming.test.ts\",\n        \"packages/core/src/__tests__/streaming-context.test.ts\",\n        \"packages/core/src/__tests__/test-helpers.ts\",\n        \"packages/core/src/index.browser.ts\",\n        \"packages/core/src/index.node.ts\",\n        \"packages/core/src/index.ts\",\n        \"packages/core/src/streaming-context.browser.ts\",\n        \"packages/core/src/streaming-context.node.ts\",\n        \"packages/core/src/streaming-context.ts\",\n        \"packages/plugin-bootstrap/src/actions/reply.ts\",\n        \"packages/core/src/__tests__/utils/streaming.test.ts\",\n        \"packages/core/src/types/index.ts\",\n        \"packages/core/src/types/streaming.ts\",\n        \"packages/core/src/utils/streaming.ts\",\n        \"packages/plugin-bootstrap/src/__tests__/actions.test.ts\"\n      ]\n    },\n    {\n      \"title\": \"Shaw/chore/deslop\",\n      \"prNumber\": 6213,\n      \"type\": \"other\",\n      \"body\": \"This PR removes a lot of slop\\r\\n\\r\\n- Fixes any and unknown and cast types with real types\\r\\n- Removes try catch\\r\\n- Removes sloppy comments\\r\\n- Removes dead files and code\",\n      \"files\": [\n        \"build-utils.ts\",\n        \"bun.lock\",\n        \"packages/api-client/src/__tests__/integration/no-content-fix.test.ts\",\n        \"packages/api-client/src/__tests__/services/agents.test.ts\",\n        \"packages/api-client/src/__tests__/services/audio.test.ts\",\n        \"packages/api-client/src/__tests__/services/jobs.test.ts\",\n        \"packages/api-client/src/__tests__/services/media.test.ts\",\n        \"packages/api-client/src/__tests__/services/memory.test.ts\",\n        \"packages/api-client/src/__tests__/services/messaging.test.ts\",\n        \"packages/api-client/src/__tests__/services/server.test.ts\",\n        \"packages/api-client/src/__tests__/services/system.test.ts\",\n        \"packages/api-client/src/lib/base-client.ts\",\n        \"packages/api-client/src/services/agents.ts\",\n        \"packages/api-client/src/services/audio.ts\",\n        \"packages/api-client/src/services/jobs.ts\",\n        \"packages/api-client/src/services/media.ts\",\n        \"packages/api-client/src/services/memory.ts\",\n        \"packages/api-client/src/services/messaging.ts\",\n        \"packages/api-client/src/services/sessions.ts\",\n        \"packages/api-client/src/services/system.ts\",\n        \"packages/api-client/src/types/agents.ts\",\n        \"packages/api-client/src/types/jobs.ts\",\n        \"packages/api-client/src/types/media.ts\",\n        \"packages/api-client/src/types/memory.ts\",\n        \"packages/api-client/src/types/server.ts\",\n        \"packages/api-client/src/types/system.ts\",\n        \"packages/app/README.md\",\n        \"packages/app/eslint.config.js\",\n        \"packages/app/index.html\",\n        \"packages/app/package.json\",\n        \"packages/app/src-tauri/Cargo.toml\",\n        \"packages/app/src-tauri/src/lib.rs\",\n        \"packages/app/src/__tests__/main.test.ts\",\n        \"packages/app/src/main.tsx\",\n        \"packages/app/src/types/bun-test.d.ts\",\n        \"packages/app/vite.config.ts\",\n        \"packages/cli/src/commands/agent/actions/crud.ts\",\n        \"packages/cli/src/commands/agent/actions/lifecycle.ts\",\n        \"packages/cli/src/commands/create/actions/creators.ts\",\n        \"packages/cli/src/commands/create/index.ts\",\n        \"packages/cli/src/commands/create/utils/validation.ts\",\n        \"packages/cli/src/commands/deploy/actions/deploy-ecs.ts\",\n        \"packages/cli/src/commands/deploy/types.ts\",\n        \"packages/cli/src/commands/dev/actions/dev-server.ts\",\n        \"packages/cli/src/commands/publish/types.ts\",\n        \"packages/cli/src/commands/report/generate.ts\",\n        \"packages/cli/src/commands/report/src/analysis-engine.ts\",\n        \"packages/cli/src/commands/scenario/docs/README.md\",\n        \"packages/cli/src/commands/scenario/docs/file-format-spec.md\",\n        \"packages/cli/src/commands/scenario/docs/matrix-testing.md\"\n      ]\n    },\n    {\n      \"title\": \"fix: resolve TypeScript build errors in every packages - first step\",\n      \"prNumber\": 6218,\n      \"type\": \"bugfix\",\n      \"body\": \"\",\n      \"files\": [\n        \"packages/api-client/src/lib/base-client.ts\",\n        \"packages/api-client/src/services/audio.ts\",\n        \"packages/api-client/src/types/agents.ts\",\n        \"packages/client/src/components/agent-action-viewer.tsx\",\n        \"packages/client/src/components/chat.tsx\",\n        \"packages/client/src/config/agent-templates.ts\",\n        \"packages/client/src/hooks/__tests__/use-agent-update.test.tsx\",\n        \"packages/client/src/hooks/use-character-convert.ts\",\n        \"packages/client/src/hooks/use-partial-update.ts\",\n        \"packages/client/src/hooks/use-query-hooks.ts\",\n        \"packages/client/src/hooks/use-socket-chat.ts\",\n        \"packages/client/src/lib/api-type-mappers.ts\",\n        \"packages/client/src/lib/socketio-manager.ts\",\n        \"packages/core/src/entities.ts\",\n        \"packages/core/src/logger.ts\",\n        \"packages/core/src/runtime.ts\",\n        \"packages/core/src/types/events.ts\",\n        \"packages/core/src/types/index.ts\",\n        \"packages/core/src/types/plugin.ts\",\n        \"packages/core/src/types/runtime.ts\",\n        \"packages/core/src/types/state.ts\",\n        \"packages/core/src/utils.ts\",\n        \"packages/plugin-bootstrap/src/actions/choice.ts\",\n        \"packages/plugin-bootstrap/src/actions/followRoom.ts\",\n        \"packages/plugin-bootstrap/src/actions/ignore.ts\",\n        \"packages/plugin-bootstrap/src/actions/imageGeneration.ts\",\n        \"packages/plugin-bootstrap/src/actions/muteRoom.ts\",\n        \"packages/plugin-bootstrap/src/actions/reply.ts\",\n        \"packages/plugin-bootstrap/src/actions/roles.ts\",\n        \"packages/plugin-bootstrap/src/actions/sendMessage.ts\",\n        \"packages/plugin-bootstrap/src/actions/unfollowRoom.ts\",\n        \"packages/plugin-bootstrap/src/actions/unmuteRoom.ts\",\n        \"packages/plugin-bootstrap/src/actions/updateEntity.ts\",\n        \"packages/plugin-bootstrap/src/evaluators/reflection.ts\",\n        \"packages/plugin-bootstrap/src/index.ts\",\n        \"packages/plugin-bootstrap/src/providers/actionState.ts\",\n        \"packages/plugin-dummy-services/src/browser/service.ts\",\n        \"packages/plugin-dummy-services/src/e2e/test-utils.ts\",\n        \"packages/plugin-sql/src/base.ts\",\n        \"packages/plugin-sql/src/index.node.ts\",\n        \"packages/plugin-sql/src/index.ts\",\n        \"packages/plugin-sql/src/migrations.ts\",\n        \"packages/plugin-sql/src/pg/adapter.ts\",\n        \"packages/plugin-sql/src/rls.ts\",\n        \"packages/plugin-sql/src/runtime-migrator/runtime-migrator.ts\",\n        \"packages/plugin-sql/src/runtime-migrator/storage/journal-storage.ts\",\n        \"packages/plugin-sql/src/runtime-migrator/storage/migration-tracker.ts\",\n        \"packages/plugin-sql/src/types.ts\",\n        \"packages/server/src/api/agents/runs.ts\",\n        \"packages/server/src/api/audio/conversation.ts\",\n        \"packages/cli/src/commands/scenario/src/EvaluationEngine.ts\",\n        \"packages/cli/src/commands/scenario/src/LocalEnvironmentProvider.ts\",\n        \"packages/cli/src/commands/scenario/src/TrajectoryReconstructor.ts\",\n        \"packages/cli/src/commands/scenario/src/UserSimulator.ts\",\n        \"packages/cli/src/commands/scenario/src/matrix-orchestrator.ts\",\n        \"packages/cli/src/commands/scenario/src/matrix-runner.ts\",\n        \"packages/cli/src/commands/scenario/src/matrix-schema.ts\",\n        \"packages/cli/src/commands/scenario/src/parameter-override.ts\",\n        \"packages/cli/src/commands/scenario/src/run-isolation.ts\",\n        \"packages/cli/src/commands/scenario/src/runtime-factory.ts\",\n        \"packages/cli/src/commands/test/actions/e2e-tests.ts\",\n        \"packages/cli/src/utils/spinner-utils.ts\",\n        \"packages/core/src/__tests__/settings.test.ts\",\n        \"packages/core/src/__tests__/utils.test.ts\",\n        \"packages/core/src/elizaos.ts\",\n        \"packages/core/src/schemas/character.ts\",\n        \"packages/core/src/settings.ts\",\n        \"packages/plugin-bootstrap/src/__tests__/logic.test.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix: encryption for character secrets in correct order\",\n      \"prNumber\": 6217,\n      \"type\": \"bugfix\",\n      \"body\": \"\",\n      \"files\": [\n        \"packages/core/src/__tests__/elizaos.test.ts\",\n        \"packages/core/src/elizaos.ts\",\n        \"packages/server/src/api/agents/crud.ts\",\n        \"packages/server/src/index.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix(plugin-sql): optimize pre-1.6.5 migration, RLS handling and SQL organisation\",\n      \"prNumber\": 6215,\n      \"type\": \"bugfix\",\n      \"body\": \"# Risks\\r\\n\\r\\n**Low** - All changes are backwards compatible and idempotent. Comprehensive test coverage added. Nothing is destructive\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- Adds smooth migration from pre-1.6.5 (camelCase) to 1.6.5+ \",\n      \"files\": [\n        \".github/workflows/plugin-sql-tests.yaml\",\n        \"examples/test-addagents-auto.ts\",\n        \"packages/plugin-sql/docker-compose.test.yml\",\n        \"packages/plugin-sql/package.json\",\n        \"packages/plugin-sql/scripts/init-test-db.sql\",\n        \"packages/plugin-sql/scripts/run-integration-tests.sh\",\n        \"packages/plugin-sql/src/__tests__/fixtures/test-plugin-schema.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/pglite-e2e.test.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/postgres/pg-adapter-integration.test.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/postgres/pglite-adapter.test.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/postgres/postgres-init.test.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/postgres/rls-entity.test.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/postgres/rls-logs.test.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/postgres/rls-message-server-agents.test.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/postgres/rls-server.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/dynamic-migration.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/e2e/docker-compose.yml\",\n        \"packages/plugin-sql/src/__tests__/migration/e2e/run-upgrade-test.sh\",\n        \"packages/plugin-sql/src/__tests__/migration/migration-before-1.6.5.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/production-scenario.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/runtime-migrator.test.ts\",\n        \"packages/plugin-sql/src/__tests__/unit/directory-creation.test.ts\",\n        \"packages/plugin-sql/src/__tests__/unit/index.test.ts\",\n        \"packages/plugin-sql/src/__tests__/unit/pg/adapter.test.ts\",\n        \"packages/plugin-sql/src/__tests__/unit/pglite/adapter.test.ts\",\n        \"packages/plugin-sql/src/base.ts\",\n        \"packages/plugin-sql/src/migrations.ts\",\n        \"packages/plugin-sql/src/pg/manager.ts\",\n        \"packages/plugin-sql/src/rls.ts\",\n        \"packages/plugin-sql/src/runtime-migrator/runtime-migrator.ts\",\n        \"packages/plugin-sql/src/schema/component.ts\",\n        \"packages/plugin-sql/src/schema/log.ts\",\n        \"packages/plugin-sql/src/schema/memory.ts\",\n        \"packages/plugin-sql/src/schema/participant.ts\",\n        \"packages/plugin-sql/src/schema/relationship.ts\",\n        \"packages/plugin-sql/src/schema/room.ts\",\n        \"packages/plugin-sql/src/schema/tasks.ts\",\n        \"packages/plugin-sql/src/schema/world.ts\",\n        \"packages/core/src/__tests__/logger-browser-node.test.ts\",\n        \"packages/plugin-sql/src/__tests__/integration/rls-entity.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/actual-runtime-scenario.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/initialization-with-plugin.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/runtime-simulation.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/schema-evolution-tests/06-index-evolution.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/schema-evolution-tests/07-foreign-key-evolution.test.ts\",\n        \"packages/plugin-sql/src/__tests__/migration/transaction-and-concurrency.test.ts\",\n        \"packages/plugin-sql/src/__tests__/test-helpers.ts\",\n        \"packages/plugin-sql/src/pglite/manager.ts\",\n        \"packages/plugin-sql/src/runtime-migrator/storage/migration-tracker.ts\",\n        \"packages/server/src/__tests__/fixtures/database.fixture.ts\"\n      ]\n    },\n    {\n      \"title\": \"fix: bootstrap action/provide format change fix + initPromise fix\",\n      \"prNumber\": 6261,\n      \"type\": \"bugfix\",\n      \"body\": \"# Risks\\r\\n\\r\\nLow, just fixes\\r\\n\\r\\n# Background\\r\\n\\r\\n## What does this PR do?\\r\\n\\r\\n- exposes initPromise so plugins can actually use it (duplicates some of #5718 but smaller and simpler)\\r\\n- fixes message format (we dropped serverId in favor of messa\",\n      \"files\": [\n        \"packages/core/src/types/runtime.ts\",\n        \"packages/plugin-bootstrap/src/__tests__/test-utils.ts\",\n        \"packages/plugin-bootstrap/src/actions/settings.ts\",\n        \"packages/plugin-bootstrap/src/providers/roles.ts\",\n        \"packages/plugin-bootstrap/src/providers/settings.ts\",\n        \"packages/plugin-quick-starter/src/__tests__/test-utils.ts\",\n        \"packages/plugin-starter/src/__tests__/test-utils.ts\",\n        \"packages/project-starter/src/__tests__/utils/core-test-utils.ts\",\n        \"packages/project-tee-starter/src/__tests__/utils/core-test-utils.ts\",\n        \"packages/test-utils/src/mocks/runtime.ts\",\n        \"packages/plugin-bootstrap/src/__tests__/providers.test.ts\"\n      ]\n    }\n  ],\n  \"topContributors\": [\n    {\n      \"username\": \"standujar\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16385918?u=718bdcd1585be8447bdfffb8c11ce249baa7532d&v=4\",\n      \"totalScore\": 540.4386888428947,\n      \"prScore\": 515.2826888428948,\n      \"issueScore\": 0,\n      \"reviewScore\": 23,\n      \"commentScore\": 2.1559999999999997,\n      \"summary\": \"standujar: This month, standujar made substantial contributions across the `elizaos` ecosystem, focusing on core system stability, refactoring, and introducing new capabilities. They implemented a new Unified API for serverless Node.js environments (elizaos/eliza#6201) and delivered several complex fixes, most notably optimizing the pre-1.6.5 migration and RLS handling in the SQL plugin (elizaos/eliza#6215), which involved over 28k lines of changes. In addition to merging seven pull requests, they have eight open PRs that introduce significant new features like JWT authentication and widespread streaming support. Their work was distributed across bug fixes, feature development, and refactoring, with a strong emphasis on code and test files.\"\n    },\n    {\n      \"username\": \"madjin\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/32600939?u=cdcf89f44c7a50906c7a80d889efa85023af2049&v=4\",\n      \"totalScore\": 323.1444101641285,\n      \"prScore\": 307.8684101641285,\n      \"issueScore\": 14.399999999999999,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.8759999999999999,\n      \"summary\": \"madjin: Focused on enhancing core functionality and maintaining project dependencies this month, merging three pull requests in the `elizaos/elizaos.github.io` repository. They implemented and fixed a new RSS feed feature (#172, #175) and also managed a substantial dependency update by upgrading the AI SDKs in a large PR (#170) with over 3300 new lines. Their work was a mix of bug fixes, feature implementation, and significant maintenance, touching both code and configuration files.\"\n    },\n    {\n      \"username\": \"wtfsayo\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/82053242?u=98209a1f10456f42d4d2fa71db4d5bf4a672cbc3&v=4\",\n      \"totalScore\": 135.9853756199966,\n      \"prScore\": 135.38537561999658,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.6000000000000001,\n      \"summary\": \"wtfsayo: Focused on client-side fixes and plugin migrations this month, merging two pull requests in the elizaos/eliza repository. They improved the user experience by fixing markdown content spacing (#6197) and migrated the SQL plugin to the new messageService API (#6202). Additionally, they have begun work on a new core feature for parallel action execution (#6209), with their overall contributions reflecting a primary focus on bug fixes and refactoring.\"\n    },\n    {\n      \"username\": \"ChristopherTrimboli\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/27584221?u=0d816ce1dcdea8f925aba18bb710153d4a87a719&v=4\",\n      \"totalScore\": 130.67356870848266,\n      \"prScore\": 111.17356870848266,\n      \"issueScore\": 0,\n      \"reviewScore\": 19.5,\n      \"commentScore\": 0,\n      \"summary\": \"ChristopherTrimboli: Focused on core feature development and dependency management, introducing ElizaOS Cloud as the default AI provider in the CLI (elizaos/eliza#6208) and executing a significant dependency update across the ecosystem (elizaos/eliza#6210). In addition to merging these two PRs, he supported the team by providing 4 code reviews. His work primarily involved modifications to configuration and test files, reflecting a focus on system health and testing alongside feature work.\"\n    },\n    {\n      \"username\": \"odilitime\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/16395496?u=c9bac48e632aae594a0d85aaf9e9c9c69b674d8b&v=4\",\n      \"totalScore\": 103.6914338220675,\n      \"prScore\": 103.49143382206749,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"odilitime: Undertook a substantial amount of work this month, reflected in 25 commits across 25 files (+2146/-592 lines). While this work has not yet been merged via a pull request, their coding activity shows a focus on bugfixes and refactoring. They also contributed by creating an issue in elizaos-plugins/plugin-mysql (#1).\"\n    },\n    {\n      \"username\": \"lalalune\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/18633264?u=e2e906c3712c2506ebfa98df01c2cfdc50050b30&v=4\",\n      \"totalScore\": 88.7855477931522,\n      \"prScore\": 84.7855477931522,\n      \"issueScore\": 4,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"lalalune: Made a substantial contribution this month by merging a large-scale chore/refactor in the elizaos/eliza repository (PR #6213), which involved over 16,000 lines of code changes. They also began work on a major new feature with the \\\"Eliza Cloud Integration\\\" pull request (#6216) and identified a crash condition that was subsequently resolved (elizaos/eliza#6204). Their activity shows a primary focus on a mix of bugfixes, feature work, and refactoring across the codebase.\"\n    },\n    {\n      \"username\": \"borisudovicic\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/31806472?u=8935f4d43fd7e4eb9bf5ff92d54d4d2f8ac8a786&v=4\",\n      \"totalScore\": 84,\n      \"prScore\": 0,\n      \"issueScore\": 84,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"borisudovicic: Focused entirely on product definition and quality assurance for the elizaos/eliza repository this month. They created 41 issues, identifying a wide range of bugs, user experience enhancements, and new feature proposals. This work included documenting critical fixes like the container deployment bug (#6187) and proposing significant UX changes such as redesigning the dashboard (#6222) and consolidating navigation (#6173). All activity was concentrated on identifying and scoping improvements for the elizaos/eliza application.\"\n    },\n    {\n      \"username\": \"DevGruGold\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/181147699?u=4258e430ad766ca1d11778ab9e7d91ecfa0e110c&v=4\",\n      \"totalScore\": 80.8515477931522,\n      \"prScore\": 80.8515477931522,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"DevGruGold: This month, DevGruGold initiated new work in the elizaos/eliza repository, opening two pull requests (#6220, #6219). While no contributions were merged, these open PRs represent a substantial effort, containing over 1900 lines of code changes across 13 commits. This work, a mix of bug fixes and other tasks, was primarily focused on modifying configuration, documentation, and test files.\"\n    },\n    {\n      \"username\": \"0xbbjoker\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/54844437?u=90fe1762420de6ad493a1c1582f1f70c0d87d8e2&v=4\",\n      \"totalScore\": 70.81247180559944,\n      \"prScore\": 33.31247180559945,\n      \"issueScore\": 2,\n      \"reviewScore\": 35.5,\n      \"commentScore\": 0,\n      \"summary\": \"0xbbjoker: This month, 0xbbjoker's work was primarily focused on bug fixes, contributing a significant volume of code changes across 68 files (+3655/-1134 lines). They merged one feature enhancement to the MCP provider (elizaos-plugins/plugin-mcp#19) and proactively opened an issue to improve the agent creator's file handling (elizaos/eliza#6245). In addition to their direct code contributions, they were an active collaborator, providing 6 code reviews for their peers.\"\n    },\n    {\n      \"username\": \"AntoineVergne\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/151149734?v=4\",\n      \"totalScore\": 33.983573590279974,\n      \"prScore\": 29.28357359027997,\n      \"issueScore\": 0,\n      \"reviewScore\": 4.5,\n      \"commentScore\": 0.2,\n      \"summary\": \"AntoineVergne: This month, AntoineVergne's work focused on expanding the plugin ecosystem by adding the new 'plugin-farcaster-local-hub' to the registry (elizaos-plugins/registry#243). This feature contribution consisted of a single-line update to a configuration file. They also provided one comment on a pull request.\"\n    },\n    {\n      \"username\": \"todoencadena\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/198127898?u=4c012fe538dffffc28d03890eda7d63746ae1ff2&v=4\",\n      \"totalScore\": 24.27972435596375,\n      \"prScore\": 24.27972435596375,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"todoencadena: Activity this month was focused on bot integration, opening a pull request to fix the Telegram bot for Railway (elizaos/eliza#6214). This work involved a single commit with minor changes to a configuration file.\"\n    },\n    {\n      \"username\": \"Tonyflam\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/150600391?u=0c905a5f627ff99389fc79e9978f1dc47546456e&v=4\",\n      \"totalScore\": 22.218573590279973,\n      \"prScore\": 22.218573590279973,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"Tonyflam: This month, their contribution focused on expanding the plugin ecosystem by adding the new `@tonyflam/plugin-openchat` plugin to the registry via PR elizaos-plugins/registry#242. This work consisted of a minor update to a configuration file.\"\n    },\n    {\n      \"username\": \"nguyennk92\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/30664183?u=d6e579cd25d50bc8e9ec4928d95909d759b841db&v=4\",\n      \"totalScore\": 8.902606672028108,\n      \"prScore\": 8.902606672028108,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": null\n    },\n    {\n      \"username\": \"github-advanced-security\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/in/57789?v=4\",\n      \"totalScore\": 4.5,\n      \"prScore\": 0,\n      \"issueScore\": 0,\n      \"reviewScore\": 4.5,\n      \"commentScore\": 0,\n      \"summary\": \"github-advanced-security: No activity this month.\"\n    },\n    {\n      \"username\": \"linear\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/in/20150?v=4\",\n      \"totalScore\": 4,\n      \"prScore\": 0,\n      \"issueScore\": 4,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"linear: Focused on server reliability by identifying and documenting an issue related to concurrent connection timeouts in elizaos/eliza (#6198).\"\n    },\n    {\n      \"username\": \"pereslavlland\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/247946180?v=4\",\n      \"totalScore\": 2.2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": \"pereslavlland: This month, pereslavlland's activity was focused on bug reporting within the elizaos/eliza repository. They identified and opened issue #6211 to document a problem with snapshot eligibility and Tangem wallet connections, and also contributed one comment to an issue.\"\n    },\n    {\n      \"username\": \"tdnupe3\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/25161668?u=94680b6bcbcfce954c7a9dd09d667a3919953041&v=4\",\n      \"totalScore\": 2,\n      \"prScore\": 0,\n      \"issueScore\": 2,\n      \"reviewScore\": 0,\n      \"commentScore\": 0,\n      \"summary\": \"tdnupe3: This month, tdnupe3's efforts were directed towards planning new payment functionalities. They initiated this work by creating issue elizaos/eliza#6244, which proposes an implementation guide for integrating Circle and Coinbase APIs for AI agent payments.\"\n    },\n    {\n      \"username\": \"otaku-x402\",\n      \"avatarUrl\": \"https://avatars.githubusercontent.com/u/242004857?u=1325b26d380eec4a0b8d84e8e249c523eebd28dc&v=4\",\n      \"totalScore\": 0.2,\n      \"prScore\": 0,\n      \"issueScore\": 0,\n      \"reviewScore\": 0,\n      \"commentScore\": 0.2,\n      \"summary\": null\n    }\n  ],\n  \"newPRs\": 23,\n  \"mergedPRs\": 15,\n  \"newIssues\": 45,\n  \"closedIssues\": 53,\n  \"activeContributors\": 18\n}\n---\n[\"actions-user_week_2025-12-14\", \"actions-user\", \"week\", \"2025-12-14\", \"actions-user: No activity this week.\", \"2025-12-17T05:24:26.674Z\"]\n[\"borisudovicic_week_2025-12-14\", \"borisudovicic\", \"week\", \"2025-12-14\", \"borisudovicic: Focused on product definition and planning for the `elizaos/eliza` application, creating 24 issues to scope out a significant user experience overhaul. These issues detail a wide range of improvements, from terminology changes (elizaos/eliza#6240) and component redesigns to a full dashboard overhaul (elizaos/eliza#6222) and new guided onboarding (elizaos/eliza#6221).\", \"2025-12-17T05:24:29.406Z\"]\n[\"0xbbjoker_week_2025-12-14\", \"0xbbjoker\", \"week\", \"2025-12-14\", \"0xbbjoker: This week, 0xbbjoker focused on extensive bugfix work, committing substantial changes (+3636/-1121 lines) across 57 files. In addition to this work, they supported the team by providing 3 code reviews and proposed a feature improvement for the agent creator in issue elizaos/eliza#6245.\", \"2025-12-17T05:24:31.055Z\"]\n[\"AntoineVergne_week_2025-12-14\", \"AntoineVergne\", \"week\", \"2025-12-14\", \"AntoineVergne: This week's focus was on expanding the plugin ecosystem by adding the new `plugin-farcaster-local-hub` to the registry in PR elizaos-plugins/registry#243. In addition to this feature work, they also provided one review comment. This activity centered on modifying configuration files to enable new functionality.\", \"2025-12-17T05:24:34.012Z\"]\n[\"madjin_week_2025-12-14\", \"madjin\", \"week\", \"2025-12-14\", \"madjin: Focused on enhancing content delivery for the `elizaos/elizaos.github.io` project by implementing a new RSS feed feature. They merged two significant PRs to add the feed endpoint (#172) and then fix its URL configuration (#175), with code changes primarily split between feature work and bug fixes. Madjin also planned for future work by creating several issues, including a blocker for a Next.js upgrade (#176) and a feature request for fuzzy search (#174).\", \"2025-12-17T05:24:35.399Z\"]\n[\"lalalune_week_2025-12-14\", \"lalalune\", \"week\", \"2025-12-14\", \"lalalune: Pushed a significant volume of code changes across 109 commits this week, modifying 17,405 files (+1,780,025/-1,083,404 lines). This activity, which did not involve any pull requests, was primarily focused on general updates, bug fixes, and refactoring.\", \"2025-12-17T05:24:35.481Z\"]\n[\"wtfsayo_week_2025-12-14\", \"wtfsayo\", \"week\", \"2025-12-14\", \"wtfsayo: No activity this week.\", \"2025-12-17T05:24:40.521Z\"]\n[\"standujar_week_2025-12-14\", \"standujar\", \"week\", \"2025-12-14\", \"standujar: Focused on a significant refactoring effort to unify the messaging API, opening pull requests in the Discord (#32) and Telegram (#22) plugins. This in-progress work was substantial, modifying 328 files with over 12k lines of new code. Their contributions this week were primarily centered on refactoring and feature development.\", \"2025-12-17T05:24:42.431Z\"]\n[\"tdnupe3_week_2025-12-14\", \"tdnupe3\", \"week\", \"2025-12-14\", \"tdnupe3 initiated planning for a new payment feature by creating an issue in elizaos/eliza (#6244) that outlines an implementation guide for integrating Circle and Coinbase APIs.\", \"2025-12-17T05:24:45.101Z\"]\n[\"lalalune_day_2025-12-14\", \"lalalune\", \"day\", \"2025-12-14\", \"lalalune: No activity today.\", \"2025-12-17T05:25:17.053Z\"]\n[\"0xbbjoker_day_2025-12-14\", \"0xbbjoker\", \"day\", \"2025-12-14\", \"0xbbjoker: No activity today.\", \"2025-12-17T05:25:17.116Z\"]\n[\"AntoineVergne_day_2025-12-15\", \"AntoineVergne\", \"day\", \"2025-12-15\", \"AntoineVergne: Focused on feature work, adding a new plugin to the registry by merging PR elizaos-plugins/registry#243, which involved modifying a configuration file.\", \"2025-12-17T05:25:17.354Z\"]\n[\"0xbbjoker_day_2025-12-15\", \"0xbbjoker\", \"day\", \"2025-12-15\", \"0xbbjoker: Today, 0xbbjoker focused on bugfix work, modifying 57 files with 3 commits, resulting in a net change of +2515 lines of code across various file types.\", \"2025-12-17T05:25:17.404Z\"]\n[\"AntoineVergne_day_2025-12-16\", \"AntoineVergne\", \"day\", \"2025-12-16\", \"AntoineVergne: No activity today.\", \"2025-12-17T05:25:17.424Z\"]\n[\"lalalune_day_2025-12-15\", \"lalalune\", \"day\", \"2025-12-15\", \"lalalune: Focused on a large-scale effort, modifying 7886 files with a net addition of over 228k lines across 31 commits, primarily centered on \\\"other work\\\" and refactoring.\", \"2025-12-17T05:25:17.456Z\"]\n[\"borisudovicic_day_2025-12-15\", \"borisudovicic\", \"day\", \"2025-12-15\", \"borisudovicic: Focused on identifying and documenting a wide range of potential user experience and UI improvements, creating 23 issues in elizaos/eliza, including suggestions for renaming sections and buttons, improving visual feedback, and redesigning core application flows.\", \"2025-12-17T05:25:17.617Z\"]\n[\"standujar_day_2025-12-15\", \"standujar\", \"day\", \"2025-12-15\", \"standujar: Focused on significant refactoring efforts, opening two substantial PRs, elizaos-plugins/plugin-discord#32 and elizaos-plugins/plugin-telegram#22, which involved modifying 295 files with a net addition of over 7,800 lines of code, primarily centered on refactoring and bug fixes.\", \"2025-12-17T05:25:17.657Z\"]\n[\"actions-user_day_2025-12-16\", \"actions-user\", \"day\", \"2025-12-16\", \"actions-user: No activity today.\", \"2025-12-17T05:25:17.760Z\"]\n[\"0xbbjoker_day_2025-12-16\", \"0xbbjoker\", \"day\", \"2025-12-16\", \"0xbbjoker: Today, 0xbbjoker initiated a new feature by creating issue elizaos/eliza#6245, \\\"Pre-upload files in agent creator for rag,\\\" and provided two reviews, including one change request, indicating engagement with ongoing development.\", \"2025-12-17T05:25:17.948Z\"]\n[\"lalalune_day_2025-12-16\", \"lalalune\", \"day\", \"2025-12-16\", \"lalalune: Focused on significant code changes, modifying 4353 files with a net addition of over 52,000 lines across 39 commits, primarily in \\\"other work\\\" and refactoring efforts.\", \"2025-12-17T05:25:18.010Z\"]\n[\"tdnupe3_day_2025-12-15\", \"tdnupe3\", \"day\", \"2025-12-15\", \"tdnupe3: Initiated a new feature development by creating an issue for \\\"AI Agent Payment Implementation Guide - Circle + Coinbase APIs\\\" (elizaos/eliza#6244), indicating a focus on integrating payment solutions within the AI agent platform.\", \"2025-12-17T05:25:18.087Z\"]\n[\"standujar_day_2025-12-16\", \"standujar\", \"day\", \"2025-12-16\", \"standujar: Focused on feature work, modifying 33 files with 8 commits (+1135/-579 lines), indicating active development across various file types.\", \"2025-12-17T05:25:18.180Z\"]\n[\"borisudovicic_day_2025-12-16\", \"borisudovicic\", \"day\", \"2025-12-16\", \"borisudovicic: Focused on enhancing user experience and functionality within elizaos/eliza by creating issues to implement toggle selection for plugins (#6236), improve plugin selection visual feedback (#6235), and introduce a \\\"Web Search\\\" feature (#6246).\", \"2025-12-17T05:25:18.303Z\"]\n[\"wtfsayo_day_2025-12-16\", \"wtfsayo\", \"day\", \"2025-12-16\", \"wtfsayo: No activity today.\", \"2025-12-17T05:25:18.322Z\"]\n[\"odilitime_week_2025-12-14\", \"odilitime\", \"week\", \"2025-12-14\", \"odilitime: No activity this week.\", \"2025-12-18T01:11:35.367Z\"]\n[\"tungpun_week_2025-12-14\", \"tungpun\", \"week\", \"2025-12-14\", \"tungpun: Focused on a significant bugfix effort, pushing a single large commit that modified 157 files (+5176/-1946 lines).\", \"2025-12-18T01:11:46.523Z\"]\n[\"madjin_day_2025-12-15\", \"madjin\", \"day\", \"2025-12-15\", \"madjin: With 5 commits modifying 6 files (+68/-36 lines), madjin's work today primarily involved other work (60%) and bugfix work (40%) across various file types.\", \"2025-12-18T01:11:47.410Z\"]\n[\"tungpun_day_2025-12-17\", \"tungpun\", \"day\", \"2025-12-17\", \"tungpun: Focused on bugfix work, making a single commit that modified 157 files with a substantial change of +5176/-1946 lines across various file types.\", \"2025-12-18T01:11:47.649Z\"]\n[\"standujar_day_2025-12-17\", \"standujar\", \"day\", \"2025-12-17\", \"standujar: Focused on feature work, modifying 21 files with 2 commits (+1271/-319 lines) and providing 1 PR comment.\", \"2025-12-18T01:11:47.684Z\"]\n[\"lalalune_day_2025-12-17\", \"lalalune\", \"day\", \"2025-12-17\", \"lalalune: Focused on other work, making 16 commits that modified 2266 files with a net addition of over 260,000 lines, indicating significant development across various file types.\", \"2025-12-18T01:11:47.728Z\"]\n[\"odilitime_day_2025-12-18\", \"odilitime\", \"day\", \"2025-12-18\", \"odilitime: Focused on other work, making a single commit that modified 5 files with a net addition of 170 lines of code.\", \"2025-12-18T01:11:47.779Z\"]\n[\"borisudovicic_day_2025-12-17\", \"borisudovicic\", \"day\", \"2025-12-17\", \"borisudovicic: Demonstrated a strong focus on product refinement and user experience by creating 31 issues, with 17 already closed, addressing a wide range of improvements from UI/UX enhancements like \\\"Rename \\\"Knowledge\\\" section to \\\"Files\\\"\\\" (elizaos/eliza#6237) and \\\"Add three-dot menu to agent cards\\\" (elizaos/eliza#6234) to critical bug fixes and performance investigations.\", \"2025-12-18T01:11:47.817Z\"]\n[\"madjin_day_2025-12-17\", \"madjin\", \"day\", \"2025-12-17\", \"madjin: Focused on enhancing the `elizaos.github.io` project's functionality and maintainability, notably implementing an RSS feed across multiple PRs (e.g., #175, #172, #178) and improving fork-friendliness by making values configurable via environment variables (#180). Their work primarily involved bug fixes, refactoring, and feature development, touching a significant amount of code across 90 files.\", \"2025-12-18T01:11:47.905Z\"]\n---\n2025-12-20T02:13:32.218685Z\n---\n2025-12-20\n---\nai_news_elizaos_discord_md_2025-12-19\n---\nai_news_elizaos_discord_md_2025-12-18\n---\nai_news_elizaos_discord_md_2025-12-17\n---\nai_news_elizaos_daily_json_2025-12-19\n---\nai_news_elizaos_daily_md_2025-12-19\n---\nai_news_elizaos_daily_discord_json_2025-12-19\n---\nai_news_elizaos_daily_discord_md_2025-12-19\n---\ngithub_summaries_week_latest_2025-12-14.md\n---\ngithub_summaries_month_latest_2025-12-01.md\n---\ngithub_summaries_daily_2025-12-20"
  ]
}