🚀 Big momentum this week: we’re unblocking the next wave of third‑party plugins while tightening up infra + community testing paths!

**Week recap (2026-05-07 → 2026-05-13):**
- 🧩 **Plugin Registry v2:** Third‑party submissions hit a blocker — `elizaos-plugins/registry` and `plugins.elizacloud.ai` are returning **404s**. Core devs are investigating, and we may **temporarily revert to PRs directly to `elizaOS/eliza`** for faster shipping.
- 📦 **Plugin submission edge cases:** A ready-to-ship plugin (`plugin-undesirables@2.0.3`) highlighted **BUSL-1.1 licensing constraints** (can’t PR into the monorepo), reinforcing why the registry path matters.
- 🤝 **Sandbox agent testing:** A community dev requested approval to test a **Python multi-agent orchestrator** (A2A read-only research agent + MCP tools like Tavily/DDG/arXiv) in a **locked-down sandbox channel**. OAuth/whitelisting flow is being coordinated.
- 🛡️ **Discord security:** Mods flagged **scammer activity / possible compromised accounts**. Team is actively reviewing server safety and permissions.
- 💸 **Ops note:** Running an Eliza Twitter bot can be as low as **~$10/month** depending on reply volume/config.

**Community highlights**
- 👋 New builder intros (AI + full-stack folks joining with a strong “production > hype” mindset).
- 🧠 Healthy discussion around registry policy + safe bot testing practices.

**AI16Z / auto.fun**
- 🪙 No official AI16Z update this week (community questions popped up—team will share clarity when available).
- 🧪 No new auto.fun launch notes in the log this week.

**Next up:** fix registry access, publish the finalized plugin submission path, and kick off the sandbox orchestrator test with clear guardrails.