release: merge develop into main for v0.32.0

Author: DavidsonGomes

.claude/rules/skills.md

@@ -26,6 +26,7 @@ The workspace has skills in two layers:
 | `pulse-` | Community (daily, weekly, monthly, FAQ sync) | 4 |
 | `sage-` | Strategy (OKR review, strategy digest, competitive analysis) | 3 |
 | `create-` | Workspace management (create-routine, create-agent, create-command, create-heartbeat, create-goal, create-ticket, manage-heartbeats) | 7 |
+| `plugin-` | Plugins (install, list, uninstall, update, marketplace, health) | 6 |
 
 > **Note:** `evo-*` skills (Evo Method) have been moved to the separate [EVO-METHOD](https://github.com/EvolutionAPI/EVO-METHOD) project.
 

.claude/settings.json

@@ -12,6 +12,16 @@
             "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/agent-tracker.sh\""
           }
         ]
+      },
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 \"$CLAUDE_PROJECT_DIR/dashboard/backend/claude_hook_dispatcher.py\" PreToolUse",
+            "_evonexus_managed": true
+          }
+        ]
       }
     ],
     "Stop": [
@@ -23,6 +33,40 @@
             "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/agent-tracker.sh\""
           }
         ]
+      },
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 \"$CLAUDE_PROJECT_DIR/dashboard/backend/claude_hook_dispatcher.py\" Stop",
+            "_evonexus_managed": true
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 \"$CLAUDE_PROJECT_DIR/dashboard/backend/claude_hook_dispatcher.py\" PostToolUse",
+            "_evonexus_managed": true
+          }
+        ]
+      }
+    ],
+    "SubagentStop": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "python3 \"$CLAUDE_PROJECT_DIR/dashboard/backend/claude_hook_dispatcher.py\" SubagentStop",
+            "_evonexus_managed": true
+          }
+        ]
       }
     ]
   },

.claude/skills/plugin-health/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: plugin-health
+description: Check an installed plugin's health — verify manifest SHA256 matches files on disk, detect tampering or corruption. Use when the user asks if a plugin is working, reports a bug, or wants to validate integrity. Triggers on "plugin X está funcionando?", "health plugin X", "status plugin X", "está ok o plugin Y?".
+metadata:
+  category: plugins
+  version: 1.0.0
+---
+
+# Plugin Health
+
+Run on-demand integrity check for a plugin. Compares `.install-manifest.json` SHA256 entries against actual files on disk. Detects tampering, partial corruption, or missing files.
+
+## How to use
+
+### Step 1 — Resolve the slug
+
+If not given, list and ask:
+
+```python
+from dashboard.backend.sdk_client import evo
+
+plugins = evo.get("/api/plugins")
+```
+
+### Step 2 — Run health check
+
+```python
+health = evo.get(f"/api/plugins/{slug}/health")
+```
+
+Response shape:
+
+```json
+{
+  "status": "active" | "broken" | "routine_activation_pending",
+  "reason": "sha_mismatch" | "missing_files" | null,
+  "files": [".claude/agents/plugin-foo-agent.md", ...],  // if broken
+  "checked_at": "..."
+}
+```
+
+### Step 3 — Report
+
+**If `active`:** plugin is healthy. Summarise: total files checked, all SHA256 matching, registered hooks/heartbeats/routines still wired.
+
+**If `broken`:**
+- List corrupted/missing files
+- Suggest options:
+  - Reinstall: `plugin-install` with same source URL (overwrites files, preserves data)
+  - Uninstall + reinstall: clean slate
+  - Manual fix: edit files back to original state (if user knows what was changed)
+
+**If `routine_activation_pending`:** scheduler was offline during install. Tell user to start/restart scheduler.
+
+## Error handling
+
+- `HTTP 404 not_found` — plugin not installed.
+- `HTTP 500 health_check_failed` — filesystem permission issue or manifest unreadable. Check `ADWs/logs/plugins/`.
+
+## Notes for the agent
+
+- Broken state doesn't auto-disable. Plugin files may still work partially. User should decide whether to act.
+- If multiple plugins broken at once, likely the user did a git operation or `.claude/` migration. Health check is diagnostic, not autofix.

