## Issue Triage — 2025-12-22

### 1) Snapshot Eligibility Issue + Tangem Wallet Connection Not Supported (Discord Support Compromised)
- **Issue Title & ID:** Snapshot Eligibility Issue + Tangem Wallet Connection Not Supported (Discord Support Compromised) — elizaos/eliza **#6211**
- **Current Status:** **OPEN** (reported; 1 comment)
- **Impact Assessment:**
  - **User Impact:** **High** (affects a meaningful subset of holders using Tangem / non-exportable wallets; repeated migration confusion echoed in Discord)
  - **Functional Impact:** **Partial** (blocks token migration for impacted users; migration is ecosystem-critical but not core runtime execution)
  - **Brand Impact:** **High** (migration friction + “Discord impersonators” narrative undermines trust)
- **Technical Classification:**
  - **Issue Category:** **Security / UX / Documentation**
  - **Component Affected:** **Token Migration Portal + Support Channels (Discord)**
  - **Complexity:** **Moderate effort** (may require portal wallet support changes, plus operational comms/verification)
- **Resource Requirements:**
  - **Required Expertise:** Web3 wallet connectivity (WalletConnect), backend allowlist/eligibility tooling, security comms/moderation
  - **Dependencies:** Snapshot/eligibility data source; migration portal code ownership; policy decision on manual remediation
  - **Estimated Effort:** **4/5**
- **Recommended Priority:** **P0**
- **Specific Actionable Next Steps:**
  1. Publish an **official, signed “Support & Safety” notice** (GitHub + docs + pinned Discord) stating: never send tokens manually; list only official links.
  2. Confirm policy: **are Tangem-held tokens eligible if on-chain address held at snapshot** (likely yes if address is in snapshot set).
  3. Implement one remediation path:
     - **Option A (preferred):** Add migration portal support for **WalletConnect/Tangem** or an alternate connection method.
     - **Option B:** Build a **manual claim workflow**: user proves address control (message signature if possible) + backend allowlist mapping.
  4. Add a **public FAQ**: “Bought after snapshot date cannot migrate,” deadline (Feb 4, 2026), and wallet limitations.
  5. Add an internal playbook for moderators to route users and close impersonation vectors (ticketing, verified bots, role restrictions).
- **Potential Assignees:** **Borko** (ecosystem lead), **Stan ⚡** (release/systems coordination per Discord), **Jin/madjin** (comms + data endpoints experience), plus whoever owns the migration portal codebase.

---

### 2) Release Pipeline Blocker: NPM “classic token” deletion / token rotation breaking releases
- **Issue Title & ID:** NPM token rotation deleted classic tokens causing publish failures — **(No GH issue captured in provided data; create tracking issue)**
- **Current Status:** **Active risk** (Discord indicates ongoing work; release pressure with Cloud MVP + streaming)
- **Impact Assessment:**
  - **User Impact:** **Critical** (blocks new versions; users can’t get fixes like streaming/npm fixes in v1.7.0 context)
  - **Functional Impact:** **Yes** (prevents shipping)
  - **Brand Impact:** **High** (failed releases, broken installs)
- **Technical Classification:**
  - **Issue Category:** **DevOps / Reliability**
  - **Component Affected:** **CI/CD + Package Publishing (npm)**
  - **Complexity:** **Simple fix → Moderate effort** (depending on CI secrets rotation and org policy)
- **Resource Requirements:**
  - **Required Expertise:** CI/CD (GitHub Actions), npm publishing, secret management
  - **Dependencies:** Access to npm org, GitHub secrets, release workflows
  - **Estimated Effort:** **2/5**
- **Recommended Priority:** **P0**
- **Specific Actionable Next Steps:**
  1. Create a GH issue in **elizaos/eliza**: “NPM publishing token rotation / release workflow failure.”
  2. Rotate to **automation tokens** with least privilege; update GitHub Actions secrets; verify provenance/2FA settings.
  3. Add a CI **preflight step** that validates auth (`npm whoami`) before attempting publish.
  4. Document a short “release operator” runbook (how to rotate tokens, where secrets live, emergency rollback).
- **Potential Assignees:** **cjft** (mentioned re: npm fixes), **ChristopherTrimboli** (CLI/release changes experience), **Stan ⚡** (release coordination)

---

### 3) Cloud MVP Streaming Release Coordination (monorepo → elizacloud-plugin → cloud-v2 order)
- **Issue Title & ID:** Cloud streaming release blocked by cross-repo sequencing / version pinning — **(No GH issue captured; create tracking issue/epic)**
- **Current Status:** **In progress** (Discord: ship Cloud MVP Monday; order of operations explicitly called out)
- **Impact Assessment:**
  - **User Impact:** **High** (Cloud MVP is a primary onboarding path; streaming is a headline UX improvement)
  - **Functional Impact:** **Partial** (Cloud works but missing/unstable streaming if not coordinated)
  - **Brand Impact:** **High** (launch quality)