.claude/skills/plugin-install/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: plugin-install
+description: Install an EvoNexus plugin from a git URL or uploaded archive. Use when the user asks to install a plugin, add a plugin, or mentions a plugin source URL (github:user/repo, https://..., or a ZIP/tar.gz upload). Triggers on phrases like "instala plugin", "install plugin X", "adicionar plugin", "quero instalar Y".
+metadata:
+  category: plugins
+  version: 1.0.0
+---
+
+# Plugin Install
+
+Install an EvoNexus plugin through the `/api/plugins/*` endpoints. Plugins execute arbitrary code (agents, skills, shell hooks, SQL migrations) — always surface the preview and require explicit confirmation before running the install.
+
+## How to use
+
+### Step 1 — Obtain the source URL
+
+Ask for the plugin source if not provided. Accepted forms:
+
+- `github:user/repo` — default branch
+- `github:user/repo@v1.2.3` — specific tag or branch
+- `https://…/archive.tar.gz` or `https://…/archive.zip` — HTTPS tarball / zip URL
+- Uploaded archive (`.zip` / `.tar.gz`) — via the `/plugins` upload flow
+
+Local filesystem paths (`/abs/path`, `./rel`, `~/...`) and non-HTTPS schemes (`file://`, `ssh://`, etc.) are **rejected by the backend** — do not try to work around that. If the user has a local checkout, tell them to push to a branch, create a release tag, or zip the plugin directory and upload it.
+
+### Step 2 — Preview the manifest
+
+Use the EvoClient SDK (auto-resolves URL + Bearer auth):
+
+```python
+from dashboard.backend.sdk_client import evo
+
+preview = evo.post("/api/plugins/preview", {"source_url": "<URL>"})
+```
+
+Show the user, in this order:
+
+- **Identidade:** id, name, version, author, license
+- **Capabilities:** agents, skills, commands, rules, heartbeats, routines, widgets, migrations, claude_hooks (only keys present)
+- **Env vars exigidas:** `env_vars_required`. Must exist in `.env`.
+- **`install.sql` completo** (expanded): full SQL. Runs in transaction against dashboard DB.
+- **Hooks shell completos:** full text of `hooks/pre-install.sh` and `hooks/post-install.sh`.
+- **Claude hook handlers** (if any): full text of `claude_hook_handlers/*.{py,sh}`.
+
+Do not abbreviate. The user needs to read everything that will execute.
+
+### Step 3 — Require explicit confirmation
+
+Accept only clear affirmatives ("sim", "confirmar", "pode instalar", "ok"). If the user hesitates or asks for changes, stop and answer — do not install.
+
+### Step 4 — Run the install
+
+```python
+result = evo.post("/api/plugins/install", {
+    "source_url": "<URL>",
+    "confirmed": True,
+})
+```
+
+### Step 5 — Report the outcome
+
+On success (`{"status":"active","id":"<slug>"}`), summarise what the user now has: agents under `.claude/agents/plugin-<slug>-*`, heartbeats visible in `/heartbeats`, routines (scheduler reload on SIGHUP), widgets on Overview next page load.
+
+If scheduler was offline and plugin has routines, backend returns `routine_activation_pending=true` — explain the user needs to start the scheduler.
+
+## Error handling
+
+- `HTTP 400 invalid_source_url` — URL failed source whitelist. Reprompt.
+- `HTTP 400 schema_invalid` — manifest rejected by Pydantic. Show validation error.
+- `HTTP 409 slug_conflict` — plugin id already installed. Offer uninstall first or a different one.
+- `HTTP 409 install_in_progress` — another install running. Retry or check `/plugins` UI.
+- `HTTP 500 migration_failed` — SQL transaction rolled back. DB unchanged. Surface SQLite error.
+- Other 5xx — capture body, suggest checking `ADWs/logs/plugins/`.
+
+## Notes for the agent
+
+- Never skip preview, even with high-trust URLs.
+- Never pass `confirmed=True` without explicit user green light.
+- Install one plugin at a time — if user asks for several, preview+confirm each in sequence.

.claude/skills/plugin-list/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: plugin-list
+description: List all installed EvoNexus plugins with status, version, and update availability. Use when the user asks about installed plugins, wants an inventory, or mentions plugins generally. Triggers on "quais plugins tenho", "list plugins", "plugins instalados", "o que tem instalado".
+metadata:
+  category: plugins
+  version: 1.0.0
+---
+
+# Plugin List
+
+Return the current inventory of installed plugins.
+
+## How to use
+
+### Step 1 — Fetch installed plugins
+
+```python
+from dashboard.backend.sdk_client import evo
+
+plugins = evo.get("/api/plugins")
+```
+
+Response is a JSON array of `{id, name, version, status, tier, installed_at, source_url}`.
+
+### Step 2 — (Optional) Cross-check marketplace for updates
+
+If user hints at "desatualizados" / "outdated" / "updates":
+
+```python
+marketplace = evo.get("/api/plugins/marketplace")
+```
+
+Match installed vs marketplace by `id`; flag when `installed.version < marketplace.version` (semver).
+
+### Step 3 — Render compact markdown table
+
+```
+| slug | name | version | status | update? |
+|------|------|---------|--------|---------|
+| pm-essentials | PM Essentials | 1.0.0 | active | — |
+| int-pipedrive | Pipedrive Suite | 0.4.1 | active | 0.5.0 |
+```
+
+Order by `name` ascending. Hide columns user didn't ask for.
+
+Close with a one-line summary: total installed, N with updates, N broken (`status=broken` = manifest SHA mismatch, suggest `plugin-health`).
+
+## Error handling
+
+- Empty `[]` — say plainly no plugins installed, offer `plugin-marketplace`.
+- HTTP 5xx — verify the dashboard backend is running; don't invent data.
+
+## Notes for the agent
+
+- Omit `source_url` from output unless asked — long and noisy.
+- If `status` is `routine_activation_pending`, surface explicitly — scheduler offline during install, restart needed.

.claude/skills/plugin-marketplace/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: plugin-marketplace
+description: Browse the EvoNexus plugin marketplace, searching for plugins by keyword, tag, or capability. Use when the user wants to find a plugin, asks what plugins are available, or describes a need that might have a plugin. Triggers on "procura plugin de X", "marketplace de plugins", "plugins disponíveis para Y", "tem algum plugin que faz Z".
+metadata:
+  category: plugins
+  version: 1.0.0
+---
+
+# Plugin Marketplace
+
+Browse the curated `registry.json` from `github.com/EvolutionAPI/evonexus-plugins` plus community plugins. Help the user find what they need and hand off to `plugin-install` when they pick one.
+
+## How to use
+
+### Step 1 — Fetch registry
+
+```python
+from dashboard.backend.sdk_client import evo
+
+marketplace = evo.get("/api/plugins/marketplace")
+```
+
+Cached 10min backend-side. If backend returns 503 `marketplace_unreachable`, tell the user the registry is offline and suggest direct install via git URL (`plugin-install`).
+
+### Step 2 — Filter by user intent
+
+Each entry: `{id, name, version, repo_url, tier, tags, description, verified, author, homepage}`.
+
+- If user provided a keyword, match against `name`, `description`, `tags`
+- If user wants "verified only", filter `verified=true`
+- If user wants a specific `tier` (essential vs full-stack), filter
+
+Default: don't filter, show everything ordered by `verified=true` first, then alphabetical.
+
+### Step 3 — Render results
+
+```
+### 🟢 PM Essentials (verified)
+Agents, skills, routines para gestão de projetos com sincronização Linear.
+v1.0.0 · tags: pm, linear, showcase · MIT · @EvolutionAPI/evonexus-plugin-pm-essentials
+
+### 🟢 Pipedrive Suite (verified)
+CRM integrado: pipeline, deals, health scores.
+v0.4.1 · tags: crm, pipedrive · MIT · @user/evonexus-plugin-pipedrive
+
+### Community: Custom Linear Sync
+Fork extendido com webhooks do Linear.
+v2.0.0 · tags: linear, webhooks · @community/evonexus-plugin-linear-webhooks
+```
+
+Use `🟢 verified` green badge, no badge for community.
+
+### Step 4 — Offer to install
+
+If the user expresses interest in a specific plugin ("instala o Pipedrive", "quero esse aí"), hand off to `plugin-install` skill passing the `repo_url` directly.
+
+## Error handling
+
+- Empty registry (nothing returned) — possible fresh registry or fetch error. Suggest direct install via git URL.
+- `HTTP 503 marketplace_unreachable` — fetcher failed (offline or GitHub down). Offer to retry or install directly by URL.
+
+## Notes for the agent
+
+- Don't invent plugins. Only list what backend returns.
+- Verified badge is meaningful — `verified=true` means the Evolution team reviewed. Default recommendations to verified.
+- If user asks "what's new", sort by installed_at descending (latest first).
+- Respect tier: `tier=full-stack` plugins are bigger commitment (UI, backend), `tier=essential` are lighter.