- **Technical Classification:**
  - **Issue Category:** **Bug / Release Management**
  - **Component Affected:** **Cloud product + plugin integration + core versioning**
  - **Complexity:** **Moderate effort**
- **Resource Requirements:**
  - **Required Expertise:** Monorepo release process, dependency/version management, cloud deployment
  - **Dependencies:** Monorepo release; merge/review of **elizacloud-plugin**; cloud-v2 consuming latest core; fix plugin core version from old alpha → stable
  - **Estimated Effort:** **3/5**
- **Recommended Priority:** **P1**
- **Specific Actionable Next Steps:**
  1. Open a single **release checklist issue** with boxes for:
     - Monorepo release
     - elizacloud-plugin merge (and core version bump)
     - cloud-v2 update + deploy
  2. Pin versions and add a CI gate to prevent **alpha core versions** being consumed by cloud plugins unless explicitly allowed.
  3. Add smoke tests: “streaming response end-to-end” + “chat creation when no summary exists” regression.
- **Potential Assignees:** **Stan ⚡**, **Borko**, **standujar** (core/server), **ChristopherTrimboli** (CLI/cloud integration context), **lalalune** (cloud integration PR author)

---

### 4) Concurrent Connection Timeouts / Server Reliability Under Load
- **Issue Title & ID:** Concurrent connection timeouts — elizaos/eliza **#6198**
- **Current Status:** **OPEN** (identified by linear; details not included in provided snippet)
- **Impact Assessment:**
  - **User Impact:** **High** (timeouts typically hit many users once load increases, especially with Cloud MVP launch)
  - **Functional Impact:** **Yes** (prevents chat/session creation or message delivery under concurrency)
  - **Brand Impact:** **High** (perceived instability)
- **Technical Classification:**
  - **Issue Category:** **Performance / Bug**
  - **Component Affected:** **Server API + Socket.IO + DB/message bus**
  - **Complexity:** **Complex solution** (likely needs profiling, pooling, backpressure, and/or architectural tuning)
- **Resource Requirements:**
  - **Required Expertise:** Node/Bun performance, DB connection pooling, Socket.IO behavior, load testing
  - **Dependencies:** Repro harness; clarity on deployment topology (cloud-v2, DB type)
  - **Estimated Effort:** **5/5**
- **Recommended Priority:** **P1**
- **Specific Actionable Next Steps:**
  1. Add a minimal **reproduction script** (k6/artillery) targeting sessions/messages endpoints + socket connect.
  2. Capture metrics: event loop lag, open connections, DB pool saturation, message bus latency.
  3. Identify whether timeouts correlate with streaming enabled (new message stream events).
  4. Implement fixes: pool sizing, request queuing, socket auth/handshake tuning, and explicit timeouts with better errors.
- **Potential Assignees:** **standujar** (server/core), **lalalune** (large-scale refactors), **ChristopherTrimboli** (infra/testing), plus cloud operator support from **Stan ⚡**

---

### 5) Pre-upload Files in Agent Creator for RAG
- **Issue Title & ID:** Pre-upload files in agent creator for rag — elizaos/eliza **#6245**
- **Current Status:** **OPEN** (created 2025-12-16 per logs)
- **Impact Assessment:**
  - **User Impact:** **Medium** (common workflow for RAG users; improves onboarding)
  - **Functional Impact:** **Partial** (RAG possible but less discoverable/efficient)
  - **Brand Impact:** **Medium** (polish and usability)
- **Technical Classification:**
  - **Issue Category:** **UX / Feature Request**
  - **Component Affected:** **Client UI + Upload/Knowledge pipeline**
  - **Complexity:** **Moderate effort**
- **Resource Requirements:**
  - **Required Expertise:** Frontend (client), server uploads, storage provider integration (Cloud/local), UX flow design
  - **Dependencies:** Any ongoing “Knowledge → Files” rename work (#6237); docs updates
  - **Estimated Effort:** **3/5**
- **Recommended Priority:** **P2**
- **Specific Actionable Next Steps:**
  1. Define desired UX: upload during agent creation vs after; supported file types; progress + error states.
  2. Ensure uploads are **scoped** correctly (especially if JWT/data isolation work lands via PR #6200).
  3. Add integration tests for: create agent → upload files → run retrieval in first chat.
- **Potential Assignees:** **0xbbjoker** (issue author), **wtfsayo** (client/plugin migrations), **standujar** (server APIs)

---

### 6) Web Search Capability (Agent Tooling)
- **Issue Title & ID:** Web Search — elizaos/eliza **#6246**
- **Current Status:** **OPEN** (planned feature per weekly summary)
- **Impact Assessment:**
  - **User Impact:** **Medium** (widely desired; expands agent usefulness)
  - **Functional Impact:** **No** (not required for core runtime)
  - **Brand Impact:** **Medium** (competitive feature expectation)
- **Technical Classification:**
  - **Issue Category:** **Feature Request**
  - **Component Affected:** **Core Framework / Tooling + Plugin System**
  - **Complexity:** **Complex solution** (providers, safety, rate limits, caching, citations)
- **Resource Requirements:**
  - **Required Expertise:** Tool design, safety/allowlisting, provider integration, evaluation
  - **Dependencies:** Decide plugin-first vs core tool; docs; potential Cloud billing/keys
  - **Estimated Effort:** **4/5**
- **Recommended Priority:** **P2**
- **Specific Actionable Next Steps:**
  1. Decide MVP: one provider (e.g., SerpAPI-like) + standardized result schema + citations.
  2. Add policy controls: domain allowlist, safe-search, max fetch count, caching.
  3. Provide an example character + scenario tests that validate grounding/citation behavior.
- **Potential Assignees:** **standujar** (core patterns), **borisudovicic** (product scoping), **lalalune** (integration), **madjin** (data pipeline thinking)

---

### 7) Payments Implementation Guide (Circle/Coinbase) for Agents
- **Issue Title & ID:** Implementation guide for integrating Circle and Coinbase APIs for AI agent payments — elizaos/eliza **#6244**
- **Current Status:** **OPEN** (planning)
- **Impact Assessment:**
  - **User Impact:** **Low → Medium** (important for monetization-focused builders)
  - **Functional Impact:** **No**
  - **Brand Impact:** **Medium** (signals maturity and real-world utility)
- **Technical Classification:**
  - **Issue Category:** **Documentation / Feature Enablement**
  - **Component Affected:** **Docs + API patterns + Plugin ecosystem**
  - **Complexity:** **Moderate effort**
- **Resource Requirements:**
  - **Required Expertise:** Payments APIs, security, webhook handling, compliance considerations
  - **Dependencies:** Auth/data isolation direction (PR #6200), Cloud key management patterns
  - **Estimated Effort:** **3/5**
- **Recommended Priority:** **P3**
- **Specific Actionable Next Steps:**
  1. Produce a docs-only MVP: threat model, reference architecture, and sample plugin skeleton.
  2. Clarify key storage/encryption expectations (align with prior secrets-encryption fix work).
- **Potential Assignees:** **tdnupe3** (issue author), **standujar** (auth/security), **madjin** (docs site work)

---

### 8) Docs Work / Gaps (especially around Cloud + Migration + Streaming)
- **Issue Title & ID:** Docs — elizaos/eliza **#6264**
- **Current Status:** **OPEN** (created 2025-12-18 per logs; details not provided)
- **Impact Assessment:**
  - **User Impact:** **High** (Cloud MVP + streaming + migration confusion are documentation-sensitive)
  - **Functional Impact:** **Partial** (reduces successful adoption and increases support burden)
  - **Brand Impact:** **High** (documentation quality signals project maturity)
- **Technical Classification:**
  - **Issue Category:** **Documentation**
  - **Component Affected:** **Docs site + CLI onboarding docs**
  - **Complexity:** **Moderate effort**
- **Resource Requirements:**
  - **Required Expertise:** Technical writing, developer experience, release coordination
  - **Dependencies:** Final behavior of Cloud MVP, streaming APIs, migration portal policy
  - **Estimated Effort:** **3/5**
- **Recommended Priority:** **P1**
- **Specific Actionable Next Steps:**
  1. Add “Getting Started (Cloud)” with streaming example and troubleshooting.
  2. Add “Migration Safety” page (link to #6211 resolution) and scam warnings.
  3. Add “Version compatibility” notes (registry mismatch detection work suggests this is recurring).
- **Potential Assignees:** **borisudovicic** (docs/product), **ChristopherTrimboli** (CLI flows), **madjin** (docs/web), **Stan ⚡** (release facts)

---

### 9) Guided Onboarding + Dashboard Redesign (UX overhaul scope)
- **Issue Title & ID:** Guided user onboarding — elizaos/eliza **#6221**
- **Current Status:** **OPEN** (strategic UX plan)
- **Impact Assessment:**
  - **User Impact:** **Medium**
  - **Functional Impact:** **No**
  - **Brand Impact:** **Medium**
- **Technical Classification:**
  - **Issue Category:** **UX / Feature Request**
  - **Component Affected:** **Client UI**
  - **Complexity:** **Architectural change** (touches IA/navigation and flows)
- **Resource Requirements:**
  - **Required Expertise:** Product UX, frontend architecture, user testing
  - **Dependencies:** Other UI issues (#6222, #6237, #6235/#6236)
  - **Estimated Effort:** **5/5**
- **Recommended Priority:** **P3**
- **Specific Actionable Next Steps:**
  1. Lock an MVP onboarding flow aligned to Cloud as default provider (already in CLI direction).
  2. Instrument completion metrics (time-to-first-chat, time-to-deploy).
- **Potential Assignees:** **borisudovicic**, **wtfsayo**, **lalalune**

- **Issue Title & ID:** Redesigned dashboard — elizaos/eliza **#6222**
- **Current Status:** **OPEN**
- **Impact Assessment:** User **Medium** / Functional **No** / Brand **Medium**
- **Technical Classification:** **UX**, **Client UI**, **Architectural change**
- **Resource Requirements:** Frontend + product; **Effort 5/5**
- **Recommended Priority:** **P3**
- **Next Steps:** Break into deliverable slices (navigation, agent cards/actions, empty states, settings).
- **Potential Assignees:** **borisudovicic**, **wtfsayo**

---

### 10) Terminology & Plugin Selection Polish (reduce confusion, improve perceived quality)
- **Issue Title & ID:** Rename “Knowledge” section to “Files” — elizaos/eliza **#6237**
- **Current Status:** **OPEN**
- **Impact Assessment:** User **Medium** / Functional **No** / Brand **Medium**
- **Technical Classification:** **UX**, **Client UI**, **Simple fix**
- **Resource Requirements:** Frontend copy + minor refactors; **Effort 2/5**
- **Recommended Priority:** **P3**
- **Next Steps:** Update UI labels + docs + any API/client mapping terms; ensure backward compatibility in saved configs.
- **Potential Assignees:** **wtfsayo**, **borisudovicic**

- **Issue Title & ID:** Improve plugin selection visual feedback — elizaos/eliza **#6235**; Toggle selection for plugins — elizaos/eliza **#6236**
- **Current Status:** **OPEN/Tracked** (referenced as rapidly implemented previously, but issues exist in weekly summary context)
- **Impact Assessment:** User **Low → Medium** / Functional **No** / Brand **Medium**
- **Technical Classification:** **UX**, **Client UI**, **Simple fix**
- **Resource Requirements:** Frontend; **Effort 1-2/5**
- **Recommended Priority:** **P3**
- **Next Steps:** Confirm whether implemented; if yes, close with verification; if partial, add regression tests and finish.
- **Potential Assignees:** **wtfsayo**, **borisudovicic**

---

## Highest-Priority Focus (Top 5–10 to address immediately)
1. **P0:** elizaos/eliza **#6211** — Migration portal Tangem support + scam/impersonation mitigation (trust & safety).
2. **P0:** **NPM token rotation/publish failures** — create tracking issue and unblock releases (shipping blocker).
3. **P1:** **Cloud MVP streaming release coordination** — single checklist issue; enforce correct version sequencing.
4. **P1:** elizaos/eliza **#6198** — Concurrent connection timeouts (stability under load, especially pre-launch).
5. **P1:** elizaos/eliza **#6264** — Docs gaps (Cloud + streaming + migration safety) to reduce support load and improve launch quality.
6. **P2:** elizaos/eliza **#6245** — Pre-upload files for RAG in agent creator (onboarding/workflow win).
7. **P2:** elizaos/eliza **#6246** — Web Search (define MVP + safety constraints).
8. **P3:** elizaos/eliza **#6221/#6222** — Onboarding + dashboard redesign (large UX initiative; schedule intentionally).
9. **P3:** elizaos/eliza **#6237/#6235/#6236** — Terminology + plugin selection polish (quick perception wins).

---

## Patterns / Themes Suggesting Deeper Issues
- **Cross-repo release coupling is a recurring risk** (monorepo ↔ plugins ↔ cloud-v2 sequencing; version mismatches in registry). This suggests the need for stricter compatibility automation and a single “source of truth” for supported core/plugin versions.
- **Trust & safety is now a product requirement, not just community moderation** (migration + impersonators). Support-channel integrity directly affects user funds and brand.
- **Operational reliability is converging with feature delivery** (streaming + Cloud MVP increases concurrency/load; timeouts become more visible). Performance work must run in parallel with launches.

---

## Process Improvements (to prevent repeats)
1. **Create “Release Train” checklists** per launch (Cloud MVP, streaming) with explicit dependency order, owners, and rollback steps.
2. **Automate compatibility enforcement**:
   - CI checks that plugins/cloud packages don’t depend on unsupported core ranges (expand on registry mismatch detection work).
   - A machine-readable compatibility matrix published daily/weekly.
3. **Add a Security/Trust playbook**:
   - Official link registry, signed announcements, verified support workflow, and standard incident comms template.
4. **Introduce load testing gates** for server changes that affect messaging/streaming and socket behavior (especially before Cloud releases).
5. **Docs-as-a-deliverable rule**: no major onboarding-flow changes (CLI defaults, Cloud login, streaming) without a docs PR linked in the release checklist.